Windows SBS 2003 Partition change

[Fyrebaugh]

I worked on a clients computer, the OS partition on the server was set to 12 GB and Windows Updates alone had filled up the space. So last night I used Acronis to back up both partitions, and then resized the two partitions in question, C: and E: Now the OS partition has 48 GB and the secondary partition has 100 GB. Then I used Acronis to recover each partition. However, now on boot, the system reports that a service or driver failed to load, during the "applying system configuration" during boot. However, the boot continues and you can log in. The event viewer shows that the SBS Monitoring fails to connect to the database eventID: 4104 and that The DSRestore Filter failed to connect to local SAM server. Error returned is .When the client is trying to run software that connects to the server, it fails to find the database. Since both partitions seem to be correct and the system is running, I'm at a loss as to why we are getting errors.

 

[imagoon]

Only thing I see about that error is this:

http://eventid.net/display.asp?eventid=4104&eventno=5254&source=SmallBusinessServer&phase=1

I am not that sure about Acronis but many of the disk imagers out there tend to miss things like the disk signatures and some of the lesser used features of NTFS that the servers use. For example I know (certain versions of?) Acronis will roach a DFS mount point on a 2003 server.

 

[Fyrebaugh]

The good news is that I have the customers software finding the database now. The problem there was the paths, originally the secondary partition had a logical drive D, and as per the customers request, we changed that to M:. However, the software was looking for a D path!

Anyway, still getting the errors on boot, and setup an M: share for the customer. Will try to get back out there and see if the uninstalling and reinstalling the monitoring services will work.

Thank you!

 

[JonathanYoung]

I would not worry about those errors. Every time I reboot our company's SBS 2003 I get the same errors. During the shutdown/startup process things happen out of order which is why the errors occur.

If you set up performance monitoring you can set it so that you receive a daily server report. As long as that report contains 0 errors, then you're fine. Another thing, I get about 15 errors on that report every time I reboot, including the unable to connect to local SAM, dsrestor errors.