VSS import unhandled exception

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
sly-fly
Posts: 3
Joined: Fri Jun 25, 2004 3:15 pm

VSS import unhandled exception

Post by sly-fly » Fri Jun 25, 2004 3:24 pm

I am wondering if someone knows why, each time i am trying to import a 4 Gig DB with about 20 labels it gives me an unhandled exception during export, Couldn't get process information from remote machine?

I have done many import so far without too much problem, i've done all i had to do in the config to set parameters to a higher value.

I had about 15 DB to convert and only those who would take about 36h to do are giving me a hard time.

Thank you and sorry for my English, 2nd spoken language :D

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Fri Jun 25, 2004 4:30 pm

I think that the following things would be helpful.

1 A screenshot of the error message
2. Where do you get in the import process? Has the prescan completed? Do some files get imported?
3. Does your import log say anything? It's located in c:\program files\sourcegear\VSS Import Tool

Thanks!

sly-fly
Posts: 3
Joined: Fri Jun 25, 2004 3:15 pm

Post by sly-fly » Fri Jun 25, 2004 7:59 pm

Ok yeah sorry !! Here are the details

The pre-scan work just fine
It is when i do click on next to start the importation itself, then it take 1 second and says importation sucessful with 0 error but then when i go into the import log i see that error i told you above and more like the beginning end ending of the importation wich is the same and that beautiful string:

Unhandled exception during export: Could't get process information from remote machine.
Trace: at System.Diagnostics.NtProcessManager.GetProcessInfos(PerformanceCounterLib library)
at System.Diagnostics.NtProcessManager.GetProcessInfos(String machineName,Boolean isRemoteMachine)
at System.Diagnostics.ProcessManager.GetProcessInfos(String machineName)
at System.Diagnostics.Process.EnsureState(State state)
at System.Diagnostics.Process.get_PrivateMemorySize()
at VSSImport.WizardForm.b(Hashtable A_0)
at VSSImport.WizardForm.e()
Logged out of the vault server.

there it is

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Post by jeremy_sg » Sat Jun 26, 2004 6:55 am

The import does the getPrivateMemorySize to check for memory leaks. email me (using the button below this post), and when I get in on Monday I will send you a build which does not call getPrivateMemorySize.

Post Reply