Sage 100

Trying to do a Verify Database on a canned crystal register (Receipt of Goods Invoice Work). Crystal 2011/MAS 5.00.5. I get the attached screen, and can't get past it. I tried launching CR and logging into server, then opening the report which sometimes works. But today, I can't get there from here. What is the magic to getting past this?

I found a Sage KB article on this dating back to version 4.4, but that's not my problem. Also, there's a post on Sage City that's related, but I don't know how to post a link to it here. The title is ""database login failed to open connection

I don't think this is it but worth a peek - https://90minds-com.socialcast.com/messages/17291104?ref=stream

This isn't a situation where they're using CS ODBC and the service stopped? Don't think it's this error but I've had that occur and think it produced something similar

No, this is an install on my local machine. I don't run WKSETUP on my local. Now, I do have 4 versions of MAS and 3 versions of Crystal on here, but I made sure I logged into the right MAS first, then launched Crystal. I run into this on client installs more than occasionally, and it irritates the heck out of me.

Try this - it's worked for me a couple of times. At the point where you are at, click on the Back button. Then you should see the SOTAMAS90 and it will let you login like normal.

You can also try 'Set Datasource Location' and make sure it's pointing to SOTAMAS90.

I think this is a bigger issue than people realize. I am starting to see this more and more. V2013 Std. See attached. The first one is multiple connections is from a client install. The second is a report that was part of the PU5 install. The path indicated is a Sage path, not one from my server. This is NOT isolated. I have even received a report from another reseller that has their login information. Take a look at your v2013 installs. You will see it throughout.

Yes I just saw this on a 4.4 to 2013 upgrade. Still can't get a working ODBC connection from within Sage 100 on their server (get the standard ODBC login prompt like Barbara). Sage support thinks those ""driver ="" connection settings are normal.

Barbara, I'm curious if you have linked in any other tables to that report? I have run into this error - vendor code 143 at one of my clients and we spent hours and hours (with and without Sage) trying to track it down with no success. The client where I ran into this is on Sage 100 Advanced All users log in through 2 different terminal servers. we tried with Client Server ODBC turned off and turned on with the same results. Here are some things we found: we only run into it when we have a custom report or have modified one of Sage's standard reports. It only seems to happen when we link in another table. If the report takes a long time to process, then the error happens almost every time. For whatever reason it always happened if we try to link the GL_Account table (that table is large for this client but not enormous) When we link in tables using the SOTAMAS90 ODBC driver we can't see the indexes (the little colored triangles). We see them when we first start the report but after I refresh it once they seem to disappear. (I don't know if this is in any way related to the issue or not, but we noted it). We found a workaround and that was to create our own ODBC driver with a silent connection and use that for custom reports that we added to the menu when we do that, the report runs fine every time. It is important to note that since the silent connection has the company code in it, then the report can only be run for one company if users switch companies the report still runs from the company in the silent connection string. This is OK for my client as they only have one live company. Also important to note this silent drive cannot be used on Forms or any report that uses a worktable. for those reports our answer was to add UDF'S to the worktable that are data sourced from the other tables instead of trying to link in other tables. Hopefully this information will help someone else! Sage could not resolve this and we have been getting by with our workaround for several months now but the underlying issue is still there, we just have to remember to use that driver if we add a custom report to the menu.

@BethBowers - that worked! At least this time . . . :-) Thank You! @DavidOverholt - I have no other linked tables, but I added a UDF to the worktable. Great suggestions, all.

Wonder if @AlnoorCassim has any insight to the real issue.

Just ran into this today with an upgrade to 2013. The back function works to reset the path it has saved, as per @JeffSchwenk 's post. You have to select the ""Select Data Source"" option and then choose SOTAMAS90. Why is it saving those paths???

See this Sage City post. Snipped from it attached. Don't know if that answers the question, though . . .http://sagecity.na.sage.com/support_communities/sage100_erp/f/98/t/74613.aspx

Interesting. Thanks @BarbaraGoldstein . Doesn't explain why they are using a connection string however.