Since NAS (at least the versions I've seen) is a 32-bit application, it "suffers" from being "boxed" in the WOW64-mode in a 64-bit OS (Windows Server 2003 x64, Vista x64 a.s.o)
The following link has Microsoft's view on things:
http://support.microsoft.com/kb/923357 (someone please fix this in a better way [-o< )
But to be brief:
The first 32-bit application that prints anything seems to "lock" any other sessions that wants to print from a 32-bit application.
This WILL occur if you have >1 NAS that runs "Reports" that print (to either virtual or real printer).
Since the NAS-session "never" closes, only reconnects, only the first one will get it's report printed.
Any other NAS will get "Cannot print" in the Event-log (it looks like the error in old version where NAS could not handle extra report-permission to modify "indirect"-tables)
Solution:
Don't run a printing NAS on a 64-bit, use a 32-bit OS instead.
Just a warning to you all, before you consider suicide for not finding this. ](*,)
(it took me >8 hrs #-o using
Sysinterals "Process Monitor" and going thru >100K log-entries)
Comments
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Thanks
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
What is WOW? I must be simple... #-o
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.