Questions

win 2003 update to sp1 and after.....

+
0 Votes
Locked

win 2003 update to sp1 and after.....

geo85
hi....
A domain called test1.com with 2 DCs :
DC1 = PDC. 192.168.5.19
DC2 = Web server, Print server. 192.168.5.20
both DCs are window 2003 based.
the domain administrator updated the DC2 to SP1, afterwards DC2 started to hangout and freezes.
the domain is located in another location so am working remotely.
we can access DC1 and from DC1:
1- ping is working.
2- web site is working.
3- nslookup for the DC2 name is working fine.
4- nslookup for the 192.168.5.20 is working fine.
5- from start menu then run then typed \\DC2.test1.com it gives the following error : The file name, directory name, or volume label syntax is incorrect.
6- from start menu then run then typed \\192.168.5.20 it gives the following error : The file name, directory name, or volume label syntax is incorrect.
7- no more printing is successful, all clients off the printing dial.

i need to go there and try to fix the problem, iv read on the net that some errors accrued in case of updating to SP1 as the windows time service stops, so after many times of remote desktop tries i could log to the server and fix the time issue, and found the following errors:
source : Service Control Manager
EventID : 7000
The DgiVecp service failed to start due to the following error:
The system cannot find the file specified.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

source : Service Control Manager
EventID : 7023
The Monitor Boot service terminated with the following error:
The specified module could not be found.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

source : Service Control Manager
EventID : 7000
The SSPORT service failed to start due to the following error:
The system cannot find the file specified.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.

then after while

warning
source : BROWSER
EventID : 8021
The browser service was unable to retrieve a list of servers from the browser master \\DC1 on the network \Device\NetBT_Tcpip_{454BDAA2-9A9A-42B1-A36C-02E8C57F53B1}.

Browser master: \\DC1
Network: \Device\NetBT_Tcpip_{454BDAA2-9A9A-42B1-A36C-02E8C57F53B1}

This event may be caused by a temporary loss of network connectivity. If this message appears again, verify that the server is still connected to the network. The return code is in the Data text box.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.

source : BROWSER
EventID : 8032
The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{454BDAA2-9A9A-42B1-A36C-02E8C57F53B1}. The backup browser is stopping.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

any help in resolving this problem.
thanks.
  • +
    0 Votes
    Spitfire_Sysop

    You know, the backup you made right before upgrading to SP1. If the problem continues then it wasn't SP1. If the problem is fixed by the restore then you have some serious troubleshooting to do. You must find the conflict and resolve it before reinstalling the update.

    If you didn't make a backup recently then good luck to you sir. It is sometimes faster to reimage from the DC install image and start over then it is to fix a problem that is really borked. There are things that once borked are not supported by MS and they will tell you to reinstall too.

    If you hack around and fix it you may find that it comes back to haunt you down the road. It looks fine now but then has odd errors that are even more difficult to track down.

    +
    0 Votes
    markp24

    Go back to before SP1 was installed and see if the issues are resolved., then look around on the internet and see if any of you hardware may have known issues with sp1 you could try formatting and reloading the system clean with windows server then sp1 immediatly after that and see if there are issues.

    +
    0 Votes
    OH Smeg

    Restore from the Backup made prior to installing the SP as recommended by M$.

    Then when that system is running if it still has issues it's most likely to be Hardware Related though it could be something else on the LAN that was altered by the SP. You'll have to Suck it and See.

    Then when you have this LAN working correctly grab a spare Box of the same Specification and load the Server OS and update to SP1 and test the **** out of it. When you do the Testing I would continue to the latest Service Pack but test the **** out of the unit and surrounding LAN which is Isolated from the Production Environment and after you are sure that everything works correctly update to the next SP.

    Continue this till the Server is fully Updated and then if it's working as desired you can start the process on the Production Unit.

    Oh and in a situation like this Remote Support isn't the ideal option it may not even be possible you really need to be able to get your hands on the thing to fix it. That may very well involve a Road Trip but it will be faster and most times far less expensive.

    Col

    +
    0 Votes

    re

    geo85

    thank u all....

    i uninstalled the sp1 and every thing working fine so far, they will move to win 2008 soon with new heavy duty servers.

  • +
    0 Votes
    Spitfire_Sysop

    You know, the backup you made right before upgrading to SP1. If the problem continues then it wasn't SP1. If the problem is fixed by the restore then you have some serious troubleshooting to do. You must find the conflict and resolve it before reinstalling the update.

    If you didn't make a backup recently then good luck to you sir. It is sometimes faster to reimage from the DC install image and start over then it is to fix a problem that is really borked. There are things that once borked are not supported by MS and they will tell you to reinstall too.

    If you hack around and fix it you may find that it comes back to haunt you down the road. It looks fine now but then has odd errors that are even more difficult to track down.

    +
    0 Votes
    markp24

    Go back to before SP1 was installed and see if the issues are resolved., then look around on the internet and see if any of you hardware may have known issues with sp1 you could try formatting and reloading the system clean with windows server then sp1 immediatly after that and see if there are issues.

    +
    0 Votes
    OH Smeg

    Restore from the Backup made prior to installing the SP as recommended by M$.

    Then when that system is running if it still has issues it's most likely to be Hardware Related though it could be something else on the LAN that was altered by the SP. You'll have to Suck it and See.

    Then when you have this LAN working correctly grab a spare Box of the same Specification and load the Server OS and update to SP1 and test the **** out of it. When you do the Testing I would continue to the latest Service Pack but test the **** out of the unit and surrounding LAN which is Isolated from the Production Environment and after you are sure that everything works correctly update to the next SP.

    Continue this till the Server is fully Updated and then if it's working as desired you can start the process on the Production Unit.

    Oh and in a situation like this Remote Support isn't the ideal option it may not even be possible you really need to be able to get your hands on the thing to fix it. That may very well involve a Road Trip but it will be faster and most times far less expensive.

    Col

    +
    0 Votes

    re

    geo85

    thank u all....

    i uninstalled the sp1 and every thing working fine so far, they will move to win 2008 soon with new heavy duty servers.