SteveJJH
Mechanical
- Feb 5, 2009
- 109
Hello
We’ve been having some problems with our PDM here today. We are running Workgroup PDM with SolidWorks 2011.
This morning a couple of times SolidWorks would seem to hang for a few seconds when trying to do anything with the vault, then late morning one by one peoples machines completely locked up.
I stopped and restarted the vault service and after the tree rebuild everything seemed fine. (Is there any way to stop it doing the rebuild by the way, it takes an hour and a half?)
Looking on the log file for the vault, there are a few lines that look like this:
pdmwRequestHandler:
rocessRequest (CMemoryException) Error: Out of memory., Request: 107
all in the last few days.
We just had a moment where it had seemed to have locked up again, but after a few minutes it carried on. I had a look at the log since the re-start and all it had was this:
01/20/2012 14:09:21 Start: Initializing global settings.
01/20/2012 14:09:21 End: Initializing global settings.
01/20/2012 14:13:58 Start: Initializing global settings.
01/20/2012 14:13:58 End: Initializing global settings.
01/20/2012 14:52:16 Start: Initializing global settings.
01/20/2012 14:52:16 End: Initializing global settings.
01/20/2012 14:53:58 Start: Initializing global settings.
01/20/2012 14:53:58 End: Initializing global settings.
Which seems to be fairly normal, although I don’t really know what those lines mean either.
Looking on the server whilst the vault appeared to be locked up, there didn’t seem to be anything swallowing resources, the CPU was ticking along below 25% and although the server is only 32bit and 2Gb RAM, the RAM usage was a total of about 1Gb and there is about 31Gb free storage space.
Any ideas what could be up?
We’ve been having some problems with our PDM here today. We are running Workgroup PDM with SolidWorks 2011.
This morning a couple of times SolidWorks would seem to hang for a few seconds when trying to do anything with the vault, then late morning one by one peoples machines completely locked up.
I stopped and restarted the vault service and after the tree rebuild everything seemed fine. (Is there any way to stop it doing the rebuild by the way, it takes an hour and a half?)
Looking on the log file for the vault, there are a few lines that look like this:
pdmwRequestHandler:
rocessRequest (CMemoryException) Error: Out of memory., Request: 107all in the last few days.
We just had a moment where it had seemed to have locked up again, but after a few minutes it carried on. I had a look at the log since the re-start and all it had was this:
01/20/2012 14:09:21 Start: Initializing global settings.
01/20/2012 14:09:21 End: Initializing global settings.
01/20/2012 14:13:58 Start: Initializing global settings.
01/20/2012 14:13:58 End: Initializing global settings.
01/20/2012 14:52:16 Start: Initializing global settings.
01/20/2012 14:52:16 End: Initializing global settings.
01/20/2012 14:53:58 Start: Initializing global settings.
01/20/2012 14:53:58 End: Initializing global settings.
Which seems to be fairly normal, although I don’t really know what those lines mean either.
Looking on the server whilst the vault appeared to be locked up, there didn’t seem to be anything swallowing resources, the CPU was ticking along below 25% and although the server is only 32bit and 2Gb RAM, the RAM usage was a total of about 1Gb and there is about 31Gb free storage space.
Any ideas what could be up?
