Hi all,
finally I got the possibility to get dT running on a Terminal Server, by publishing the Agent-Tool itself as TerminalServer-application.
Now I was able to configure an Agent, but I'm getting an error. Following is the Log:
2013-04-05 09:59:33 info [native] dynaTrace Agent injected
2013-04-05 09:59:33 info [native] dynaTrace Bootstrap Agent 4.1.0.2898
2013-04-05 09:59:33 info [native] Using C:/Program Files (x86)/dynaTrace/dynaTrace Agent 4.1.0 as Agent storage
2013-04-05 09:59:33 info [native] Log file at L:\ApplicationLogs\dynaTrace\dynaTrace_12404
2013-04-05 09:59:33 info [native] Trying to connect to mucs800595.dev.munich.munichre.com:9998 for up to 60 seconds
2013-04-05 09:59:33 info [native] Connected successfully
2013-04-05 09:59:33 info [native] Server requests us to use Agent 5.0.0.3772 with a hash of d2f81ff640f554780d905a24ef242ff3
2013-04-05 09:59:33 info [native] Agent already available locally
2013-04-05 09:59:33 info [native] Loading Agent C:/Program Files (x86)/dynaTrace/dynaTrace Agent 4.1.0/agent/downloads/5.0.0.3772/native/windows-x86-32/dtagentcore.dll
2013-04-05 09:59:33 severe [native] DllGetClassObject: %1 is not a valid Win32 application.
Anyone a suggestion about this issue?
Thanks in advance!
Regards,
Denis
Answer by Andreas G. ·
That is interesting. First of all I would open a support ticket.
My gut feeling about this is that DllGetClassObject tries to load our .NET Agent library (dtagentcore.dll). It fails though as it thinks it is not a valid library. Is it possible that your .NET application is a 64bit application? But we try to actually load the 32bit agent dll?
JANUARY 15, 3:00 PM GMT / 10:00 AM ET