SOTI Pulse Logo

15.1.3 Build 1021 -> 15.3.0 Build 6713 MCDeplSvr.exe not starting anymore

Solved
R
Remy
Zollner Elektronik AG

Hello,

After the update we found this strange log:

2021-03-11 17:31:50,290 (0x00000908) [ERROR] [CMyService::ServiceMain] Error starting Deployment Server Extensions: Newtonsoft.Json.JsonReaderException: Input string '697CDE57CF56FBC5049CDE5FBC18E7CD168FCC48FB46F9955F96D319F358E98133A8E939C077CDB925AAAF71844AD8ED2DF5AF7D8E3A9FAB739AE52ED37AD3E646C99617F42982DB03E69E78A81BB5935CD3D71FB803A3945493DF64A52BB29B61E2AB6187319EA368E0A34F832B82B66BF2B127C4369DB274B3FF58852F95A1880A40D734902E648E1B44DF2A98475E8A04428A6CC62D1D9F0A51816BAA072F' is not a valid number. Path '', line 1, position 320.
at Newtonsoft.Json.JsonTextReader.ParseReadNumber(ReadType readType, Char firstChar, Int32 initialPosition)
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
at Soti.MobiControl.Settings.SerializationHelper.GetDeserializeObject[T](String serializedValue)
at Soti.MobiControl.Settings.SettingsService.Decrypt(String encryptedSetting)
at Soti.MobiControl.Settings.SettingsService.GetSetting[T](String feature, String setting, CachingOptions cachingOptions, ObfuscationOption obfuscationOption, T defaultValue)
at Soti.MobiControl.CoreFeatures.Implementation.GlobalProxy.ProxySettingManagementService.GetProxySetting()
at Soti.MobiControl.CoreFeatures.Implementation.GlobalProxy.ProxyService.UpdateGlobalProxy()
at Soti.MobiControl.DeploymentServerExtensions.DeploymentServerExtensionsHost.Start()
at CMyService.ServiceMain(CMyService* , UInt32 dwArgc, Char** lpszArgv)

and from here there is no way to get the "Deployment Server/Deployment Server Extensions &  Managment Service" in a "running state".

4 years ago
SOTI MobiControl
ANSWERS
J
JCMOD@SOTI
4 years ago

Hi Remy,

If your DS / DSE is not operational, I suggest you raise a Support Case through support@soti.net / support.eu@soti.net. Alternatively, you can telephone Technical Support and receive assistance promptly.

Regarding the issue at hand. The difference between 15.1.3 and 15.3 is quite a lot, I suggest you double-check the System Requirements page for 15.3 and ensure your environment meets the specification detailed within.

If the above is fruitless, ensure you uninstall MobiControl via Control Panel. Double-check the MobiControl directory is empty in Program Files then perform a fresh install via running the installer exe.

Source: https://www.soti.net/mc/help/v15.3/en/setup/installing/system_requirements.html#installing_system_requirements

Let us know how it goes Remy, if you need clarification or have any questions feel free to reach out. If this helped resolve the issue, please mark this post as the solution.

Regards,

Solution
RC
Raymond Chan Diamond Contributor
4 years ago (edited 4 years ago)

Try running the v15.3 installation .exe file again on your already upgraded server instance.

R
Remy
4 years ago

Hi Raymond,

I've already tried that...also after an uninstall and a new install we have the same problem.

Do we "omit something"?

R
Remy
4 years ago

Is this a "bug" in the JSON deserialization process?

R
Remy
4 years ago

Hi JCMOD,

Quick update: in the end it was a DB issue!

HR
Hubert Reininger (FIELDWORX)
4 years ago

Hello everyone!

We experienced the same issue when upgrading a customer´s instance from 15.1.2 to 15.4.1 ...

The problem was indeed a database issue (as already mentioned by Remy):
After the upgrade, the GlobalProxy-Settings entry couldn´t be decrypted correctly anymore, which causes the following JSON-Deserializer methods to fail. This internal exception prevents the Deployment Server Service from starting up.

To SOLVE this issue you need to update the GlobalProxy.Setting entry in table 'Settings' with NULL value.
The DeplSrv Service will start again, and in the new UI you can enter the GlobalProxy Settings again (in case that you need some).

Hope that helps...

Regards,
Hubert@FWX

Similar Discussions