hi Edward Bradburn Thank you for your post and for clarifying your Studio version.

I assume that Studio works well in other aspects and this error is directly related to your WS Packages?
Please can you confirm what version of the WS add-in it is that you are working with? 

You can check this by going to: C:\Users\[user name]\AppData\Roaming\SDL\SDL Trados Studio\16\Plugins\Unpacked
Go into the WorldServer folder and open the pluginpackage.manifest.xml file to review the version installed.

I believe you should have 16.9.1821
Lyds

hi Edward Bradburn Thank you for your post and for clarifying your Studio version.

I assume that Studio works well in other aspects and this error is directly related to your WS Packages?
Please can you confirm what version of the WS add-in it is that you are working with? 

You can check this by going to: C:\Users\[user name]\AppData\Roaming\SDL\SDL Trados Studio\16\Plugins\Unpacked
Go into the WorldServer folder and open the pluginpackage.manifest.xml file to review the version installed.

I believe you should have 16.9.1821
Lyds

Hi ,

Many thanks for the rapid response!

Yes, Studio works OK in all other respects, this is related to the ongoing problem I have with WorldServer packages.

Interestingly, the plugin is NOT located at that place on my system, although I can see that the plugin is installed when I click "Plug-ins" in Trados Studio.

I tried reinstalling the plugin to see if that would work.

After reinstalling, everything looks exactly the same: I can see the plugin in Trados but there is nothing in the "16" folder and Trados does NOT show WorldServer packages with the "Open Package" dialog.

HOWEVER, I can use "*" to find all files and then I can indeed open the package.

So ... it sort of works, but it would be great if I did not have to reinstall the plugin every time a service pack comes out... And the "Package Open" dialog should show me WorldServer files, but it does not.

So the workaround seems to be:

1. Every time a Service Pack comes out, reinstall the WorldServer plugin
2. To open a WorldServer file, double-click on the file. If using "Package Open" dialog, use "*" to find "WorldServer" files.

(WorldServer files are associated with Studio by Windows. If I double-click them, I can open them fine. It's just the "Package Open" dialog that does not show them.)

Sincerely,

Ed

Oh yes Edward Bradburn you are correct. As it's a msi it wont be in the folder paths I initially indicated but as you pointed out it is listed under "Plug-ins"

But to answer your questions

Edward Bradburn said:

Every time a Service Pack comes out, reinstall the WorldServer plugin

Due to dependencies and other factors, it is to be expected that when Studio has been updated some plugins would need to be updated also.
Originally WS package support was integrated with Studio, so this upgrade/maintenance had no impact. But in order to keep Studio installers and other components as small and possible we decided to decouple it, given WS package support is not a benefit to all end users.

Edward Bradburn said:

To open a WorldServer file, double-click on the file. If using "Package Open" dialog, use "*" to find "WorldServer" files.

Are you implying that you cant browse and automatically see the packages (format *.wsxz) when in this view?

Lyds

Many thanks for the confirmation, I'll do this from now on.

Actually, I don't use the toolbar much on the Projects page, so I wasn't aware that icon was even there

But if you go to File -> Open Package, you will see that WorldServer packages are not found. That's what I meant.

I'll use the icon instead if I need to, thanks for the tip!

Ed

Oh I see Edward Bradburn

HA! Looks like we both learnt something new . I see that via your method the *.wsxz is not listed


Project View - Home Ribbon would be easier. In the meantime I will feed your method to development as it would make sense to have it listed also, provided a user has the plugin installed.

Lyds 

Thanks for noting the other file open method, !

That would be helpful to anyone using the File dialog.

And yes, a win-win on this issue today, thanks again for your help!

Ed