Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Vault Replication Error

2 REPLIES 2
Reply
Message 1 of 3
BSchubring
456 Views, 2 Replies

Vault Replication Error

Self inflicted, please help me figure out what else is broken!  Short version, we're running Vault 2013 Pro in a multi-site replication environment.  One of these sites needed a Windows Read only domain controller, and we had the bright idea to put it on the Vault server.  That's the sound of a dozen palms slapping foreheads I just heard as everyone realizes that Active Directory blows away local accounts and pretty much puts a bullet in SQL and Vault operation.

 

We managed to get it back up and running after removing AD services, then manually recreating the AutodeskVault account, and I believe that we have reassigned permissions to that account as needed on the affected system (Vault filestore and Vault's IIS folder) and the system is up and running. Users can check in and out from it. However, replication (and transferring worgroup ownership) appears to still be failing, please see attached image.

 

Capture.PNG

 

What have I potentially missed? The blacked out account name is the administrator account on our domain that all SQL and Vault services run under.  A few services that use this account had to have the credentials re-entered after removing AD, so I think we might have just missed one, but as far as I can tell I got everything related to Vault.

 

Please offer any assistance you think might be helpful to reinstate vault operation after our train wreck of an idea.

2 REPLIES 2
Message 2 of 3
herrerh
in reply to: BSchubring

First i'd check for any errors in the system and application event logs and address those.

 

Then in Local Users and Groups, check to make sure you have the default IIS groups.

 

IIS 7 and up - IIS_WPG.

 

Here are the default permissions for IIS - http://support.microsoft.com/kb/981949

 

Also attach the vlogs, and adms console logs to the posting.

 

-Hywel



Hywell Herrero
Data Management Support Specialist
Product Support
Autodesk, Inc.
Message 3 of 3
BSchubring
in reply to: BSchubring

Just an update of how this is going in case anyone else ever does this to themselves.

 

After removing AD from the Vault server, we recreated the AutodeskVault local account, searched for, and re-added this local account to have permissions on directories like the Filestore, IIS, and the Vault install directory, reset SQL services to run as the proper user (the admin we set up during SQL install), and performed a Repair install of Vault. (regretfully, I didn't keep a close log of what I had fixed) This had the effect of allowing the subscriber to come back online. Users could log into it, check in and check out. However, replication was failing, and workgroup ownership transfers would be marked as 'pending' and never occur.

 

After some more discussion and troubleshooting, Autodesk Support had this to say, and I think it is good advice. 

 

"I highly recommend deleting the workgroup, disabling replication, re-enabling, and recreating the workgroup.  There's going to be too many things that could be wrong and I wouldn't trust it even guessing everything that could be missing after recreating the groups for SQL and IIS."

 

Yesterday, I got the server back in house.  Once we were sure we got all critical data from it, I felt more comfortable beating on it to try and get it to replicate for one last clean backup.  On the problem subscriber, I went through and re-created each SQL/IIS user group and assigned similar permissions to what I saw on the publisher. I uninstalled IIS, rebooted, reinstalled IIS per the adv config guide. Then I performed a repair install of SQL where I was notified a few dozen times about a failure to map user and security IDs, but the repair completed successfully.  I then performed one last re-install (through add-remove programs) of Vault 2013 Pro. After a reboot, replication started!

 

We're still going through with the uninstall/reinstall of all critical components on that system, and upgrading to Vault 2014 SP1 because, as the support rep said, the environment is just too untrustworthy now. But, with a successful replication, and a backup that includes all updates from the problem subscriber, I'll feel a lot better about moving forward.

 

My manager made this analogy which I thought was apt: Ammonia and bleach are effective cleaners, but never should be used together. SQL and AD are the ammonia and bleach of IT.

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report