Community Feedback

[spauley]

We have an error that pops up intermittently on our MAS server. 

The problem details, are as follows:

Problem signature:

  Problem Event Name:                        APPCRASH

  Application Name:                             pvxwin32.exe

  Application Version:                           8.10.0.0

  Application Timestamp:                     47b36116

  Fault Module Name:                          PVXIO.DLL

  Fault Module Version:                        4.21.1000.0

  Fault Module Timestamp:                  4725d862

  Exception Code:                                  c0000005

  Exception Offset:                                0001080b

  OS Version:                                          6.1.7600.2.0.0.274.10

  Locale ID:                                             1033

  Additional Information 1:                  8db3

  Additional Information 2:                  8db313e53ef84cb9b1ad25d565e750c9

  Additional Information 3:                  ec9a

  Additional Information 4:                  ec9a69979ccfbc62a208b882df9ce1ec

Read our privacy statement online:

  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

  C:\Windows\system32\en-US\erofflps.txt

After this error pops up on the server, when some end users attempt to launch the MAS client on their PC, they get a white box  that hangs on the clients screen, until an administrator closes the error on the MAS server console. Once the error is closed on the server, the client can successfully launch MAS.

This error on the server intermittently occurs. Some days, it won’t happen at all, while other days, it happens several times.

Anyone else have this problem? Were you able to resolve it? Any Help or feedback would be appreciated. 

[ASI]

Are you running MAS 200?  Do you have a lot of users?  Are you running the host as a service?  If you answered yes to all of these questions, you should try running the host as an application instead of as a service.  We had a client with something very similar to what you described and the issue was caused by running the host as a service.

[kanes]

What kind of server are you running?

[jorgem]

Im having the same problem did you resolve this?

[jorgem]

I was able to resolve this problem

In my case it was a combination of some workstations not having .Net 3.5 installed and the Ternimal Server not liking the print drivers for our networked HP printers.

I Installed the drivers locally on the client workstations and made sure they had .Net 3.5 installed. TS 2008 needs .Net installed on the client workstation in order to properly redirect printing to the client.

Hope this helps someone else having this similar issue

[TheOtherGuy]

This a fairly common issue with redirected printers.  Redirected meaning: A printer that locally connected to a computer but  is being printed to from a program run through a terminal server / Citrix connection.

The terminal server and the workstation have to have the same drivers.  If they become out of sync you can see a variety of different issues in our program and other programs as well. 

Simple text printing will often be ok. This will lead some users to believe it is a MAS 90 or 200 issue.

If you are unfamiliar with TS or Citrix and you don't know how to sync the drivers you can always add the local printer to the Terminal Server computer as a network printer then print to it from there instead of using redirection. 

HP printers are notorious for this type of issue.  Presumably because HP printers often have several different drivers for each printer and they update them all the time.

Remember the driver on the workstation has to be same as the driver on the Terminal server.  Yes, even the version can make a difference.