Sage 100

Installing version 2013 Advanced on Windows 2008 64-bit server. Get a bunch of messages referencing failure to register DLLs in this folder. Have tried disabling AV (Sophos) and reinstalling MAS. Have tried manually registering, but get failure with that, too. Any suggestions?

@BarbaraGoldstein were the dll's Crystal related and did you get a ""HRESULT -2147023898"" error at the end of the error message dialog box?

Make sure to be logged in to the server as administrator or equivalent AND right click on the autorun.exe and run As Administrator. I usually disable the AV, too. You have to run 'Autorun.exe' to get the prerequisits installed

@JohnLeonard , YES. @MaryMays - did all that.

What OS? I have this error on Windows 2003 server and Sage basically shrugs their shoulder and says I dunno.

Windows 2008

@JohnLeonard , has it been a problem for the users?

I have had a single workstation testing, and all crystal printing has been working.

In my case I could not run any Crystal reports from the server. Since I was updating from v4.3 and the main purpose was for payroll etc. we decided to go with 4.5 for now and see if we could come up with a resolution later. If you are not having any problems running reports etc, then you may be OK. Sage basically said it was a ""server"" issue.

Details on what dlls failed to register as well as the exact error will be helpful. Many times I write down the errors verbatim so I can research later. Without specifics I'm at a loss to search for much of anything.

Forgot to upload this. There are a bunch of them. All living in the same folder.

I don't have anything specific on that error - found this on a general Google search - seems to lean toward 64-bit issue and maybe the C++ redistributable. Did that get installed as a prerequisite? I know in some cases it must be installed through the server console and will fail to self-install.

Oops - link -> http://social.msdn.microsoft.com/Forums/vstudio/en-US/dcc2ae63-d169-4b3d-a89d-082cafdd32cb/error-during-load-crytal-report?forum=csharpgeneral

In my case I uninstalled and then reinstalled the C++ redistributables and that did not solve the issue. I also tried to manually register the dll file and received some sort of memory error when it failed to register.

Yep- that's what I got. Opened case with Sage. They couldn't resolve.

So, the client IT hacked away at it and at some point got the DLLS to register, but I still couldn't print from the server. He installed Service Pack 2 (which should have been there to begin with - don't ask), and now it's working.

Maybe the IT guy forgot to right click and select ""run as administrator"".....

I just got this same error - this is on a Windows SB Server 2003 R2. Happens at the tail end of install after entering in the password for the Sage Integration Engine.

@BarbaraGoldstein any idea what the IT staff did to resolve this? System shows I'm logged in as administrator so my WAG would be AV interference

AV is Trend Micro in my case (which I've found to be especially problematic with Sage 100)

Removed/Shut off Trend - same error. Attempted Regsvr32 on one of the DLL files. Receive probably the same error as Barbara got originally. Holding out hope the customer IT staff recognize some issue that is stopping the installation.

All AV's have been causing issues with our Sage 2013 installs and Crystal installs - I have been turning them off during the installation phase and then exclude the files recommended by Sage. Didn't have near the install issues with 4.5 - but on some servers DEP (Data Execution Prevention) may prevent installation - Have IT set it to 'only for windows programs' and reboot the server.

@WayneSchulz not sure what it was, but have you tried installing the 2005 and 2010 re-distributable packages? Turn off UAC?

In my case the server was a 2003 server. I turned off all AV, made sure all MS patches were up to date turned of DEP and still no luck. I also uninstalled and reinstalled the MS C++ redistributables. The only thing I did not try was to uninstall and reinstall .net4.

I did not try any of the re-distributable reinstalls. @JohnLeonard were you able to get it going and if so do you remember how? If not what did you do?

@WayneSchulz I never was able to get it to work. We ended up upgrading to 4.5 as they were on 4.3 and needed to get something going for payroll. Hopefully they will get a new server before we need to upgrade again or Sage will give us some direction on this (not holding my breath on that one though).

@WayneSchulz - Did the install prompt for any of the 4 pre-requisite programs required for Sage 2013? Here are some steps Sage gave me in June 2013 - I only do the UFAR if I have trouble with the migration and have to redo. This is the process I use when I do my upgrades to 2013. Especially if they are NON SPS Credit Card users. So far these steps have not failed me. 1.Rebuild Keys Files all modules for all companies that will be migrated 2.Rebuild Sort Files all modules for all companies that will be migrated 3.UFAR SY0CTL.SOA file in the Source Installation 4.To UFAR the file do the following: 1.Browse to the ..\..\MAS90\SOA directory of the source installation 2.Make a copy of the SY0CTL.SOA 3.Browse to the ..\..\MAS90\HOME directory of the source installation 4.Double click on Pvxwin32.exe 5.Click OK to message 6.At the prompt type in the following command >Run ""*UFAR"" and hit Enter 7.For Name of KEYED/DIRECT/EFF file: type in SY0CTL.SOA and hit Enter then Enter again 8.Active_Index will be selected by default. Hit Enter ( If not use arrows to move back and forth to select it) 9.""Is this correct for ALL records in this file? Use arrows to select D-Wrong and hit Enter 10.""Is this correct for ALL records in this file? Use arrows to select E-Wrong and hit Enter 11.The Recovered Records count will show. 12.""Clear and reload original file? Yes will be selected by default. Hit Enter 13.File ""Sy0ctl.soa"" repaired successfully. ""Erase temporary file 'Sy0ctl.B01'? 14.Yes will be highlighted by default. Hit Enter 15.Type Bye to exit UFAR 5.From the 2013 Autorun click on Install Sage ERP Standard 6.Click on Productivity Tools in the bottom of the list 7.Install Module SDK 8.Reboot Server 9.Browse to the 2013 installation folders 10.Open BARSETUP directory 11.Double click on SageExchange.Application.msi to install Sage Exchange 12.Install New Instance of 2013 from autorun 13.Install Update 4 (or current update) 14.Install any hotfixes or IRDs 15.Zip up the new 2013 MAS90 directory and all of its contents before starting any migrations. Want to have a backup just in case. 16.Proceed with Pre-Migration 17.Proceed with Parallel Migration 18.Convert as Usual

Thanks - I did get the prompt to install and register the prerequisites. The system appears to have done that - prompting for a reboot of the server. It's possible that one of the prerequisites did not install or did not install completely. At this point looks like I'm going to pull a Sage case and let them struggle.

Not able to resolve - opening support case with Sage.

An oldie but a goodie - not sure if this will be of any help http://infosource.sagesoftwareonline.com/infasp/kdb.asp?isresolutionconceptid=403942

Loading this did NOT help. There are probably 15 different ""it could be this or that"" related to this issue that you can find in a Google search.

I really like the last option - reinstall the operating system :)

On occasion I have seen where the C++ redistributables seemed like they installed from the download location but they really didn't. Had to get them from Microsoft and run them. You may have already tried that but I don't see it in the notes above.

When I look on the server I can see around 20 - 30 copies of MSVCR80.DLL -- or whatever the C++ DLL is (at least that's what I think it is). At this point I can neither complete the Sage 100 install or a full install of Crystal. The full Crystal will install but won't run. I presume there's some type of DLL conflict. I pulled a case with Sage and per my agreement with customers that's where my responsibility ends unless they want an expensive add-on project to ""Try this and try that"". For 2014 I'm going to stop-loss these types of catastrophes quite fast. Give it and hour then pull the Sage case. Especially if it's an issue other 90 Minders have run into.

Update: No luck whatsoever on this. Sage has recommended variations of trying to manually install the pre-requisites to the system. None of that worked. Still have the 1904 error. Also I am able to install the full Crystal Reports but it will NOT start up no matter how many times I click the Crystal icon. It just sits and does nothing. I would strongly recommend anyone encountering this to immediately pull a case with Sage and then discuss with the customer how they'd want to proceed. I have now written into my upgrade quotes that one of the things we presume is that the Autorun from Sage will run without error. If it does not then we propose a change request. Also this was a Windows 2003 server SB -- and there were a lot of duplicate DLL files (as noted previously) which were way beyond my ability to clean up on the server. I suspect this problem is related to duplicate/wrong version .NET or C++ system level DLL files.

@WayneSchulz - you might want to add to your list of adders one for Small Business Server - it breaks M$ own best practices and is more likely to have these kinds of conflicts.

Thanks Phil that's a good idea. I'm going to be much more diligent in the future. If the Autorun won't run and there's no 90 Minds discussion on a quick fix I'll open a case with Sage immediately. It takes way too long to go through 5 or 6 rounds of ""trying"" to install only to get the same results.

Sage suggested running this .NET fix utility and send the link below. http://www.microsoft.com/en-us/download/details.aspx?id=30135 Have not tried yet - if it works I will followup

Notes on what the tool does: http://support.microsoft.com/kb/2698555

I just spoke with support again on this and they also suggested renaming the SAP Business Object folder before trying to reinstall.

i had to do what @JohnLeonard did as well

Running the suggested .NET repair did NOT resolve this particular issue. Exact same error. I'm beginning to believe this could be an endless game of ""try this"" and ""try that"" culminating in ""oh I guess the customer has to wipe their server and reinstall the OS"" ....

And each exploration of ""maybe this maybe that"" is a 20 to 30 minute chunk of time that you'll never get back...

With the amount of time I put in on this problem I am quite certain I could have hand coded an all new Sage 100 2015, upgraded the remaining non-framework modules to framework , upgraded the customer and completely trained them ...

I tried to rename the SAP Business Objects Folder and also tried the dotnetfix utility and neither of them worked.

Wayne have you tried choosing Ignore to see if it will go around it?

Yes I've done ignore. It does complete and based on other feedback I believe the primary issue would be that you cannot print from the server. I might be able to setup workstations and have those workstations operate normally. However I'm not terribly comfortable with that since I'm unsure whether some other issue could crop up that is related.

Yes - I would also be worried about something not working later on down the road. I have had more trouble installing Sage 2013 on 2003 server and XP workstations than on Server 2008 or Server 2012. I have had TERRIBLE issues with .net on server 2003 related to programs other than Sage and have had to create cases with Microsoft to fix. It relates to some certificates being expired and Microsoft technician had to do a command line install of .net - took couple of hours. Microsoft was supposed to fix the issue with the certificates so MS Updates .net install would update. Is there any hope your client would consider a server upgrade?

@WayneSchulz - I felt the same way as you. I could print from a workstation, but not from the server. I was uncomfortable going live without resolving the issue because of unknown issues that could make themselves known (and I needed to sleep at night).

@MaryMays I'm not sure if the end user would consider a server upgrade. At this point I had to put in a stop loss because I've already spent more time than I'll be able to collect for an upgrade. If there's no light at the end of the tunnel the customer can either retain me for a separate Sage project to debug Sage's install routine or they can call Sage on the case # and track it themselves.

I don't understand why Sage can't debug the installation and fix it themselves - should not be something that the consultants have to do.

@wayne - This is where I throw up my hands, open a case with Sage and let them deal with it and pray they don't throw their hands up......

I would expect a response similar to: Make sure that you are logged in as an Administrator and not under Admin Group account. Temporarily Disable firewall and AV. Launch the install application under option: Run As Administrator. If installing with PU2 please let me know as there are additional setup steps for this particular update that relates to LM 5004-t hot fix

Got a message from Sage to try this. I'll probably see if it makes a difference but honestly at this point I feel that it's mostly a shot in the dark and I'm unwilling to put in unlimited time to solve an installer problem (whether it's Sage or Crystal). http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333533333334333333393333%7D.do

I tried the fix Wayne posted and it worked!! Yea. Thanks @WayneSchulz for posting.

I guess I'll be trying this as well tonight. I'd been holding off because every ""try this"" takes me 45 minutes to login and get setup. After about the 12th time I've lost a little enthusiasm to be the tester.

I believe this fix does resolve the issue. The link to the relevant KB is as follows (I'll also copy/paste in case the link goes away). http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333533333334333333393333%7D.do Symptom Deploying the Crystal Reports for Visual Studio 2010 runtime, CRRuntime_32bit_13_0.msi. Error 1904. Module C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dtsagent.dll failed to register. HRESULT -1073741819. Contact your support personnel. Other Crystal Reports dll's that may fail to register are: commonobjectmodel.dll ReportPromptEMF.dll ReportSourceBridge.dll error.jpg Environment Visual Studio 2010 Crystal Reports for Visual Studio 2010, RTM Cause An incorrect version of cryptocme2.dll is being picked up by the Crystal Reports installer. A system environment path is pointing to c:\program files\CA\Shared Components\Etpki\lib\cryptocme2.dll Crystal Reports is not able to use this dll. Resolution Search your system for all instances of cryptocme2.dll. Rename cryptocme2.dll files you find to something like *.org Do NOT rename the cryptocme2.dll files you find the in the subdirectories of C:\Program Files (x86)\SAP BusinessObjects Install the Crystal Reports runtime (CRRuntime_32bit_13_0.msi). Rename cryptocme2.org files back to cryptocme2.dll. The issue is resolved in Service Pack 1 for CRVS2010 NOTE - there is one exception; The system environment variable ""R_SHLIB_LD_LIBRARY_PATH"" can not be overwritten and thus steps above must be applied. Keywords Crystal Reports 2010, cr4vs2010, cr4vs, VS .NET2010

This is the Sage person who provided the solution

A follow up to this - I ONLY had to rename the file specifically mentioned in the fix (CA folder). (Whew, because that file was out there a billion times.) Thank you all for blazing the trail before me.