Notifications
Clear all
Topic starter
Does anyone know of a way to enable DEBUG-level logging for the LinkLogicDTS service? I'm having some trouble getting the service to run in my test environment. Thanks.
Posted : May 11, 2015 1:07 pm
I assume you're specifically talking about using the app as a service?
There is an application error log at C:\Program Files (x86)\Centricity Practice Solution\Client\mlerrlog.txt.
Service apps should at least log start and stop to the Windows system log also.
I highly recommend NSSM instead of srvany for manually deployed services. https://nssm.cc/.
Posted : May 12, 2015 5:31 am
Have you run DTS as a program from the console rather than a service successfully?
Posted : May 13, 2015 3:42 am
Topic starter
SLHV - I was trying to run the app as a service, yes. I do not have a log file in the Client folder named mlerrorlog.txt. The service actually "starts", and remains in a Started state according to Windows, but in my CPS client under Chart > LinkLogic > DTS Monitor, no DTS Stations are visible. And my export task isn't working.
David - I have not managed to successfully run it from the console. When attempting to do so I get an error dialog "DTS Startup Error: The Data Transfer Station is not supported under WinFrame." If I could get that working it definitely might be helpful. This is the command I am attempting to use, except with my actual sql server name:
C:\...\Client>ml3dts.exe -u "http://sqlservername:9080/centricityps/cps/" Instance=1
Posted : May 13, 2015 7:51 am
Justin, you can't run the DTS application via RDP. You have to be at the physical keyboard if it is a physical server and if it is virtual, you have to be using whatever Virtual Server management application your virtual environment uses to view the console.
Posted : May 13, 2015 9:19 am
Justin I used to use VNC or LogMeInfor remote console access on DTS. Now it's a VM so console is through VMWare.
David is right. Get it running as an interactive app first. Then switch to the service.
Posted : May 13, 2015 9:29 am
Topic starter
Ah, thank you both. It didn't occur to me it might be restricted to not run in an RDP session. I'll try again from the console and will report back. Is my command line still correct, particularly the -u parameter?
Posted : May 14, 2015 8:32 am
The command line looks correct. My notes show "instance" as all lower case. I don't know if it is case sensitive. I doubt it.
Posted : May 14, 2015 8:40 am
Topic starter
Okay I have console access. Attempting to run ml3dts.exe from the command line shows me a splash screen, then the message "Cannot run DTS. This station is not configured as a LinkLogic Data Transfer Station."
When I look at the L3DTS table, the contents appear to be the same as my production system except with the test environment server name instead of the production server name.
Posted : May 18, 2015 7:49 am
From our internal KB:
Not configured as DTS station on startup
This may indicate that the section DTS # is missing in the EMR.INI file on the DTS workstation.
For example, here is the relevant section in our EMR.INI file. Our server name is APP4. The DTS instance is 1. The L3ID is arbitrary. Make up a number and try it.
[APP4 DTS 1]
CENTRICITYPM_L3ID=155
DTSDesc=app4
Posted : May 18, 2015 8:19 am
Topic starter
Awesome, that was it. Thank you. That's a nice internal KB you have there. I can now run it from the console and as a service.
To supplement your records, I think the two lines in the EMR.ini file correspond to a row in the L3DTS table. For example, in the L3DTS table in my production system, the row that appears to be the relevant DTS station has a value in the DTS column of 20 and a value in the DESCRIPTION column of "DTS". Which matches my ini file:
[APPSERVERNAME DTS 1]
CENTRICITYPS_L3ID=20
DTSDesc=DTS
Thanks again.
Posted : May 19, 2015 7:34 am
Thanks for the follow-up. I checked our L3DTS table and you are correct. The DTS value matches the L3ID value. I don't know if I changed the value in EMR.INI and restarted it if it would update in the L3DTS table. I'm not interested enough to experiment with it, but I will update our notes. Thanks.
On a side note, we use mediawiki for our KB. Easy to use, edit, and document things.
Posted : May 19, 2015 8:45 am
Topic starter
Good to hear a review for mediawiki. We have an instance of dokuwiki, but of course its utility is directly correlated to the amount of energy people put into it.
Posted : May 19, 2015 8:57 am
