Web Server Error

Service Unavailable:

If you face the error ‘Service unavailable’  while accessing the domains in the browser.

Cause:

Application pool gets stopped for that domain.

Fix:

In this case you have to  to start or restart the application pool belongs to that domain.

—————————————————————————————————————————————————

Oscommerce:

Error Message

  1. Warning: Installation directory exists at: C:/AppServ/www/catalog/install. Please remove this directory for security reasons.
  2. Warning: I am able to write to the configuration file: C:/AppServ/www/catalog/includes/configure.php. This is a potential security risk – please set the right user permissions on this file.
  3. Warning Warning: The sessions directory does not exist: /tmp. Sessions will not work until this directory is created.

Fix:

  1. Have to delete/rename the install folder
  2. Have to set the configure.php to read-only.
  3. Have to create a /tmp directory or set the sessions from file to database.

—————————————————————————————————————————————————

4o4 errors of ASP.NET MVC:

  1. Open IIS 6 Administrative Console and select the virtual folder of the deployed MVC application. Right click on the virtual folder and select Properties. It brings up properties dialog.
  2. Make sure you’re on the Virtual Directory tab and select Configuration. It brings up the Application Configuration dialog.
  3. In the Wildcard application maps section, click the Insert. button; it brings up the wildcard application mapping dialog.
  4. Enter the path as “c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll”.

Note: The path of the dll might differ on your machine. One easy way to find out is to look for the .aspx extension in the application extensions list and double click it to get the full path.

Uncheck the Verify that file exists checkbox and click the Ok button. Don’t forget to uncheck.

Save the changes by clicking on Ok.

Ref:

http://www.techdreams.org/microsoft/aspnet/how-to-fix-404-errors-of-aspnet-mvc-website-deployed-on-iis-6-windows-server-2003/2572-20090515     Click

—————————————————————————————————————————————————

Error: This is a marker file generated by the precompilation tool, and should not be deleted!

To fix this error, convert the folder to a virtual directory.

————————————————————————————————————————————————–

 

Shared application pool gets stopped:

ASP Error: Could not create a Disk Cache Sub-directory for the Application Pool.

Error: The Template Persistent Cache initialization failed for Application Pool
‘Shared_ASPNET1.1_AppPool’

If you face these errors in IIS. Use the below fix.

Issue fixed by giving access to ‘Inetsrv’. This is a permission problem.

Give IIS_WPG and NETWORK SERVICE permission to access the following directories:

%systemroot%\System32\Inetsrv\ASP Compiled Templates*
%systemroot%\Help\IISHelp\Common
%systemroot%\IIS Temporary Compressed files

http://support.microsoft.com/kb/842493     Click

http://rlieving.blogspot.com/2008/04/resolve-asp-error-could-not-create-disk.html  Click

—————————————————————————————————————————————————

FTP not binded with plesk:

If you face the error while creating the FTP account inside your domain.

“Unable to update hosting preferences: Update FTP user failed: ftpmng –update-user failed: Exception occurred.”

Follow the following steps to fix it.

Go to the path “C:\Parallels\Plesk\admin\bin>” in the command prompt and type the collosing command.

ftpmng –reconfigure-all

It throws error to create the FTP account with the IP address.

Then create the IP address and run the reconfigure command to fix the error.

————————————————————————————————————————–

Server wide PHP error:

Error

"PHP Warning:  PHP Startup: Unable to load dynamic library 'C:\Program
Files\HSphere\3rdparty\PHP\PHP5\ext\php_curl.dll' - The specified module
could not be found"

This error is fixed by placing the DLL "zlib.dll" in the system32 folder.

http://www.forum.psoft.net/showthread.php?t=29775     Click
---------------------------------------------------------------------------------------


Frontpage Extensions:
 
If you are unable to install Frontpage Extensions for a domain.
 
Cause:
 
The folder related to Frontpage Extensions will already there in your web space.
 
Fix
 Delete the folders that start with “_vti” and the reinstall Frontpage Extensions it will be installed successfully.

---------------------------------------------------------------------------------------

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s