WebGIS Discussions

Need a push in the right direction when configuring WebMap, Portal or SDI services? Looking for hints and tips, or just looking for Ideas and information? The WebGIS discussion board is where you start those discussions, connect and share information.
Showing results for 
Search instead for 
Do you mean 
Reply
Contributor
Posts: 24
Registered: ‎10-05-2016

Backend version is no compatible with current application

Hi,

with the latest version of Mobile MapWorks Advantage (16.5.0) this message appears when I configure my MapWorks Server: "Backend version is no compatible with current application". My backend version is "Mobile SDK 16.0.2.6". What's the problem?

 

Thanks!

 

Sergi Gumà

Contributor
Posts: 24
Registered: ‎10-05-2016

Re: Backend version is no compatible with current application

Hi,

Does anyone know the solution to this problem?

Is there a new backend version that has not been released?

 

 

Thanks!

 

Sergi Gumà

 

Staff
Posts: 25
Registered: ‎01-18-2016

Re: Backend version is no compatible with current application

Hi Sergi

 

We have to update our App becasue is not fully compatibile with the 16.05 MMW Installer. 

We plan do this as soon as possible.

 

Best regards

Dominik

Contributor
Posts: 24
Registered: ‎10-05-2016

Re: Backend version is no compatible with current application

Ok, thanks!

 

 

Sergi Gumà

Member
Posts: 1
Registered: ‎10-19-2018

Backend version is no compatible with current application

Hi,

with the latest version of Mobile MapWorks Advantage (16.5.8) this message appears when I configure my MapWorks Server: "Backend version is no compatible with current application". My backend version is "Mobile SDK 16.0.2.6". CAn you solved me this situation???

 

Thanks!

 

Sergi Gumà

Technical Evangelist
Posts: 184
Registered: ‎07-30-2015

Re: Backend version is no compatible with current application

SDK 16.5.0 is comaptible only with 16.5 MMW services.

 

It means that in order to use the SDK, the MMW installer must be used in order to install the services.

Highlighted
Staff
Posts: 332
Registered: ‎02-04-2016

Re: Backend version is no compatible with current application

[ Edited ]

Hi All,

 

With MMW 16.5 installed, there is no need to have mmwsdk copied to the server (unless you needs mmwsdk, then please make sure the sdk version is 16.5), MMW 16.5 delivers 3 IIS Applications under the "C:\inetpub\wwwroot", namely mmw, mmwBlobService and mmwSyncService, and they are all ready to be used (http://server/mmw will by default pointing to C:\inetpub\wwwroot\mmw\ConfigurationFiles\workspace_config_test.json).

 

No more "Backend version is not compatible..." warning.

 

Regards,

 

Frank

 

New Contributor
Posts: 3
Registered: ‎09-27-2019

Re: Backend version is no compatible with current application


@fmak wrote:

Hi All,

 

With MMW 16.5 installed, there is no need to have mmwsdk copied to the server (unless you needs mmwsdk, then please make sure the sdk version is 16.5), MMW 16.5 delivers 3 IIS Applications under the "C:\inetpub\wwwroot", namely mmw, mmwBlobService and mmwSyncService, and they are all ready to be used (http://server/mmw will by default pointing to C:\inetpub\wwwroot\mmw\ConfigurationFiles\workspace_config_test.json).

 

No more "Backend version is not compatible..." warning.

 

Regards,

 

Frank

 


Does anyone know the solution to this problem?

Is there a new backend version that has not been released?

Staff
Posts: 332
Registered: ‎02-04-2016

Re: Backend version is no compatible with current application

This issue usually happens on a server with earlier (pre-16.5) MMW version, with users on v16.5 MMW Adv mobile app pointing/using the outdated mmw backend/url.  If you are on v16.5, then your mmw url should be http://server/mmw , and physically located at C:\inetpub\wwwroot\mmw.

 

The solution is installing/configuring v16.5 MMW Adv on the server.