env: /etc/init.d/xxx: No such file or directory

Friday, September 3, 2010


Symptom

Shell script in Linux fail to start and returns the following error message:

"env: /etc/init.d/xxx: No such file or directory"

Cause
Due to different way of handling text file encoding, a Linux shell script might contains extra after transferring from a Windows machine to a Linux machine.

Resolution

1. Download DOS2UNIX utility and put it into the same directory as your shell script in a Windows machine.

2. Run Windows Command Prompt and execute:

dos2unix.exe <filename>

3. Once completed, upload the file in ASCII mode via your FTP client to the Linux machine and try running the shell script again.

Google Desktop Search Outlook Addin is not loading

Friday, July 16, 2010


Symptom

When you start Microsoft Office Outlook 2007, you receive the following error message:

"The Add-in “Google Desktop Search Outlook Addin” (C:\Program Files\Google\Google Desktop Search\ GoogleDesktopOffice.dll) cannot be loaded and has been disabled by Outlook. Please contact the Add-in manufacturer for an update. If no update is available, please uninstall the Add-in."



Cause
This error occurs when Microsoft Office Outlook 2007 was trying to load GoogleDesktopOffice.dll file which had been removed during the uninstallation of Google Desktop Search application.

Resolution
1. Open Microsoft Office Outlook 2007. In the toolbar, select Tools -> Trust Center. A new dialog box will be displayed. Select Add-Ins and then ensure Exchange Client Extensions is selected at the bottom of the dialog box. Click Go to proceed.



2. Uncheck the Google Desktop Search Outlook Addin in the Add-In Manager list to remove the add-in reference. Finally, click OK and then restart the Outlook application.

The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to (path)

Monday, July 5, 2010


Symptom

When requesting ASP.NET page on a Microsoft Windows Server 2003 server that is running Internet Information Services (IIS) 6.0, the following error message are displayed:

"The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files. "



Cause
User NT AUTHORITY/NETWORK SERVICE does not have the necessary permissions to write files in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files folder.

Resolution
1. Right click on Temporary ASP.NET Files directory, select Properties and then Security tab.

2. Check whether user NETWORK SERVICE is listed in the “Group or user names” column.



3. If it is listed, select Allow for the following check boxes:
  • Read & Execute
  • List Folder Contents
  • Read
  • Write


4. If it is not listed, click the Add button to add user NETWORK SERVICE and then repeat Step 3.

5. Click OK to save your changes.

6. You may be warned that “You are about to change the permission settings on system folders…”



Finally, click Yes to proceed.

HTTP Error 404 - File or directory not found

Saturday, June 26, 2010


Symptom

When requesting dynamic content such as an ASP or ASP.NET page on a Microsoft Windows Server 2003 server that is running Internet Information Services (IIS) 6.0, the following error message are displayed:

"HTTP Error 404 - File or directory not found."



Cause
By default, IIS disables dynamic content on any version of the Windows Server 2003 family for security reasons.

Resolution
1. Open IIS Manager, expand the master server node, and then select the Web Service Extensions node.



2. Check whether the extension of the dynamic content is listed in the Web Service Extension list.

3. If it is listed, then check the status. If the current status is Prohibited, click the Allow button.

4. If it is not listed, you need to create a new extension. In the right pane of the IIS Manager, click Add a new Web service extension under Tasks. In the Extension name box, type a name for the extension that you want to add.

In the Required files box, click Add, and then select the path and the name of the file that will handle requests for the specific extension. After you select the path and the file name, click OK.



Click to select the Set extension status to Allowed check box.

Click OK to save your changes.