Exception 'NoProductionLogic' caught

[Former Member]

I do not understand. In the test device published a new version of the software. I'm trying to publish a working version (the older). In the folder "Logs" I see the following message

2015/08/31 08: 39: 52.655: + Thread = 2720

2015/08/31 08: 39: 52.655: + Thread Pool = ANGEL Front End

2015/08/31 08: 39: 52.655: + WorkFunction = 000000005663EED0

2015/08/31 08: 39: 52.655: + ANGEL Connection = 10.206.254.34: 1028

2015/08/31 08: 39: 52.655: + ANGEL Vine = 2011034691

2015/08/31 08: 39: 52.655: + User = s.krushelnitskiy

2015/08/31 08: 39: 52.655: + Server = Agentry

2015/08/31 08: 39: 52.655: Received Client App Version Info: version 2.0 mod 277

2015/08/31 08: 39: 52.655: Load App: Client has app version 2.0 mod 277

2015/08/31 08: 39: 52.655: Load App: Production mode

2015/08/31 08: 39: 52.655: Skipping localized definition check because the locale is not specified.

2015/08/31 08: 39: 52.655: Looking for base definitions

2015/08/31 08: 39: 52.655: Found base definitions

2015/08/31 08: 39: 52.655: No matching definition found

2015/08/31 08: 39: 52.655: No Production Business logic

2015/08/31 08: 39: 52.655: *** Exception 'NoProductionLogic' caught, see events.log

In events.log writes

08/31/2015 8:39:52, 1, 20, 3, Thr 2720, No production logic, agent \ AgentUserOSManager.cpp # 2647: ProductionUserOSManager :: setAppVersion

But when tested by ATE Projects run correctly. The current version of the project - 2.1 18.

[Former Member · Accepted solution]

No Production logic means the version the client is using is not loaded by the server.  When you look in the application\production folder do you see version "2.1.18"?

Stephen

[Former Member · Accepted solution]

Yes. In application \ production version "2.1.18". How do I get the device to download this version , rather than trying to upgrade to 2.0.277

[bill_froelich · Accepted solution]

The versions are the other way around.  The device is currently running version 2.0.277 but the current version on the server is 2.1.18.  However, the device needs to have access to the version currently on the device in order to process any pending transactions before upgrading automatically to the latest available version.

You have two options here. 

1. Redeploy version 2.0.277 to the server so any devices running that version can sync and upgrade to 2.1.18
2. Reset the device (you will lose any pending transactions that have not been sync'd yet) and it will do an initial download of the latest version 2.1.18

--Bill

[Former Member · Accepted solution]

Thank you. I chose the second option. Now I understand the principle of operation.