Discussion:
ibmdi.log still empty
(too old to reply)
d***@gmail.com
2019-07-16 12:38:32 UTC
Permalink
Hello,

I moved my TDI instance from Windows 2008R2 to Windows 2016 Server.
I made a fresh install and import ALs et server settings.
All ALs has been working fine for a month but the log files are still empty. The ALs were installed as a Windows Service and with 'LocalService' profil.

If I ran ALs in the configuration editor, all messages are printed in the window.

I'm using TDI 7.1.1.8!

Olivier
d***@gmail.com
2019-07-16 14:17:25 UTC
Permalink
Post by d***@gmail.com
Hello,
I moved my TDI instance from Windows 2008R2 to Windows 2016 Server.
I made a fresh install and import ALs et server settings.
All ALs has been working fine for a month but the log files are still empty. The ALs were installed as a Windows Service and with 'LocalService' profil.
If I ran ALs in the configuration editor, all messages are printed in the window.
I'm using TDI 7.1.1.8!
Olivier
The log4j.properties was missing in the solution directory. All work fine since I copied it from w32_service !

Olivier
Eddie Hartman
2019-07-17 14:01:01 UTC
Permalink
Post by d***@gmail.com
Post by d***@gmail.com
Hello,
I moved my TDI instance from Windows 2008R2 to Windows 2016 Server.
I made a fresh install and import ALs et server settings.
All ALs has been working fine for a month but the log files are still empty. The ALs were installed as a Windows Service and with 'LocalService' profil.
If I ran ALs in the configuration editor, all messages are printed in the window.
I'm using TDI 7.1.1.8!
Olivier
The log4j.properties was missing in the solution directory. All work fine since I copied it from w32_service !
Olivier
Remember, Olivier, that whenever you use the ibmdiservice command to create a Windows Service that you do this from your Solution Directory. And if you use relative paths and put all support files in your SolDir and sub-folders, your solutions becomes readily moveable :)

/Eddie

Loading...