Runtime error 217 at 00048C3B

[Gustavo]

Hi Glenn,
Getting an error when I start DesktopInfo for the first time in a computer: “Runtime error 217 at 00048C3B”.

DesktopInfo version: 1.10.2
Windows version: Windows Server 2016 full patched
.ini and .log files are not created

The program runs without any problem in other Windows Server 2016 computers. Any idea what could it be?
Thanks in advance, and thanks for your efforts and software.
Gr.,
Gustavo

[GlennKeymaster]

Greetings,

Switch on log-level=debug in the ini file while testing.

Does it throw the error as soon as it runs? Is there a full or partial display?

Try disabling items in the ini file until it stops throwing the error.

If you get a log file with the errors, post it here.

Cheers

[Gustavo]

Hi Glenn,
No success, no log file generated, no partial display, nothing, just direct the error window immediately after start. For my feeling, the software starts directly getting the error, and it has no chance to event start logging. Worst of that, normally, when the program starts, it creates a working copy of the desktopinfo-sample.ini (if I understand it good), but this also doesn’t happen. I know it is a hard one, and most probably a kind of conflict somewhere in this server, because it works flawless in other similar servers, but I think it is also an interesting one to solve. Let me know if you want to run any kind of debugging tool to try to trace the problem. Unfortunately, I cannot give you access to the server, but for the rest, most probably I can run other software to help if necessary.

Thanks,
Gustavo

[Gustavo]

Hi. If it helps, a dump of the error window in http://www.gavd.net/servers/files/images/2018/desktopinfoerror01.png
Gr,
Gustavo

[GlennKeymaster]

are all the servers the same build of Windows?

[Gustavo]

Yes, they are. All of them virtualized and full patched.

[GlennKeymaster]

Ok. I guess there must be some difference because one behaves differently to the others.

Error 217 is often associated with problems with static linking of Windows DLLs. I’ve come across this issue in a couple of places recently. Let’s see if the next release solves your problem.

[Gustavo]

Fair enough for me. Thanks for your efforts. If I can help in any way, let me know. Looking forward for the new version.

[ThePCPro]

Good Evening,
I am having the same issue with the Error 217 on only one workstation of 10 all built the same. Win 10 with all same updates. Have tried older and latest builds and all do the same. “Runtime error 217 at 00048F03” , I have noticed the last 3 digits will be different depending on the version of DI.

[GlennKeymaster]

I haven’t seen this for a while now. I’ve done a lot of testing on 1803, not so much on 1809. what build of windows are you running? can you give me a rundown of which runtime error address appears in which version of DTI. i’ll see if i can make it match up with the code. also are you using a customised ini file?

[ThePCPro]

Hello again Glenn,
Thanks for the quick reply. I ran the tests again to give you the information requested.
My current Windows 10 build on all workstations is 1803.
Using DTI version 1.5.1.874 the runtime error is 217 at 00045848
Using DTI version 1.12.0.2094 the runtime error is 217 at 00048F03
I know the first version is a bit old, but it’s what I’ve been using till this happened. The only reason for downloading the new version was in case the old version was the cause. Currently the 9 other workstations are still running the older version just fine.
Yes I do use a custom config file, but for these tests I used the example included in the original zip file
Thanks again for the help and the great app.

[ThePCPro]

Hello again,
Just wondering if there is any update or if you are needing more information.
Thanks again.

[GlennKeymaster]

no news. I can’t reproduce this problem so I’m just poking around looking for ideas. The runtime error address took me nowhere.

There may be some external interference. Are you running with admin privileges? Try temporarily disabling your AV before running DTI. Try doing a clean start by disabling startup programs and services in msconfig.

[ThePCPro]

Hello,
Thanks for the reply. I have tried both Admin and basic user, same result. I also tried disabling my AV with no success. I agree there is most likely an outside influence I just cant isolate what that might be. I will try your suggestion of a clean start next. If it could help you, I can convert the problem PC to a VM and set up for your remote access to play around. Since you can’t reproduce the issue this would allow you to see it first hand and since it would be a clone you can be aggressive with testing.
Thank you for your help.

[GlennKeymaster]

That could be useful.

[PP1Participant]

Dear Glenn
I’m using Desktop Info on a Terminal Server environment. I need the client via WMI query. The variant with the variable is not usable because it is not updated.

Thanks
Peter P.

[PP1Participant]

I’m using Desktop Info on a Terminal Server environment. I need the clientname via WMI query. The variant with the variable is not usable because it is not updated.

[Author]

Posts