I was wondering if anyone else has seen this issue.

Last week, we've upgraded our file/print servers from NW65SP7 to NW65SP8 along with all the available public patches. (ie., iprntnw65sp8a)

Since the server update, I've noticed that if click on any of the following tabs from a Windows client, printer properties, the workstation will hang.

NDPS Printer Settings
NDPS Printer Details
NDPS Job Holds
NDPS Notifications

Once the workstation hangs, you can CTRL+ALT+DEL and end the non- responding "Printers and Faxes" window and the workstation becomes usable.

None of the other tabs, effect the workstation or printing behavior.

This seems to happen on workstations regardless of what client version or SP level the client is. It happens with both 4.91SP4 and 4.91SP5 clients, with or without the latest updates.

All NDPS Printers (iPrint is not being utilized) exhibit this behavior. All network printers are HP printers and every family model exhibit this behavior. (HP 4000, 4100, 4200, 4500, 4600, etc....)

The Printer Agents are configured with the default NDPS settings. (ie., NDPSGW PORT=LPR HOSTADDRESS=x.x.x.x PRINTERNAME=PASSTHROUGH)

The Dr. Watson log reports a fault from NDPSPROP.DLL from an Explorer.exe process.

Application exception occurred:
App: C:\WINDOWS\Explorer.EXE (pid=3972)
When: 8/24/2009 @ 12:10:14.078
Exception number: c0000005 (access violation)


eax=00000000 ebx=00000000 ecx=02cfda00 edx=02cfcdc0 esi=58506185 edi=02f8f1e4
eip=58509f7f esp=02f8e8d8 ebp=02f8e9d8 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\ndpsprop.dll -
function: ndpsprop
58509f56 ffff ???
58509f58 ff8b82db0200 dec dword ptr [ebx+0x2db82]
58509f5e 008981270300 add [ecx+0x32781],cl
58509f64 00e9 add cl,ch
58509f66 650200 add al,gs:[eax]
58509f69 008b8d30ffff add [ebx-0xcf73],cl
58509f6f ff8b91a70200 dec dword ptr [ebx+0x2a791]
58509f75 008b42088b8d add [ebx+0x8d8b0842],cl
58509f7b 30ff xor bh,bh
58509f7d ffff ???
FAULT ->58509f7f 8b5018 mov edx,[eax+0x18] ds:0023:00000018=????????
58509f82 8991bb020000 mov [ecx+0x2bb],edx
58509f88 8b8530ffffff mov eax,[ebp-0xd0]
58509f8e 8b88a7020000 mov ecx,[eax+0x2a7]
58509f94 8b5108 mov edx,[ecx+0x8]
58509f97 8b8530ffffff mov eax,[ebp-0xd0]
58509f9d 8b4a14 mov ecx,[edx+0x14]
58509fa0 8988b7020000 mov [eax+0x2b7],ecx
58509fa6 8b9530ffffff mov edx,[ebp-0xd0]
58509fac 8b82a7020000 mov eax,[edx+0x2a7]
58509fb2 8b4808 mov ecx,[eax+0x8]

*----> Stack Back Trace <----*

The date on NDPSPROP.DLL is 12/12/02 which is the file and system date from the Novell client installation folder.

Workstations exhibiting the problem are Windows XP Professional with SP3. (No SP2 clients available to test a potential Windows service pack related issue).

The only thing I haven't tried at this point is back rev'ing the NDPS modules back to SP7. I hate doing that because I fear of putting the server into an unstable state succeptible to server abends.

Any thoughts or suggestions would greatly be appreciated.