Re: Remedy ODBC Drivers and 7.1

2009-02-25 Thread Grooms, Frederick W
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:arsl...@arslist.org] On Behalf Of ccrashh
Sent: Wednesday, February 25, 2009 7:26 AM
To: arslist@ARSLIST.ORG
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 thorin.ma...@we-energies.com
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:ccra...@gmail.com]
 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


Re: Remedy ODBC Drivers and 7.1

2009-02-25 Thread Marty.Thorin
 
Dear ???
Attached is the ODBC of my install document for the 7.01.00 Patch 5 user 
tool.  I have had your error.  I resolved it by fixing the ODBC setup.

List:
Do we have a place to put documents?  This is a 261KB word document.  
(Almost all of it is screen shots.)  I am not very good at uploading / 
downloading / etc.

Thorin

-Original Message-
From: ccrashh [mailto:ccra...@gmail.com]
Sent: Wednesday, February 25, 2009 7:26 AM
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 thorin.ma...@we-energies.com
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:ccra...@gmail.com]
 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 atwww.arslist.orgPlatinum
 Sponsor: RMI Solutions ARSlist: Where the Answers Are

 __
 _ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org 
 Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI 
Solutions ARSlist: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are


Re: Remedy ODBC Drivers and 7.1

2009-02-25 Thread Danny Kellett
You could just use one of the many free ones available online

http://www.megaupload.com/
rapidshare.com


-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Marty.Thorin
Sent: 25 February 2009 21:37
To: arslist@ARSLIST.ORG
Subject: Re: Remedy ODBC Drivers and 7.1

 
Dear ???
Attached is the ODBC of my install document for the 7.01.00 Patch 5 user
tool.  I have had your error.  I resolved it by fixing the ODBC setup.

List:
Do we have a place to put documents?  This is a 261KB word document.
(Almost all of it is screen shots.)  I am not very good at uploading /
downloading / etc.

Thorin

-Original Message-
From: ccrashh [mailto:ccra...@gmail.com]
Sent: Wednesday, February 25, 2009 7:26 AM
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 thorin.ma...@we-energies.com
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:ccra...@gmail.com]
 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 atwww.arslist.orgPlatinum
 Sponsor: RMI Solutions ARSlist: Where the Answers Are

 __
 _ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org 
 Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:
RMI Solutions ARSlist: Where the Answers Are


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are
 

__ Information from ESET NOD32 Antivirus, version of virus signature
database 3889 (20090225) __

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are


Re: Remedy ODBC Drivers and 7.1

2009-02-25 Thread Easter, David
You could post the document on the BMC Developer Network.  That'd be a very 
appropriate place to share a document of benefit to the broader community.

http://developer.bmc.com/

 
-David J. Easter
Sr. Product Manager, Solution Strategy and Development
BMC Software, Inc.
 
The opinions, statements, and/or suggested courses of action expressed in this 
E-mail do not necessarily reflect those of BMC Software, Inc.  My voluntary 
participation in this forum is not intended to convey a role as a spokesperson, 
liaison or public relations representative for BMC Software, Inc.

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Marty.Thorin
Sent: Wednesday, February 25, 2009 1:37 PM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy ODBC Drivers and 7.1

 
Dear ???
Attached is the ODBC of my install document for the 7.01.00 Patch 5 user 
tool.  I have had your error.  I resolved it by fixing the ODBC setup.

List:
Do we have a place to put documents?  This is a 261KB word document.  
(Almost all of it is screen shots.)  I am not very good at uploading / 
downloading / etc.

Thorin

-Original Message-
From: ccrashh [mailto:ccra...@gmail.com]
Sent: Wednesday, February 25, 2009 7:26 AM
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 thorin.ma...@we-energies.com
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:ccra...@gmail.com]
 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 atwww.arslist.orgPlatinum
 Sponsor: RMI Solutions ARSlist: Where the Answers Are

 __
 _ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org 
 Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI 
Solutions ARSlist: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI 
Solutions ARSlist: Where the Answers Are

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are


Remedy ODBC Drivers and 7.1

2009-02-24 Thread ccrashh
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


Re: Remedy ODBC Drivers and 7.1

2009-02-24 Thread Marty.Thorin
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:ccra...@gmail.com] 
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

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: Where the Answers Are