Hi,
We are planning to do a migration from MKS to SVN and we have found a svnimporter from Polarion and using that to do an import.
I have a linux 64 bit machine and trying to installed 32 bit MKS Integrity client 2009 and it fails to invoke si and gives an error as below. Can you please help?
Although PATH variable will be set - it would continue to give this error and we cannot extract any code as si does not work.
07:32:11,586 [stderr] INFO Exec:84 - /home/vagrant/MKS/IntegrityClient/bin/si: Attempt to launch MKS Integrity Client Timed out. To solve this please try the following:
07:32:11,587 [stderr] INFO Exec:84 - - Verify that the user you are logged in as has read and write permissions to the Integrity Client install directory.
07:32:11,587 [stderr] INFO Exec:84 - - Make sure the Integrity Client install directory is the very first entry in the path.
I have actually set the PATH variable and have tried every possible way. Can you please help?
Thanks
Shalini
Solved! Go to Solution.
Hi Shalini,
the link below leads to a document about trouble shooting for Integrity Client startup problems under LINUX:
https://support.ptc.com/appserver/cs/view/case_solution.jsp?n=CS123560&lang=en
(see also attachment if you do not have access to this page).
Maybe this can help you to find the cause of your problem.
And what about the message
07:32:11,587 [stderr] INFO Exec:84 - - Verify that the user you are logged in as has read and write permissions to the Integrity Client install directory.
Do you have the read and write permission within the complete Integrity Client install directoy including all sub-directories?
Regards,
Peter
Hi Shalini,
the link below leads to a document about trouble shooting for Integrity Client startup problems under LINUX:
https://support.ptc.com/appserver/cs/view/case_solution.jsp?n=CS123560&lang=en
(see also attachment if you do not have access to this page).
Maybe this can help you to find the cause of your problem.
And what about the message
07:32:11,587 [stderr] INFO Exec:84 - - Verify that the user you are logged in as has read and write permissions to the Integrity Client install directory.
Do you have the read and write permission within the complete Integrity Client install directoy including all sub-directories?
Regards,
Peter
Peter's article is probably the correct first step.
You might also find these two Linux client specific articles helpful:
Regards,
Kael