Mas90 Crystal Reports

Hi guys I have a client with an old MAS90 server and I set up a new workstation and just directed the icon to the server and it worked but it didn’t install crystal reports. I realized there is a workstation install but it’s asking to put the path to the server and I just want to make sure if I install it on the workstation it’s not going to mess up the server if I direct it to the server, as they have no backup or anything and can’t mess up the server. Any help would be appreciated!

  • 0

    Thanks guys the version is: 

    SSSystem Setup

    4.05

    11/12/2004

    i don’t think there are left over versions it’s a fresh copy of windows 10, I was able to copy mas90 from the server to the root of workstation to get the workstation setup to complete, but now I went from the first error to the second error when trying to do the customized reports.

  • 0 in reply to Christopher May

    Oh my, not a type-o correct? :) Unsure of the version of Crystal that came with 4.05. Bound to be some compatibility hindrances. Cullen's feedback is most helpful IMHO, I too was trying to find that article as well as I know it was a high profile and used KB which should be able to be found.  His details direct you where to go and check as long as there are not compatibility limitations.  

  • 0 in reply to Jeff Konstanzer

    4.05 was probably using CR 8.5. That KB is probably in the download center as a "version of Crystal" document. Yup, there it is, with a new KB# and everything: Solution ID:  224924150050666.

  • 0

    Hey guys is there anyone who knows how to work on this old version that we would be able to pay to remote in and fix this issue?

    Thanks!

  • 0 in reply to Christopher May

    I would think a Windows 10 operating system with an old v4.05 version of Sage 100 and Crystal 8.5, is not going to be compatible. I mean, that version of Sage 100 was released in November 2004; it is almost 20 years old. 

  • 0

    No we’ve had it work without this error before just fine so it can be done 

  • 0 in reply to Christopher May

    To answer your previous question, yes - there are lots of people who can work on this old version. Many of us have been working with MAS 90 for many years, and in fact still keep a library of old manuals, knowledgebase articles, program patches, etc.

    I want to point out, however, that you are playing with fire and/or putting a band-aid on a sucking chest wound by not upgrading this version 4.05 data to an updated program that is designed to work on modern plattforms. So IMHO, your first order of business should not be trying to get this old system working on Windows 10, but it should be upgrading MAS 90 4.05 to Sage 100 2023. And yes, there are plenty of us who can help you with that, as well.

    FWIW, here is an old archived copy of MAS 90 v4.05 I have installed on an old Win 7 VM. This is running in Hyper-V, and as you can see it allows me to access and input data, print and preview reports, etc.

    So here is one potential solution to your current problem. Copy these files over to a Win 7 VM and use it to access data and run reports while you install the newer version on a new server and prepare to upgrade.

    If your current VAR/Reseller/Sage Partner is not comfortable with this old version, they can reach out to either Sage or to another reseller for assistance to work on a contract basis (at least I think that's possible - I'm just a technician, myself). Sage Support will not exactly assist with this, but they should be able to point you to a reseller who will.

  • 0 in reply to Christopher May

    Windows updates frequently break things that used to work.  On modern versions, Sage will work to fix things broken by 3rd parties, but just because an older version used to run, does not mean it can again, on a newer operating system.

  • 0

    Thank you, but my customer has told me they used to spend thousands a year for this software and support and now it’s gotten so expensive they are looking at something like 15 grand to upgrade because of how much it costs… the software works fine on the win 10 server it’s installed on so I know this can be done on windows 10. I also have an exact clone of the server and we back it up weekly so if something does break I can get back to a working level. My issue is just getting this error done and working, it worked before on win 10 on the workstations and still works today on the win 10 server… if someone here would be willing to remote in please let me know so we can talk about hiring you. Thanks!

  • 0 in reply to Christopher May

    Based on your comments "and just directed the icon to the server and it worked" and the error message "A DLL is either corrupt, not been properly registered, or incorrect version."  I am guessing you did not run work station setup which installs the Crystal run time engine and the DLLs.