I have an old server running SQL 2008 R2 Standard and Solidworks Enterprise PDM. I am needing to migrate the vault, and all settings, to the new server which is running SQL 2008 R2 and has a fresh install of the same version (2013 sp2) of Solidworks Enterprise PDM.
I am having difficulty finding documentation on how do do this, or an intuitive method of migrating the vault from Administration.
Any help would be appreciated
Hi John,
I think what you're looking for is covered in the Installation Guide under the "Moving Server Components to Another System" section starting on page 129 of the 2013 guide. The guide is found on my system (where EPDM is installed) under the following directory:
"C:\Program Files\SolidWorks Enterprise PDM\Lang\GB"
I'm assuming it would be in a similar location on yours.
-Matt
Neither C:\Program Files\SolidWorks Enterprise PDM\Lang\GB, or Install DVD: \Support\Guides\GB contains that file. I did a search at the top of both directories with no results. I have administration guide, installation guide, web server guide and whatsnewenterprise only
Try looking in the "Installation Guide.pdf" you just found. It should be covered in the very last chapter.
Thanks Matt, I found it. I have followed the instructions, but I am having issues. When go to Solidworks Enterprise PDM Administration on the new server, click on my vault and enter my admin password, it says that "the speicified vault does not exist on this archive server". The location of the vault is on a different drive letter than the previous server. Launching archive server configuration does nothing. Launching database server configuration presents me with a SQL sa login - after clicking login it does nothing.
How can I point this program to the new location (if thats the issue)
The term archive server conflicts with the fact that I am trying to set this up as a database server per Solidworks terminology. Is this accurate?
I am sorry about my intro questions, I didn't know this software existed until yesterday.
I'm a little confused as to what exactly is going on now with regards to the error messages. I've only been using EPDM for ~1 year, so fortunately I haven't had to migrate to a new server yet.
Reading through the Installation Guide pg. 129, it specifically states "Copy the entire file vault archive folder from the old server to the new server, maintaining the same path." I'm guessing you weren't able to do this if your vault on the new server is on a different drive letter than the previous server.
Since I've never actually performed this procedure, take the following with a grain of salt. You might have to initially keep the same path as the old server and then follow the instructions from the 2013 EPDM online help regarding "Relocating a File Vault Archive":
-Matt
John,
On new server you must maintain the same location for archive server files. Ex on old server was D:\Vault.. on the new server must be D:\Vault.
I uninstalled PDM completely, and changed drive letters to match the old server, then re-installed to match the file path from the old server exactly. I followed the steps according to the Installation Guide PDF. When signing into the vault via the PDM client, I get:
Could not log in to the database "NAME OF THE SQL DATABASE CORRESPONDING TO THE VAULT" on server "THIS LOCAL SERVER". Cause: The specified vault does not exist on this archive server.
I also get this in the background:
Could not (un)register module "LogFile.dll"! Check access rights to the HKEY_CURRENT_USER\Software\Classes registry section.
Is there something I am missing beyond the directions?
the error message is common and only appears once.
it looks like you did not keep the instance of SQL the same or you did not restore the conisiomasterdb to your new server.
Kip Speck,
I did restore the conisiomasterdb to the new server. However, you are correct in that the new server's SQL instance name is different. However, I am having trouble finding a way to modify that value from the PDM software's point of view to reflect the new instance name.
John,
This data where is stored in the SQL db for the vault and the Client Registry.
Please do not taske this the wrong way, but you should really get somene involved that knows the software, eiter your VAR or call us. I am really not trying to sales pitch you, but you should not be tinkering with this unless you know what you are doing.
I can tell you that our rate is 150.00 an hour and I would be happy to get you back on your feet wit this.
If you changed the Instance name on your SQL install, you will have additional items to fix with the clients. How many client computers is this installed on?
Kip Speck
the term "server" can refer to either a physical machine or a service. In the case of epdm you have two services acting as servers, not physical but software.
once the archive server has been launched you will see an icon in the system trey, next to the clock right mouse click it to open it.
the database service interface is just for you to manage the name and password that epdm uses to access SQL.
if this is a production environemt and you are down, you should either contact your var to get this resolved.
or
you can contact us at stratus-x.
the resolution to this is fairly straight forward if you know the software.
John,
At this point it sounds like the registry information is no longer valid. If you need this resolved immediatly I would suggest that you either contact your VAR (Reseller) immediately so that they can you you back on your feet.
Or you can contact us at Stratus-X and we can get you going as well.
Please do not try and "Hack" out a solution, you could make things worse.
Kip Speck
Checkout the very last chapter in the Installation guide [Install DVD: \Support\Guides\GB] entitiled: "Moving Server Components to Another System"