Microsoft Knowledge Base Email Alertz

After you upgrade to the FrontPage 2000 Server Extensions, the Application log records two errors each time the Server Extensions are installed to a new Web site or each time a new subweb is created.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 244975 - Last Review: February 22, 2007 - Revision: 1.1

Event Viewer Logs Error "Initializing the SD Failed"

This article was previously published under Q244975

SYMPTOMS

After you upgrade to the FrontPage 2000 Server Extensions, the Application log records two errors each time the Server Extensions are installed to a new Web site or each time a new subweb is created.

The following errors are logged to the Event Viewer Application Log:

Microsoft FrontPage Server Extensions: (OS Error #2 Message: The system cannot find the file specified.)
Microsoft FrontPage Server Extensions: http://servername - Error #e002c Message: Cannot read or set the permissions for file, c:\path\_vti_bin: initializing the SD failed.

CAUSE

The error is generated when the value AllowExecutableScripts=1 is set for a Web site that resides on Internet Information Server. When AllowExecutableScripts is set to a non-zero value, FrontPage sets the executable bit on files within executable directories. In this case, the Server Extensions attempt to mark the files within _vti_bin as executable, but the _vti_bin is no longer in the content area of the Web site. The _vti_bin is now a virtual directory pointing outside of the content area and is a design change with the FrontPage 2000 Server Extensions.

The value AllowExecutableScripts=1 is set when you configure the Server Extensions tab in the Internet Service Manager to "Allow authors to upload executables." This value can be set in the master properties or per virtual site.

RESOLUTION

Ignore the errors in the Event Viewer. The errors are logged to the Event Viewer Application log, and are innocuous.

If you prefer not to see the errors, set the value for AllowExecutableScripts to 0 in the Registry at the following locations:
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\All Ports\AllowExecutableScripts

HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Ports\Port /LM/W3SVC/# Where # is the instance of the Web site.
				
Setting AllowExecutableScripts to a value of 0 means that you can publish content to the server and executable files uploaded to the server, but the files will not be marked executable. This will be the case if the corresponding value NoExecutableCgiUpload is set to a value of 0 as well.

STATUS

Microsoft has confirmed that this is a problem in Microsoft FrontPage 2000 Server Extensions.

APPLIES TO
  • Microsoft FrontPage 2000 Server Extensions
Keywords: 
kbbug kbpending KB244975
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate