APP Crash - When emailing RM statements

(1) Share

Report

Posted on by Community Member

Has anyone seen this before? Customer is trying to email statements and gets this error. How does GP use the MSVCR90.dll? The user can print the statements to the screen with no error, just emailing seems to be the issue.

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (0)

Bill Campbell 12 on at

Like (0)

Report

Shelly I am sure i have seen this before and it was related to some permission to a temp folder that the system wanted to access. I know this not an answer, but a comment - so be sure to look at the overall permissions on the user - the computer - the share where the Report.dic is located.

Does this happen only on the one workstation? or does it happen where ever the user connects from?

Talk soon.

Was this reply helpful? Yes No
Suggested answer

babubaskaran@outloo... 12 on at

Like (0)

Report

Shelly,

What version of GP. Please check whether you have installed the Microsoft Office web components which might cause this issue.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hey guys! Thanks for your help. I actually opened a case with MS on this one. I gave security to the GP folder and Temp folder. Installed the web components for office. Ran a repair on MS office, rebooted the server. And still same issue. We also tried the following:

1) We eliminated the third party products.

2) We eliminated the Reports.dic file

3) We performed a new code installation. This didn't make any difference.

4) Created a new ODBC Connection

5) Captures a process monitor log file - did not see any access denied's

I will keep you posted!

Was this reply helpful? Yes No
drummerboy_10 on at

Like (0)

Report

I'll be curious to know what the resolution was to this problem since we're using GP2010 and getting ready to talk about emailing RM statements.

Was this reply helpful? Yes No
Suggested answer

babubaskaran@outloo... 12 on at

Like (0)

Report

Hi Shelly,

Have you tried to disable UAC on the server.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

could be the number of statements that are being generated as well. If you do a small subset of say like 10 (just to test); does same error occur? if they are using the word template options for statements there is a limit to number that can be generated at once; this can cause some system failures.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I am having a very similar issue when attempting to do anything related to email (ie: putting in a new email address in the Customer Maintenance window and clicking Save). Everything I do with email caused GP to crash with now error, but the event viewer gives the error related to the MSVCR90.dll.

This is a Windows Server 2012 OS on a Terminal Server with Office 2010 Standard installed and GP2013. There are two custom forms with VBA code installed on GP. I did a full re-install of GP and did not have the issue with it crashing when attempting to email until the VBA code was added back. The VBA code is fine, and works properly on the user's individual workstations. I am certain that it is something with the TS environment and specifically the Windows Updates that were installed earlier this month, when the issue began.

I am curious if anyone has found a resolution for this yet?

Thanks,

Dana

Was this reply helpful? Yes No
Ian McQuade - Arctic 25 on at

Like (0)

Report

Hello All

I have the same issue

Anything I do that involves email spawns this crash and error

Has anyone found resolve?

Cheers

Ian

Was this reply helpful? Yes No
Carl Meadows 315 on at

Like (0)

Report

Apologies for adding to an old call but I have the same problem.

GP crashes with MSVCR90.dll as the fault module name. This happens when you attempt to amend an email address or send an email from GP using templates documents.

Has anyone who posted here found a resolution?

Was this reply helpful? Yes No
Suggested answer

Steve Simon 348 on at

Like (0)

Report

Why don't you use the Regsvr32 command to Un-Register the bad version of MSVCR90.DLL; then Register a prior version. These DLL's are in folders in the Windows\WinSxS directory. Search for MSVCR90.DLL and look at the properties->detail to see if the version number matches the one in the Event Viewer. That is the one to Un-Register. Then find an earlier dated file with same name and Register that.

1. To Un-Register:

2. OPEN COMMAND PROMPT: From START menu select RUN option. ...

3. NAVIGATE TO THE EXACT LOCATION OF DLL: Type “regsvr32 /u filename.dll” where “filename” is the name of the DLL that you are trying to unregister.

4.

To Register

5. OPEN COMMAND PROMPT: From START menu select RUN option. ...

6. NAVIGATE TO THE EXACT LOCATION OF DLL: Type “regsvr32 filename.dll” where “filename” is the name of the DLL that you are trying to register.

If this doesn't fix it, then reverse the procedure and you will be back to where you were.

Steve Simon

PDG Consultants

Was this reply helpful? Yes No