RE: Failing Application?
- From: v-stezhu@xxxxxxxxxxxxxxxxxxxx (Steven Zhu [MSFT])
- Date: Mon, 24 Apr 2006 07:23:47 GMT
Hi Robert,
Thanks for posting here.
From your post, my understanding on the issue is: you get the "IIS WorkerProcess encountered a problem and needed to close" error message when you
logon the server, and you find the following error message in Event Log:
----------------------------------------------------------------------
Event ID: 1000 Source: Application Error
Faulting application w3wp.exe, version 6.0.3790.1830, faulting module
unknown, version 0.0.0.0, fault address 0x001f0001
Event ID: 1000 Source: Windows SharePoint Services 2.0
#50070: Unable to connect to the database STS_Config on
SBSERVER\SharePoint.
Check the database connection information and make sure that the database
server is running.
-----------------------------------------------------------------------
If I am off base, please feel free to let me know.
Based on my research, this problem could be caused because the SharePoint
Timer Service failed to contact the SharePoint database while the SBS is
rebooting. In SBS 2003, the SharePoint Timer Services is used to send
notifications and performs scheduled tasks of WSS. It needs to access the
SharePoint database when starting. Since the Veritas Backup exec software
is installed on the server box and several backup exec related services
have started during the reboot, these services could cause the SharePoint
database from being mounted in a timely manner, thus, causing the problem
to occur.
I reproduced this problem in my test machine. After the MSSQL$SHAREPOINT
service has stopped, this error message will be logged in the application
log. You may now try to manually start this service to see if the problem
will still occur.
1. Start-->Run-->Type ''services.msc'' (without the quotation marks) and
press Enter.
2. In the Services console, stop the ''SharePoint Timer Services''. Check
the status of the ''MSSQL$SHAREPOINT'' service, make sure it has been
started and then restart the ''SharePoint Timer Services''. The problem
should be resolved.
If there is no problem with the manually service startup, we can set a
service dependent of the SharePoint Timer Service. Please try the following
steps:
1. Start-->Run-->Type ''Regedit'' (without the quotation marks) and press
Enter.
2. In the registry editor, navigate to the following registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer
3. Right-click the blank area in the right panel, click
''New''-->''Multi-String Value''.
4. Input the value name ''DependOnService'' (without the quotation marks)
and then double-click the newly created value. In the value data area, type
''MSSQL$SHAREPOINT'' and click ''OK''.
5. Close the registry editor and reboot the server box.
I hope the above information helps.
Have a nice day.
Best Regards,
Steven Zhu
MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
updated on February 14, 2006.? Please complete a re-registration process
by entering the secure code mmpng06 when prompted. Once you have
entered the secure code mmpng06, you will be able to update your profile
and access the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- Prev by Date: RE: Having a problem with user and admin login
- Next by Date: Re: fax auto answer fails windows 2003 server
- Previous by thread: RE: LaunchConsole.exe can not be found in my 2003 Small Business Serve
- Next by thread: Re: disable email Urgently
- Index(es):
Relevant Pages
|
