REGASM a4wcrinterop.dll

Registered successfully but still getting same error.

Close Sage 300. Export the registry branch (as a backup, just in case):

Computer\HKEY_CURRENT_USER\Software\ACCPAC INTERNATIONAL, INC. 

...then delete it. Try again.

Deleted and still getting same error.

Also getting this with class not registered when printing. 

Did you manage to resolve?

If the other suggestions don't work, check the Visual Studio C++ redistributables are installed correctly.  The biggest problem is when you have duplicate versions of the same C++ redistributable installed but different revisions.  If these prerequisites are not installed correctly they can cause this error.  To quickest way to check/fix this is to uninstall Workstation Setup off the machine, uninstall all presently installed C++ redistributables then re-install Workstation Setup which will install the correct ones.  On a clean 2023 PU3 server working perfectly, here are the presently installed C++ redistributables:

Good luck!

No, still working with Sage support.

Thankyou so much - it worked

Unfortunately did not work.

What environment is the workstation on where the error is occurring?  Does the Crystal error occur on the server itself, as well as the workstation - on both or only one?  Is the workstation an RDS server or a stand-alone workstation?  It would be unusual for this error to occur on server itself, but please let us know.

I am having a problem on server running Windows Server  2019 and we are using RDS affecting all users. 

If you have this error on server you have a bad luck. After a month long work with Sage support only solution is to reinstall Windows.

Hi

sage 2023. Upgraded to new server in dec clients did testing all ok 

reloaded data last night converted. Did not touch programs only data. 

Now when printing even standard layout get  -2147467259 method of object failed. Any suggestions please. This is on server. 

on RDS it says cannot open file. 

Rerun workstation setup to reinstall Crystal libraries

Hi

should I run wstation set up on server or tserver. I did on tserver and it still says it can not connect to the DLL. That is the oe 

Run workstation setup everywhere.

Ok that altered the error no longer the method of object failed

Now the same as tS is "Failed to open connection 2BZA(form name) 

That's a customized OE invoice.  Make sure the DATAPIPE lines in OERPT.INI are correct.  Look at OERPT.INI in the previous version around the OEINV01 and OEINV02 sections.  If it is a datapipe report, then you need to copy the newest version of the DLL to the OE custom folder just above ENG.

If I open the report in crystal it wont let me alter pathing to dll

This is the error

That's right, you can't do that.  Put that DLL in the ..\Custom\OE70A folder, just above the ENG folder where that RPT file is.

Hi all sorted

Only issue I am having is it request the sa user and password before printing

Thankyou for your assistance

Contact the person who wrote that report, they did something non-standard.

me :) I think its in sql remeber now on old server - admin group with all accpac users mapped database to that assigned server roles

Add CSCOM to the report as a table.  You don't need to add any fields.  Don't link CSCOM to the DLL even when it warns you about multiple starting points.  

I know I've said this before but this is the best tip ever.  Before I learned this from Jay, I had to add everyone to a AD group, add that group into SQL as a security login, and grant database permissions to the group.  Such a pain!