v3 to v4.1 PU3 Upgrade - Invoice printing - method of object call failed (2 replies)
I have a number of clients who use iman to print documents like orders/invoices from Sage 300. In these situations we get one of two errors: Method of Object call failed, or something that indicates the Sage300printspooler has blown up midway through running the job. One of my clients did some digging and has resolved the issue (i.e. her job was blowing up daily and it's now been 2 weeks without error). She did 3 things on the iman virtual: 1)Turned of DEP for the Sage 300 print spooler 2) Ran System File Checker from a DOS command to fix any registry corruption issues 3)Ran DISM from a DOS command to fix any windows update issues. Please see the attached Word Doc for details on this procedure. I don't know that this will fix it for sure for all of my client's, but I'm certainly going to try it...
Sorry - see attached zip file that includes word doc...
I upgraded a client's iman server from v3 to v4.1 w PU3 today. I have two jobs that print invoices to pdf and then email the invoices out. When I run the job or step through the job, the method of object call failed occurs when I try to print the sage 300 invoices. The client is currently using Sage 300 2014 PU5. I can login to sage 300 on the iman server and print the invoices, using the same crystal report the Iman job calls. I've verified the a4wcrinterop.dll was already under the c:\inetpub\wwwroot\iman\bin folder and registered it - just in case. Refreshed services and apps. Got the same message in the Sage 300 step of the job.
I've attached a zip file that includes: a screenshot of the error inside iman, the errors.txt file, and a customaddinloadlog file that had the same date/time stamp as the errors.txt - just in case...