Lessons Learned

This page contains some solutions to situations we've encountered during the life of Truxton

Administrative

Load.exe Disappears From Install Folder

When Truxton is processing incoming media, it may (probably will) encounter malware. When Load.exe (or maybe EMail.exe) writes this malware to the depot file, the process might get quarantined by your virus scanner. When this happens, depending on your settings, the executable files will disappear from the installation folder.

You can prevent this by disabling virus protection on loader machines or configuring them to exempt Truxton's processes and folders from scanning.

Delete Folder Structure

When expanding PST files, sometimes folders can be left behind. Usually, they will contain filenames that Windows thinks doesn't exist. To delete the folder, use the "escaped" name which tells Windows to not think too hard when interpreting the filename.

rmdir /s /q \\?\H:\Trux\Truxton\55E3AF7109F30CA7

Deleting Folder Structure 2

Sometimes, when expanding archives, folder ownership will be reset. To delete them, you must first take ownership and reset the security.

takeown /a /r /d Y /f D:\Temp
icacls D:\Temp /t /grant administrators:F
rmdir /S /Q D:\Temp
mkdir D:\Temp

Killing Processes

If you have mistakenly started loading a load list, you can stop the Truxton service but the Load.exe processes will still be running.

taskkill /fi "IMAGENAME eq Load.exe" /F

Debugging PostgreSQL

Sorry, too many clients already

We have seen PostgreSQL run out of connections and die (yes, the entire process tree collapses). It does not matter how many connections it is configured to support. To help debug this, set the following three items in postgresql.conf file:

log_connections = on
log_disconnections = on
log_hostname = off

Debugging ETLs

Application is in Break Mode

"Application is in Break Mode" is Microsoftspeak for "Cannot debug because Just My Code is enabled"

When your ETL goes bonkers, you can right button on the process in Task Manager and choose Create Dump File. This will dump the state of your process to your %appdata% temp folder. You can open your project in Visual Studio, then open the DMP file and it will magically take you to the point where the process was. Well, unless you get the "Application is in break mode" message whereby you can do nothing. To fix this, in Visual Studio, go to Debug->Options->General and uncheck "Enable Just My Code"

Remote Desktop

Who else is logged on?

C:\> query use