Event ID 13360 & 8390 when deleting Storage Service
Trying to decomm an older EV 9.0.2 server from Site.
It's running on a 32-bit Win2k3 Server.
All of the archive data was migrated and remaining Indexes and Vault Store was deleted, although the Vault Store is still there but marked for deletion. A restart of the server was performed but did not complete the delete of the VS.
The services were being removed when an error occured when trying to remove the storage service.
I get a pop-up saying "Unable to delete the service information from the Enterprise Vault directory. Enterprise Vault Storage Service"
Then I get 2 13360 and an 8390 in Event Viewer.
The strange thing is that the Enterprise Vault Storage Service is gone from Windows Services but there is an entry for it in the Admin Console under Services for this server.
I would attempt a Dtrace but not sure which ID to monitor.
I'd like to get rid of the server altogether since my newer Win2k8 Server is up and running with all user data moved over to it.
thoughts?
Comments 6 Comments • Jump to latest comment
One tip to run dtrace is to verify the source on the event viewer error/warning. Then you can dtrace on that process ID. Storagedelete and storagearchive is the first step to start the dtrace. please paste the results.
8390 and 13360 are generic errors so it will be a good idea to post the entire description. 13360 is related to the connection to the sql server.
There is a know issue but is for the version 9.0.3 about the error 8390 that may match with your problem.
http://www.symantec.com/docs/TECH182774
If this response answers your concern, please mark it as a "solution"
Here is the full event ID:
The EV environment is 9.0.2
Here is the output of a DTrace for the DirectoryService which was the source for the 13360 event.
Both the event and the dtrace are complaining about the VaultStoreEntry and StorageServiceEntry tables and there being a conflict when the delete is attempted?
Is this because the legacy VaultStore never finished deleting? And is preventing the deletion of the Storage Service? My initial thought is to manually remove the entry for the Vault Store in the VaultStoreEntry table and then try to remove the service from the Admin Console again?
1- Yes, you cannot delete the service because the are still items in the vaultstore that need to be removed based on the contraint.
CONS_FK_STORAGESERVICEENTRY_VAULTSTOREENTRY
2- Do you have CA / DA ? Because there is technote that explain that you can have items in legal hold.
4- Verify that you dont have any traces created within the console. If you have it delete it and then verify if the store is removed from mark for deletion.
5- Run a dtrace for the storagedelete and then restart the storage service.
If this response answers your concern, please mark it as a "solution"
Don't remove it from the Databases manually, I have seen other customers do this and the vault store contains items that are shared from other vault stores and causes dataloss.
The constraint you are seeing though is that the vault store is tied to the storage service, and until the vault store is removed, the storage service can't be removed...though not even sure why it would be firing that event, it should just show you a pop up dialog
@JesusWept3: Okay so I definately won't do that.
I really want to get off version 9.x and decomm this older EV server.
I was thinking that I could create a new Vault Store Group with new VSs and Partitions and re-migrate the mailbox archives again. This would obviously be painful but since I'd be moving the archives into a net new VSG and VS wouldn't that remove the "shared" constraint I'm currently being limited by?
JOE
Would you like to reply?
Login or Register to post your comment.