question

hietran avatar image
hietran asked hietran posted

Could not launch the product because the specified workspace cannot be created. - ERROR msg

Hi,

 

"Could not launch the product because the specified workspace cannot be created.  The specified workspace directory is either invalid or read-only. - ERROR msg"

 

 

I get the above error message when i launch itest3.4.4 on my laptop (xp).  But when I launch the same version on my linux box (centos) and pointing to the same workspace, it works perfectly fine.  Does anybody know what is wrong?

 

thanks,

Hiep

iTestinstallation - licensing
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
ZhongyuZ avatar image
ZhongyuZ answered ZhongyuZ posted

It seems this is a system issue. Can you double check whether you have write permission in the specified workspace folder? Or you can try to use a different workspace directory.

5 comments
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

hietran avatar image hietran commented ·

Hi,

 

I cannot change workspace because when i get that error message, itest will close after I press OK on the error message. 

 

thanks,

Hiep

0 Likes 0 ·
IvanS avatar image IvanS hietran commented ·

If workspace is corrupted and you want to use projects from it you can create new workspace and import projects from the old one (using File->Import...->General->Existing Projects into Workspace)

0 Likes 0 ·
KumarS avatar image KumarS IvanS commented ·

Ivan's solution is better. It is not a good idea to share a workspace folder across operating systems. The root of workspace folder contains .metadata folder where iTest stores files for its proper functioning and some of these are per operating system. You need to create different workspaces for different operating systems.

 

The correct way to share project files across operating systems is to store the data in a Source Control repository and have a copy of the projects on each one of your machines.

 

Another sub-optimal way is to create a local workspace folder and then import projects from a shared location. In this case, you can choose to copy the projects or work on projects on the remote shared location. Copying will cause you trouble because after you make your changes, you will have to copy the changes back to shared location (I am assuming they were in shared location because you were sharing these projects across users) and that can cause conflict among users if multiple users are modifying the files at the same time. Sharing the projects will again cause the problem if multiple users are modifying these files at the same time.

 

The best workflow is to really use a Source Control system for sharing. Then you get  a local copy per operating system and when you are done modifying, you can check your changes into the source control system. You can then checkout changes on another computer and continue working from there.

0 Likes 0 ·
GuanghongY avatar image GuanghongY IvanS commented ·

I think Hietran's problem is that iTest is using the workspace as a default workspace and so he won't be able to switch the workspace. You can try either remove the configurations so as to let iTest ask you the workspace (the configuration files are in your user_home\.iTestConfiguration_xx where xx is the version number; or you can try to re-install iTest and choose a different and accessible path as the default workspace.

0 Likes 0 ·
hietran avatar image hietran GuanghongY commented ·

thanks all for your suggestion.

 

this seems to work, delete some of the workspace paths in the files below. 

C:\Documents and Settings\hietran\.iTestConfiguration_3.4\.settings\org.eclipse.ui.ide.prefs

 

thanks,

Hiep

 

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.