Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 5150 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Hello,

What should be the required version of the FmServiceWrapper on FMSWPE?

The Master FMS is a V10.0.2.206 on Window Server 2008 and IIS

Actually We have a FMSWPE (FmServiceWrapper)

File version = 10.0.1.54

Product version = 10.0.1.1

And Date Modified = 11/26/2008

Also on Window Server 2008 and IIs

Is that correct?

Thank you

Alain

Posted

Hi,

Yes it's a two machine deployement.

I'm verifying the version because we had experimented unexpected crash of the server, something like "illegal DLL access".

In paralelle to this we found window trying to decompress an update and doesn't succeed, making a warning. I don't know if it's related.We had disconnected the automated update.

We try to install FMSAV11 on two machines but we still experiment a misconnection between the WPE and the MASTER under Window Server 2008 SP2.

The MASTER doesn't reconize the WPE machine. We are thinking to deploy it only on one machine.

Al of our clients users are in V10 or V8.03.

Thank you

Alain

Posted

It was installed at with the same installer, so I guess it's up-to-date.

But if by any chance somebody have the correct Version number for FMServiceWrapper I will appreciate.

Thank you for your help, I appreciate it very much.

Have a good evening.

Alain

Posted

Only trust the version number returned in the admin console. Keeping a list of correct version numbers for each component because not all of them might get updated for each version ref.

This topic is 5150 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.