Hello,
I have an issue upgrading DataMiner to the 10.2 branch.
The 10.2.1 Feature Release works, but anything after this, including the Main Release do not.
The issue is always the same. The upgrade completes without any errors until DataMiner should start again. At this point nothing happens any more.
Looking into the Log-Files I can see the the issue seems to be communicating with SLNet, as I can see timeout messages in an infinite loop here.
Could this be an issue with an non English Windows? I have for a while now had the issue that I need to manually add the DCOM Config Permissions for SLASPConnection, could this be something similar?
So far the I tried the upgrade on 4 DMAs, only one worked.
Best Regards
Hi Robert, some users reported a similar issue after upgrading to 10.2 on hosts running localized versions of windows (in this case, configured to use the German language during the installation). For example, DataMiner was searching for NT-AUTHORITY\System user whereas the name of the same user on a German host is NT-AUTORITÄT\SYSTEM.
Several hotfixes have been tested internally, one of which is already merged in 10.2.0 CU2 (main release).
Could you please upgrade your demo/development platform to the latest build and let us know if it fixes the issue?
Thanks!
Hi Robert,
this issue doesn't ring a bell, the only thing i can think of is that the services aren't properly registered again after the upgrade, you can do this manually again to verify if this is the root cause:
-Stop DataMiner
-Run “C:\Skyline DataMiner\Tools\UnRegister DataMiner.bat” as admin
-Run “C:\Skyline DataMiner\Tools\UnRegister dll's of DataMiner.bat” as admin
-Run “C:\Skyline DataMiner\Tools\Register dll's of DataMiner (silent).bat” as admin
-Run “C:\Skyline DataMiner\Tools\Register DataMiner as Service.bat” as admin
-Start DataMiner
If this doesn't solve it i would definitely register a high priority support ticket to get this investigated asap
Hello Marlies,
I tried it, but that was not the issue.
I will open a Ticket then.
Best Regards,
Robert
Hello Ciprian,
yes, the latest build fixes the issue.
Thank you again for your support!