Double check your ODBC data sources... We had a problem where there was a System, User, and File ODBC all with the same name. Try the following:
Remove all AR System ODBC data sources (System, User, and File ones) Uninstall the user tool (If they have old versions remove them as well) Re-install the User Tool (Make sure you do this as a user with FULL admin rights) We have never had to put a server name, user, or password in the ODBC data source Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of ccrashh Sent: Wednesday, February 25, 2009 7:26 AM To: [email protected] Subject: Re: Remedy ODBC Drivers and 7.1 No, it isn't a password issue. It's definitely a problem with the way 7.1 creates the User Datasource. They even have a "bug" filed for it - but are also calling it "as designed". Bizzare... On Feb 24, 2:02 pm, "Marty.Thorin" <[email protected]> wrote: > The first question to ask is "What is in your password?" I do not care > about A through Z, nor 1 through 9: the other characters. Remedy is not > picky but Crystal tries to parse passwords. > > Thorin > > -----Original Message----- > From: ccrashh [mailto:[email protected]] > Sent: Tuesday, February 24, 2009 10:37 AM > Subject: Remedy ODBC Drivers and 7.1 > > Has anyone else seen this issue? When trying to run an embedded Crystal > Report, we got the error: > > "An error occurred while generating the Crystal Report: 0x80047e48 - > Logon Failed (ARERR 1904)" > > What we discovered is that the AR System ODBC driver existed as a Data > Source but did not have a server name (that is, if you go to Windows > Start/Administrative Tools/Data Sources (ODBC), there should be a line > for the AR System ODBC driver...if not, you can add it). Now, if there > is no AR System ODBC driver listed as a User Data Source, you can still > run the report via a 6.3 User Tool. The User Data Source is created and > set properly (i.e. with a server name). However, if you run the report > from a 7.1 User tool, it does NOT create the data source. > > As well, on SOME machines, even if the data source is there but there is > no Server Name, you get the error above - on other machines, as long as > the Data Source exists, the report runs even if there is no Server Name. > We can't figure out why, and what is happening. > > BMC says that this is "as designed" - that is, each Client Workstation > has to manually set the AR System ODBC driver. Sigh. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
