Forum Discussion

jkrolczy's avatar
jkrolczy
Regular Contributor
5 years ago
Solved

SoapUI Workspace opens with all Projects CLOSED/ REMOTE and not accessible

All,

 

My issue has to be a setting somewhere that I cannot find.

 

I have 2 valid SoapUI workspaces that I can open.

 

1 open correctly and is usable.

 

The other opens up, both all the Projects are all grayed out and unaccessible.

Trying to open one will asked for a Remote URL?

 

If I save\close the Workspace\Projects, the xxxxx Workspace.xml file's syntax is as such for all the projects:

 

<con:project type="REMOTE" status="CLOSED" name="Authorization

  <con:project type="REMOTE" status="CLOSED" name="Search

etc ....

 

Has anyone seen this before and know what I need to do to clear out to change a setting for this 

to not occur anymore.

 

Using SoapUI 5.4.0 currently.

 

 

 

 

 

  • jkrolczy's avatar
    jkrolczy
    5 years ago

    So by the location that the project is checkout and a user clonging the code to a different location, somehow this throws off SoapUI into not finding the files correctly and thus creating the above wierd xml settings.

     

    Now with the user cloing the project out to the correct folder location expected by thye workspace file used by SoapUI, all works as it should.

     

    This was just a weird scenario a user created.

     

     

4 Replies

Sort By
  • jkrolczy's avatar
    jkrolczy
    Regular Contributor
    5 years ago

    I have uninstalled, cleared out Window registry items, did I get all folder locations of saved info ?, 

    I restarted computer, reinstalled SoapUI 5.4.0
    I cloned fresh copy of project code that works for everyone else.

    Started up SoapUI 5.4.0 to this project and same issue still seen.

     

    Theye has to be some hidden settings, configs, etc. saved off somewhere that I am missing in clearing out.

     

    Other porjects opened are not affected like this one.

     

    I want to upgrade to SoapUI 5.5.0 but worried that the hidden issue may carry over to that side as well.

     

    Hopefully someone has seen this issue before and knows how to resolve it.

    • nmrao's avatar
      nmrao
      Champion Level 3
      5 years ago
      Got chance to look into the logs to get some information?

      May be use new workspace / settings file (have backup of existing files, you can the paths in the log files) and move them so that tool creates new files. See if this helps.
      • jkrolczy's avatar
        jkrolczy
        Regular Contributor
        5 years ago

        So by the location that the project is checkout and a user clonging the code to a different location, somehow this throws off SoapUI into not finding the files correctly and thus creating the above wierd xml settings.

         

        Now with the user cloing the project out to the correct folder location expected by thye workspace file used by SoapUI, all works as it should.

         

        This was just a weird scenario a user created.