BizTalk, PAL, Performance

PAL not working with restricted account

Just thought I’d post this since I couldn’t find a concise hit myself when searching for it. I’m using the PAL (Performance Analysis of Logs) tool in a restricted environment where my default user isn’t an administrator. In certain scenarios this will cause PAL to fail. The definition of certain in my case is when the LogParser CSVInMaxRowSize registry key is too low, causing PAL to want to write a new value, on line 173: WshShell.RegWrite “HKLMSOFTWAREMicrosoftLog ParserCSVInMaxRowSize”, iRowSize, “REG_DWORD”. The error message that PAL will display in its Command window is: C:Program FilesPALPAL v1.3.3PAL.vbs(173, 9) WshShell.RegWrite: Invalid root in registry key “HKLMSOFTWAREMicrosoftLog ParserCSVInMaxRowSize”.


I “solved” this by running PAL (the call to CScript that is) as an administrative user, since I had that option. I guess smaller (less counters collected) logfiles than mine would not get this error, as would situations where the LogParser maximum row size is already set to a large enough value.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s