<![CDATA[User experience LH metric]]>Hi all,

ProTop 319 on Windows 10 with OE 11.7.13 64-bit.

ProTop is working fine and I see my dashboards in the portal. It has been uploading user experience data for shared memory connections by default, and I'm trying to get it working for localhost as well. I got some errors when I set it up in the scheduler so I undid that and tried to simplify things by just running zippyng.bat from inside a ProEnv shell in my ProTop folder, like this:

bin\zippyng.bat nick lh 4013

nick is the friendly name for my local database, real name pms. I can connect to it from the same ProEnv without any errors:

prowin pms -H localhost -S 4013 -N tcp

When I run zippyng.bat as shown, it seems to work OK - I get a log\zippyng.nick.lh.log with entries like this:

28/03/2022 17:59:49.149+11:00 270000
28/03/2022 18:00:49.789+11:00 190000
28/03/2022 18:01:50.348+11:00 150000

...and there's nothing nasty in log\dbmonitor.log:

2022/03/28 18:02:58.166+11:00 starting: nick waiting to start yes C:\Garradin\Work\v12.1\app\OE117\db\pms
2022/03/28 18:02:58.174+11:00 startWaiting, launched: _progres -b -p util\pt3agent.p -pf etc\protop.pf -param nick -T C:\Garradin\Application\ProTop\tmp -basekey "INI" -ininame etc\protop.ini C:\Garradin\Work\v12.1\app\OE117\db\pms -errorstack -clientlog C:\Garradin\Application\ProTop\tmp\pt3agent.nick.debug
2022/03/28 18:02:58.817+11:00 lgDate: 70/01/01 skipping ahead to: 22/03/28
2022/03/28 18:02:58.818+11:00 sendAlert( dashboard.protop.com.au, logMessage794, info, "" )

The LH stats are uploading to the Bogomips dashboard correctly, but I get a tmp\zippyng.nick.lh.err containing these entries:

The system cannot find the drive specified.
28/03/2022 17:59:49.087+11:00 Unable to find dbanalys: or pms
28/03/2022 17:59:49.094+11:00 Creating new flag file: C:\Garradin\Application\ProTop\tmp/zippyng.nick.lh.flg 10488

There is an up-to-date dbanalys - I did it from inside Protop RT today. Do I need to worry about the error messages?

TIA
Nick

]]>https://community.wss.com/topic/82/user-experience-lh-metricRSS for NodeTue, 11 Aug 2026 23:03:08 GMTMon, 28 Mar 2022 07:24:14 GMT60<![CDATA[Reply to User experience LH metric on Tue, 29 Mar 2022 00:59:32 GMT]]>@nickw still getting the dbanalys msg too? Or just the "cannot find drive" msg?

Can you email to me log\dbmonitor.log and tmp\dbmonitor.debug and err please?

]]>https://community.wss.com/post/326https://community.wss.com/post/326Tue, 29 Mar 2022 00:59:32 GMT<![CDATA[Reply to User experience LH metric on Tue, 29 Mar 2022 00:55:22 GMT]]>Thanks Paul. I updated to to the latest build this morning and I still see the error, but the stats are uploading just fine so I'll ignore it.

Cheers,
Nick

]]>https://community.wss.com/post/325https://community.wss.com/post/325Tue, 29 Mar 2022 00:55:22 GMT<![CDATA[Reply to User experience LH metric on Mon, 28 Mar 2022 12:45:04 GMT]]>@nickw I have seen this "System cannot find the drive" message before. May be a bug - need to look in our ticketing system.

There is a new protop 319 that was released this week. I suggest you try that first. Simply run %PROTOP%\bin\pt3upd from ProEnv.

The DBAnalysis file has to be in %PROTOP\dbanalys and named nick.dba. But if you did it from ProTop RT then it should be fine. That msg may be from before you run DB Analysis.

The "Creating new flag" is normal. All ProTop processes use a file named %PROTOP%\tmp<something>.flg to signal their existance. The easiest way to stop a ProTop process is to simply remove the associated flg file.

]]>https://community.wss.com/post/324https://community.wss.com/post/324Mon, 28 Mar 2022 12:45:04 GMT<![CDATA[Reply to User experience LH metric on Mon, 28 Mar 2022 07:48:30 GMT]]>Should have mentioned... by adding some debug output to the BAT file, I know the command it is invoking is:

start /b _progres -b -p util/zippyng.p -db pms -S 4013 -H localhost -param nick.lh -basekey "INI" -ininame etc\protop.ini -pf etc\protop.pf -T C:\Garradin\Application\ProTop\tmp

I don't have a nick.lh file anywhere. BTW, I have also added zippyng.bat back into the scheduler, and it behaves the same as it does from the command line - the LH stats upload successfully, and I get the errors in tmp\zippyng.nick.lh.err.

]]>https://community.wss.com/post/323https://community.wss.com/post/323Mon, 28 Mar 2022 07:48:30 GMT