none
APPCRASH returns RRS feed

  • Question

  •  

    Ok here is my deal.  I have a client running a brand new out of the box HP 8300F system bought from wal-mart or somewhere who knows.  Point is there is NOTHING installed on it except what came preloaded from the factory.  We like our agents to use Nuance's PaperPort to scan and ftp documents to us.  The Machine is a Vista Home Premium setup 2.4ghs, 3gigs of ram 260+gigs of drive space.  The scanner she is using is a Dell 1600n MFP.  I have installed the vista drivers for the MFP freshly downloaded from Dell, installed printer works beautiful.  The agent went out and bought box copy of PaperPort 11 standard,  11 is Vista compatible (per Nuance).  I install the program everything works great except when I go to scan a document in, I run into issues.  The document scans fine when you select the Done button in PaperPort signaling you have no more to scan in, I get the following error window:

    _______________________________________________

    "PaperPort has stopped Working and needs to close"

    Problem signature:

    Problem Event Name: APPCRASH

    Application Name: PaprPort.exe

    Application Version: 11.0.6255.1

    Application Timestamp: 44685aa6

    Fault Module Name: PSMAXAPI.DLL

    Fault Module Version: 2.0.6.0

    Fault Module Timestamp: 442d2baa

    Exception Code: 80000003

    Exception Offset: 000134f9

    OS Version: 6.0.6000.2.0.0.768.3

    Locale ID: 1033

    Additional Information 1: 8cda

    Additional Information 2: 3db089bfebd928f405f218c353f5b53c

    Additional Information 3: 267f

    Additional Information 4: be5f4b06a61610f30854834fd9d83700

    Read our privacy statement:

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

    _______________________________________________________

     

    If I click on close it goes into a never ending cycle of the error popping up as soon as paper port reloads.  Nuance wants 19.95 to even submit my question with no garuntee of fixing and they want 9.95 to e-mail it in to them...

     

    Please somebody out here has got to have a solution.

     

    Wednesday, February 20, 2008 4:33 PM

Answers

  • The fault aka crash is occuring inside the psmaxapi.dll.  If the crash occurs in a Microsoft function, a lot of times I can at least explain how the function call was called incorrectly.   If you  Right Click on the problem and click "Check for Solution", the report will be sent and the statistics on this particular crash can rise.  The vendor can sign up to investigate their crashes that are occuring on the following web site https://winqual.microsoft.com/default.aspx. It appears that you can file a bug here http://www.nuance.com/help/contact/bug/ but that's not going to get you someone to consult on an immediate solution.

     

     John

     

    I work at Microsoft. These are my opinions and not my employers.

    This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, February 22, 2008 10:41 AM

All replies

  • The fault aka crash is occuring inside the psmaxapi.dll.  If the crash occurs in a Microsoft function, a lot of times I can at least explain how the function call was called incorrectly.   If you  Right Click on the problem and click "Check for Solution", the report will be sent and the statistics on this particular crash can rise.  The vendor can sign up to investigate their crashes that are occuring on the following web site https://winqual.microsoft.com/default.aspx. It appears that you can file a bug here http://www.nuance.com/help/contact/bug/ but that's not going to get you someone to consult on an immediate solution.

     

     John

     

    I work at Microsoft. These are my opinions and not my employers.

    This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, February 22, 2008 10:41 AM
  • I have (had) exactly the same problem and the SOLUTION was that the folders, into which the files were being saved, had the wrong permissions. At least wrong from the software's standpoint. I changed the permissions on every folder in the My Paperport Documents folder and the problem was solved. In the security tab of the folder's properties, I simply opened the permissions to FULL for everybody and every account.
    Sunday, August 2, 2009 6:56 PM