PWB and PAMS

For general issues related to PWB v2.

Moderators: Tyler, Scott, PWB v2 Moderator

Post Reply
vsedys

PWB and PAMS

Post by vsedys »

We are using 3M PAMS (used to be Library Guardian) filtering system at our library. The system is setup to load on Windows login, once a user is authenticated with a smart card, access to desktop is allowed. On the desktop we have shortcuts to Office apps and PWB.
On occasion, PWB crashes when a user is viewing a page. Windows Event Log shows:
---
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 1/20/2005
Time: 16:01:15
User: N/A
Computer: PUBLIC7
Description:
Faulting application pwb.exe, version 2.0.4.2, faulting module deny.dll, version 4.2.0.0, fault address 0x00005e48.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 70 77 62 ure pwb
0018: 2e 65 78 65 20 32 2e 30 .exe 2.0
0020: 2e 34 2e 32 20 69 6e 20 .4.2 in
0028: 64 65 6e 79 2e 64 6c 6c deny.dll
0030: 20 34 2e 32 2e 30 2e 30 4.2.0.0
0038: 20 61 74 20 6f 66 66 73 at offs
0040: 65 74 20 30 30 30 30 35 et 00005
0048: 65 34 38 0d 0a e48..
---

Deny.dll is one of the files used by PAMS. Suspecting, that there is some kind of conflict between the filtering system and PWB, I forwarded this information, together with PAMS logs, to 3M. After investigating the problem, this was their response:

---
We found the problem. PWB.exe is creating problems while we are trying to load up our config when Windows loads. Not sure what PWB is doing at that point, but it is definitely creating a problem when we are trying to load the LSP.


We can fix that by creating an exception for PWB in the LSP config. We
already do this for a number of apps like Norton AV, etc. I will let you
know when we have something.
---

My question is - what is PWB trying to do on startup? (During Windows logon, when PAMS is loading.) The browser isn't being launched until the user is fully authenticated and double-clicks on the desktop shortcut for PWB. AutoRestart is not being used on those machines.

Thank you,
Vaidas Sedys
Howell Carnegie District Library

Scott
Site Admin
Site Admin
Posts: 2539
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

By default PWB does not load at startup. The only way PWB will load at startup is if you are using PWB as the Windows Shell, have PWB in the Startup folder, or have PWB loading in the Run key in the registry.

Perhaps they meant when PWB loads, not when Windows loads.

Aer you using ManageIE? This will load when Windows loads because Internet Explorer is part of the Windows GUI.

--Scott

vsedys

Post by vsedys »

Yes, we are using ManageIE on those stations. Would ManageIE have any references to PWB anywhere?

Vaidas Sedys
Howell Carnegie District Library

Scott
Site Admin
Site Admin
Posts: 2539
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

ManageIE does not reference PWB in anyway and does not need PWB to run.

At what point in time does the error indicated happen, When Windows is loading, or when PWB is clicked on?

Does the error occur if the user double clicks the shortcut immediately after Windows loads?

--Scott

vsedys

Post by vsedys »

The error occurs randomly, when a user is browsing the web. It can happen anytime during their session, after they have already looked at a number of sites. It doesn't happen frequently, I'd say couple times a week on some computers, probably even less on others. When the error does occur, the browser crashes and the user has to start over. I have not been able to attribute a specific web site or user action to this event - it appears to be simply random.

Vaidas Sedys
Howell Carnegie District Library

Scott
Site Admin
Site Admin
Posts: 2539
Joined: Mon Dec 16, 2002 12:31 pm
Location: Rochester, MN
Contact:

Post by Scott »

Since the error is happening while PWB is running, it may be an error in PWB. The current version of PWB is 2.0.6.2. You seem to be using an older version according to the error log, 2.0.4.2. Try upgrading to the newer version since there were quite a few bug fixes between the versions.

--Scott

Post Reply