This is most likely down to authentication credentials that
relate to the SQL data accessed by the ODBC data source. These credentials are set
by right clicking on the report and selecting “Set ODBC data source” I would
suggest that you compare those that don’t work against those that do.
You may need to provide more information but this error
relates to the ODBC connection. Was this working before or is reporting new to
this PC? Are there any other crystal reports that run from within GoldMine?
When you create the ODBC data source is the test successful at the end and how
are you authenticating unified login or SQL ? Is your PC 64 or 32 bit? I would start the trouble
shooting by making sure that the ODBC is 32bit - c:\Windows\SysWOW64\odbcad32.exe
also you may want to consider making sure that the SQL user has data reader
and data writer access or use unified login.
Everything was working from GM from two computers... both Win 8. I'm guessing a windows update or something must have broke it.
I've done everything you've mentioned... but I'm not sure where you check for the SQL data reader verses writer OR unified login. Is this in the ODBC connection?
My guess is that someone edited the report and tweaked the stored credentials or updated the connection in some way. I'd resist making changes on the workstations -- since they both simultaneously failed, it's probably not them.
Doug,
THANKS for the reply.
The reports work fine in Crystal so what should I check? Doesn't make sense to me.
Hi Gary
So can you confirm that the report runs fine using Crystal on the PC and fails when running through GoldMine on the same PC? If so have you checked the credentials in GoldMine Right click the report and set odbc data source and credentials.
Yes. That's it exactly and yes I've tried numerous times to "reset" the creds in GM. Doesn't make sense... because it's happening on a Windows 7 machine also.... although this machine does not have Crystal. It only has the runtime.
does the goldmine user you're testing with have crystal settings in their own INI or do you have an override set in the gm.ini for the crystal settings?
When creating the ODBC Data Source, did you create a 32-bit ODBC? If you created a 64-bit ODBC, Crystal Reports will not see this and you will get the IDispatch error.
I used the 32 bit.... the odd thing was that it was all working... then one day it decided to not work any more. The mystery of working with computers... what caused it to stop... may never know. In the meantime I will be installing Crystal full blown version on the other computer so they can run it.
great question. - No settings in the GM.ini file.
Settings in each of the user ini's only.
Should I try wiping out the [Crystals] section in the user.ini file and then have them reenter the credentials???
I prefer to set a gm.ini override if the crystal odbc name and credential is globally established/the same. Easier to manage.
Didn't work.... wiped out the Cyrstals section and reentered... same error.
Doug,
Makes sense.... Do I just put the same settings in the user.ini into the Gm.ini?
Yeah, like this:
[User-Override:Crystals]
DSN0=goldmine
UserID0=gmuser
Password0=^$#*^RITF^%DFI^TDF*^%D*
DSN1=goldmine
UserID1=gmuser
Password1=HO*GO&G(*&Y)*G&*G)
(password hashes changed by smashing the keyboard, your details will, naturally, be different)
