Hello Ralph,
Thank you for posting here.
According to your description, I understand that you get many event error
1000 about Windows SharePoint Services 2.0 on SBS after you performed the
swing migration. If I have misunderstood the problem, please don't hesitate
to let me know.
Based on my research, I suggest we try the following suggestions to see if
we can resolve this issue:
Suggestion 1:
This issue may occur when the SharePoint Timer Service tries to contact the
configuration database when the computer starts or shuts down. By default,
the configuration database in Windows SharePoint Services is named
STS_config.
The error message that is mentioned in the "Symptoms" section does not
affect the functionality of Windows SharePoint Services or of Windows Small
Business Server 2003. If you can connect to the Windows SharePoint Services
Web site successfully, you can safely ignore this error message.
To work around this issue, add the DependOnService registry entry to the
following registry subkey on the server, and then set the DependOnService
registry entry to MSSQL$SHAREPOINT:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer
To do this, follow these steps.
Warning: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.
1. Click Start, and then click Run.
2. In the Open box, type regedit , and then click OK.
3. Locate, and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer
4. On the Edit menu, point to New, and then click String Value.
5. Type DependOnService , and then press ENTER
6. On the Edit menu, click Modify.
7. In the Value data box, type MSSQL$SHAREPOINT , and then click OK.
8. Quit Registry Editor.
For detail information:
An event ID 1000 error message is logged to the application event log when
you restart Windows Small Business Server 2003
http://support.microsoft.com/?id=840685
Suggestion 2:
This issue may occur if the user account to which the Windows SharePoint
Services Timer Service is configured to log on does not have permissions to
the configuration database. A user account may not have permissions to the
configuration database if the following conditions are true in the order in
which they are presented:
a. You change the user account that is configured as the application pool
identity for the administration and content virtual servers in Windows
SharePoint Services.
b. You do not synchronize the SharePoint Timer Service together with the
new user account information.
For example, this issue may occur in the following scenario. You follow the
steps in the following article in the Microsoft Knowledge Base to change
the application pool identity for the Windows SharePoint Services
administration and content virtual servers. However, you do not perform
substep 3 of the "Step 5: Configure the user Account as the application
pool identity for SharePoint Central Administration" section.
How to change the application pool identity for Windows SharePoint Services
administration and content virtual servers
http://support.microsoft.com/?id=832770
To resolve this issue, synchronize the Windows SharePoint Services Timer
Service together with the new user account information. To do this, follow
these steps:
1. Start Windows SharePoint Services Central Administration.
2. On the Windows SharePoint Services Central Administration page, click
Configure virtual server for central administration under Server
Configuration.
3. On the Configure Administrative Virtual Server page, click Use an
existing application pool, click the existing application pool that you are
already using, and then click OK.
For detail information:
Event ID 1000 is logged one or more times in the Application log and users
do not receive e-mail notification when content on the Web site changes in
Windows SharePoint Services
http://support.microsoft.com/?id=900498
If we cannot resolve the issue after we perform the above steps, please
kindly help me collect some information for further investigation:
Gather MPS network report:
a. Download MPSrepot_network from
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_NETWORK.EXE
b. Run MPSRPT_NETWORK.exe on the server box.
c. The tool will automatically collect the information. This procedure will
take 10~15 minutes.
d. Open Windows Explorer, navigate to the folder:
%SystemRoot%\MPSReports\Network\Reports\Cab\
e. Send the .cab file directly to me at v-terliu@microsoft.com
I hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
the
SBS
SQL
regarding
states
something