I just upgraded our ePDM to 2013sp3 from 2011. After the upgarde, every time the server starts, ConisioDBServer.exe starts chewing up ram...eating more memory than SQL Server takes. Last night it counted up to over 6 gigs of system ram, chewing up all of the available virtual memory (when you include SQL and all the other server processes) and the process eventually crashed.
Has anyone ever experienced this? If so, what was the fix?
A related question: I've noticed that the couple of times I killed the ConisioDBServer process, the ePDM was still available to our engineers. What services does this helper provide and can ePDM run without it until a fix is implemented?
The above image was taken 2 hours after ConsisioDBServer was restarted.
Message was edited by: Bob Steffen
Bob,
The ConisioDBServer is responsible for notifications, XML Exports and replications. Basically it runs scheduled tasks against the database, and if you stop it you will only lose that functionality. I haven't seen it grow out of control like that before, a few things to check are the version of that file to make sure it got updated with everything else:
And check your Windows Event logs after you restart it, you will usually get a few messages about it connection to archive servers etc and any errors will be reported there.