Sage 100

I have an unsupported user running 4.20 that is used to just lookup old data. It is running on an old server as 4.20 MAS200. I copied to old workstation since we want to get rid of the old server. The workstation is running XP. I ran workstation setup to just get the DLLs into the windows subdirectory and then setup a MAS90 shortcut so it runs as a thick client. Everything works except when we try to print a report we get a 3.71 company, user and password prompt. I have checked the 3 pvx files in the windows\system32 and they match those on the server. Any thoughts on what needs to be replaced or adjusted to get printing to work?

Have you looked at the odbc driver? If you are running mas90 mode you probably need a valid path to the mas90 folder.

path all looks good there. When I test the ODBC driver I get the same legacy company, user and password. I think I have a file missing or outdated somewhere in the operating system.

Maybe one of the dlls didn't get registered. Maybe try and re-register them.

Is Excel on the workstation? If so, launch a query. If this works, you can rule out the ODBC connection. Does the report work if you add the prompted information.

Just those three or is there a registration utility like there was for FRx some time back.

Excel is also pulling up the old prompt for user and password.

I vaguely remember an issue with early version of 4.x where crystal reports would pull up a security screen and that screen is the old version.

The query should prompt you. Question is, does the query work after prompting.

I setup a new user. The new user shows up in the 3.71 style dropdown. When I put in a valid user and password, it comes back failed. It is acting like the driver is not valid.

Maybe you can install v4.2 Standard GL and LM only on the workstation. That would re-install the odbc dlls. Then modify the path of the odbc driver to point to the Advanced folder.

Last time I had this happen (v 5.3) It's was user permissions. Also, did I follow that you copied MAS 200 to an XP workstation? I don't think you can run the Client Server (MAS200) version on a workstation operating system.

I made sure to repopulate permissions and made it everyone full control to eliminate security. Keep in mind the security challenge is the ODBC challenge for 3.71 and this is 4.2. I checked the dll in DSN management to ensure it matches what is working on the old server today.

Have you seen this, not exactly the same level? You'll need to log into the Sage KB to access this link https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=57706&sliceId=1&cmd=displayKC&dialogID=105102&docType=kc&isLoadPublishedVer=&stateId=105104&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

I did see that one. I have checked there are no selections or settings that turn on the C/S ODBC. I also checked to make sure the file copied to the workstation where I am attempting to set this up.

I moved the 3 PVX... files from the windows\system32 directory dated 2006 and decided to risk temporarily copying ones from my 2015 version dated 2014. I no longer get the credential prompt and my reports preview.

Yea!