dougoz888
IS-IT--Management
- Apr 9, 2008
- 1
Our Network Setup:
Raid Server Running Windows SBS SP2 with network card connecting to a Symantec Gateway 360, with 3 client computers running XP. We only want the server to function as a central server for an accounting program, with no need for email services. There is also an old Server Running on Novell Netware, with 3 older computers running Windows 98, and 1 running XP. All are connected to the Gateway device on the WAN1; WAN2 is disabled. Network DHTP Server is the gateway device. Server DNS and WINS Servers point to the SBS IP address. NET/BIOS is not installed on SBS server.
The problem is that we are getting a series of error messages from SBS every 1 1/2 minutes. On the Application Event Viewer, we get the error message: "Failed to access the metabase, error code is 80080005 (Server execution failed)". Source: MSExchangeMU. Catagory: General. Event ID: 1009.
On the System Event Viewer, we get this sequence of error messages after a start control is sent to IIS Admin Service: "Unable to decrypt the secure property. Ignoring the property. /LM/NNTPSVCAdminACL". Source: IIS Config. Catagory: Catalog. Event ID: 51262.
Next error message: "Unable to decrypt the secure property. Ignoring the property./LM/NNTPSVCLog0dbcPassword". ErrorCode : 0x80090006. Source: IIS Config. Catagory: Catalog. Event ID: 51262.
Next error message: "Unable to decrypt the secure property. Ignoring the property./LM/NNTPSVC/InfoAdminACL. ErrorCode : 0x80090006. Source: IIS Config. Catagory: Catalog. Event ID: 51262.
Next error message: "Unable to decrypt the secure property. Ignoring the property./LM/POP3SVC/1AdminACL". ErrorCode : 0x80090006. Source: IIS Config. Catagory: Catalog. Event ID: 51262.
Next event: "The IIS Admin Service service entered the stopped state.". Source: service Control Manager. Category: None. Event ID: 7036.
On the File Replication Service Event Viewer, twice a day we get the following error message: "The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path. This was detected for the following replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file. [1]At the first poll which will occur in 5 minutes this computer will be deleted from the replica set. [2]At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-additiion will trigger a full tree wync tor the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not."
Then the File Replication Service stops.
This server has had problems before. The IT people who handled it before had to replace the motherboard, which they then proceeded to install incorrectly, breaking the mirror; they re-installed the board and then repaired the mirror. As far as I can tell, after this is when the error messages started, but the event logs do not go back that far. Any help would be appreciated.
Raid Server Running Windows SBS SP2 with network card connecting to a Symantec Gateway 360, with 3 client computers running XP. We only want the server to function as a central server for an accounting program, with no need for email services. There is also an old Server Running on Novell Netware, with 3 older computers running Windows 98, and 1 running XP. All are connected to the Gateway device on the WAN1; WAN2 is disabled. Network DHTP Server is the gateway device. Server DNS and WINS Servers point to the SBS IP address. NET/BIOS is not installed on SBS server.
The problem is that we are getting a series of error messages from SBS every 1 1/2 minutes. On the Application Event Viewer, we get the error message: "Failed to access the metabase, error code is 80080005 (Server execution failed)". Source: MSExchangeMU. Catagory: General. Event ID: 1009.
On the System Event Viewer, we get this sequence of error messages after a start control is sent to IIS Admin Service: "Unable to decrypt the secure property. Ignoring the property. /LM/NNTPSVCAdminACL". Source: IIS Config. Catagory: Catalog. Event ID: 51262.
Next error message: "Unable to decrypt the secure property. Ignoring the property./LM/NNTPSVCLog0dbcPassword". ErrorCode : 0x80090006. Source: IIS Config. Catagory: Catalog. Event ID: 51262.
Next error message: "Unable to decrypt the secure property. Ignoring the property./LM/NNTPSVC/InfoAdminACL. ErrorCode : 0x80090006. Source: IIS Config. Catagory: Catalog. Event ID: 51262.
Next error message: "Unable to decrypt the secure property. Ignoring the property./LM/POP3SVC/1AdminACL". ErrorCode : 0x80090006. Source: IIS Config. Catagory: Catalog. Event ID: 51262.
Next event: "The IIS Admin Service service entered the stopped state.". Source: service Control Manager. Category: None. Event ID: 7036.
On the File Replication Service Event Viewer, twice a day we get the following error message: "The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path. This was detected for the following replica set: "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file. [1]At the first poll which will occur in 5 minutes this computer will be deleted from the replica set. [2]At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-additiion will trigger a full tree wync tor the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not."
Then the File Replication Service stops.
This server has had problems before. The IT people who handled it before had to replace the motherboard, which they then proceeded to install incorrectly, breaking the mirror; they re-installed the board and then repaired the mirror. As far as I can tell, after this is when the error messages started, but the event logs do not go back that far. Any help would be appreciated.
