Page 1 of 2 1 2 >
Topic Options
Rate This Topic
#133398 - 03/14/06 05:06 AM AR System ODBC Driver and SCRIBE
flirble Offline
journeyman

Registered: 03/09/05
Posts: 82
**
Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen
20060125This posting was submitted with HTML in it

Top
#133399 - 03/14/06 05:10 AM Re: AR System ODBC Driver and SCRIBE [Re: tlockwood]
joe_remedy107 Offline
old hand

Registered: 06/28/04
Posts: 736
**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**
Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen



Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it

Top
#133400 - 03/14/06 05:25 AM Re: AR System ODBC Driver and SCRIBE [Re: tlockwood]
flirble Offline
journeyman

Registered: 03/09/05
Posts: 82
**
Joe,

Yes when we were testing we tried a restricted user, and also used my login which is administrator, thus should have access to all forms/tables needed.

Stephen


On 14/03/06, Joe DeSouza wrote:

**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**

Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen




Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it




20060125This posting was submitted with HTML in it

Top
#133401 - 03/14/06 05:39 AM Re: AR System ODBC Driver and SCRIBE [Re: tlockwood]
joe_remedy107 Offline
old hand

Registered: 06/28/04
Posts: 736
**
Any errors when you try to log on to the AR Server using the AR ODBC driver?

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**
Joe,

Yes when we were testing we tried a restricted user, and also used my login which is administrator, thus should have access to all forms/tables needed.

Stephen


On 14/03/06, Joe DeSouza wrote:

**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**

Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen




Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it

20060125This posting was submitted with HTML in it





Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it


Top
#133402 - 03/13/06 10:11 PM Re: AR System ODBC Driver and SCRIBE [Re: tlockwood]
beanta Offline
enthusiast

Registered: 09/15/04
Posts: 313
**
Stephen,
Is the SCRIBE application connecting via a custom-defined 'System DSN' that uses the AR System ODBC driver (recommended), or is it attempting a connection via the default 'User DSN' entry for the driver?

--Thomas


----- Original Message -----
From: Stephen Earl
Newsgroups: gmane.comp.crm.arsystem.general
Sent: Tuesday, March 14, 2006 11:25
Subject: Re: AR System ODBC Driver and SCRIBE

**
Joe,

Yes when we were testing we tried a restricted user, and also used my login which is administrator, thus should have access to all forms/tables needed.

Stephen


On 14/03/06, Joe DeSouza wrote:

**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**

Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen




Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it






20060125This posting was submitted with HTML in it

20060125This posting was submitted with HTML in it

Top
#133403 - 03/15/06 02:04 AM Re: AR System ODBC Driver and SCRIBE [Re: tlockwood]
joe_remedy107 Offline
old hand

Registered: 06/28/04
Posts: 736
**
I do not think its flaky too, you might need to do certain things that may not be very clearly documented to get it to work, but once you get it to work it is pretty consistent.

The problem with SCRIBE seems to be more of how SCRIBE is handling the driver.. They could try running a network snoop to see if SCRIBE is sending any packets at all forward to the server while attempting to log on to the Remedy server via the ODBC, and if not it would mean there is something wrong with SCRIBE itself... not the ODBC driver as he says it works well with other apps...

Joe

Carey Matthew Black wrote:

Axton,

Flaky? Really? You have had problems with it working, not working,
and working again for some unknown reason?

Limited...yes.. by Remedy design. (AKA: Working as designed) However,
I have not had problems with it being "Flaky".

--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.



On 3/15/06, Axton wrote:
> Do keep in mind that Remedy's ARODBC driver is flaky at best.
> Supported ODBC call types are extremely limited.
>
> Axton Grams



Relax. Yahoo! Mail virus scanning helps detect nasty viruses! 20060125This posting was submitted with HTML in it

Top
#133404 - 03/14/06 07:06 PM Re: AR System ODBC Driver and SCRIBE [Re: tlockwood]
flirble Offline
journeyman

Registered: 03/09/05
Posts: 82
**
Thomas,

I've tried both, system and user with the same results, after discussions with Joe I'm pretty convinced it's a SCRIBE problem as we now have got as far as an error from scribe of:

Data source label SOURCE not found

I'm going to see if it even tries to connect or if it's an internal error...




On 14/03/06, Thomas Bean wrote:

**
Stephen,
Is the SCRIBE application connecting via a custom-defined 'System DSN' that uses the AR System ODBC driver (recommended), or is it attempting a connection via the default 'User DSN' entry for the driver?


--Thomas



----- Original Message -----
From: Stephen Earl
Newsgroups: gmane.comp.crm.arsystem.general
Sent: Tuesday, March 14, 2006 11:25
Subject: Re: AR System ODBC Driver and SCRIBE


**
Joe,

Yes when we were testing we tried a restricted user, and also used my login which is administrator, thus should have access to all forms/tables needed.

Stephen


On 14/03/06, Joe DeSouza wrote:

**

Stephen,

While configuring the ODBC driver did they specify a Remedy user that has the rights to see all the tables you need to see.. Bear in mind that the Remedy ODBC driver respects the permission set you have defined in Remedy on the forms...

Joe D'Souza
Remedy Developer / Consultant,
Shyle Networks,
New Jersey.

Stephen Earl wrote:

**

Hi,

We have a 3rd party trying to integrate to our AR System platform and ideally we'd like them to 'read' via the AR System ODBC driver then they can make use of the date translation abilities etc...

However when they connect using an application called SCRIBE and select the AR System ODBC datasource as an ODBC data source it fails to return any forms or rows, if they use the raw Oracle ODBC connector they can see the raw tables etc... quite happily... are the known limitations using the ODBC connector with certain apps?

Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?

Config info:

AR System 6.0.3 patch 11
App Server: Solaris
DB Server: Oracle 9.2.0 patch 4
DB Platform: Solaris
Application: SCRIBE
SCRIBE Server: Windows Server 2003

Crystal runs fine on the same server using AR System ODBC as does our Crystal Reports Distribution program, we've used Excel successfully on said server, but SCRIBE just fails to be able to use the ODBC connection...

All constructive suggestions appreciated.

Stephen




Yahoo! Mail
Use Photomail to share photos without annoying attachments. 20060125This posting was submitted with HTML in it








20060125This posting was submitted with HTML in it

20060125This posting was submitted with HTML in it


20060125This posting was submitted with HTML in it

Top
#133405 - 03/15/06 01:25 AM Re: AR System ODBC Driver and SCRIBE [Re: tlockwood]
axton_grams Offline
old hand

Registered: 03/22/05
Posts: 738
Do keep in mind that Remedy's ARODBC driver is flaky at best.
Supported ODBC call types are extremely limited.

Axton Grams

On 3/15/06, Stephen Earl wrote:
> **
> Thomas,
>
> I've tried both, system and user with the same results, after discussions
> with Joe I'm pretty convinced it's a SCRIBE problem as we now have got as
> far as an error from scribe of:
>
> Data source label SOURCE not found
>
> I'm going to see if it even tries to connect or if it's an internal error...
>
>
>
>
> On 14/03/06, Thomas Bean wrote:
> > **
> > Stephen,
> > Is the SCRIBE application connecting via a custom-defined 'System DSN'
> that uses the AR System ODBC driver (recommended), or is it attempting a
> connection via the default 'User DSN' entry for the driver?
> >
> > --Thomas
> >
> >
> > ----- Original Message -----
> > From: Stephen Earl
> > Newsgroups: gmane.comp.crm.arsystem.general
> > Sent: Tuesday, March 14, 2006 11:25
> > Subject: Re: AR System ODBC Driver and SCRIBE
> >
> >
> > **
> > Joe,
> >
> > Yes when we were testing we tried a restricted user, and also used my
> login which is administrator, thus should have access to all forms/tables
> needed.
> >
> > Stephen
> >
> >
> > On 14/03/06, Joe DeSouza wrote:
> > > **
> > >
> > > Stephen,
> > >
> > > While configuring the ODBC driver did they specify a Remedy user that
> has the rights to see all the tables you need to see.. Bear in mind that the
> Remedy ODBC driver respects the permission set you have defined in Remedy on
> the forms...
> > >
> > > Joe D'Souza
> > > Remedy Developer / Consultant,
> > > Shyle Networks,
> > > New Jersey.
> > >
> > > Stephen Earl wrote:
> > > **
> > >
> > > Hi,
> > >
> > > We have a 3rd party trying to integrate to our AR System platform and
> ideally we'd like them to 'read' via the AR System ODBC driver then they can
> make use of the date translation abilities etc...
> > >
> > > However when they connect using an application called SCRIBE and select
> the AR System ODBC datasource as an ODBC data source it fails to return any
> forms or rows, if they use the raw Oracle ODBC connector they can see the
> raw tables etc... quite happily... are the known limitations using the ODBC
> connector with certain apps?
> > >
> > > Has anyone successfully used SCRIBE and the ARSystem ODBC datasource?
> > >
> > > Config info:
> > >
> > > AR System 6.0.3 patch 11
> > > App Server: Solaris
> > > DB Server: Oracle 9.2.0 patch 4
> > > DB Platform: Solaris
> > > Application: SCRIBE
> > > SCRIBE Server: Windows Server 2003
> > >
> > > Crystal runs fine on the same server using AR System ODBC as does our
> Crystal Reports Distribution program, we've used Excel successfully on said
> server, but SCRIBE just fails to be able to use the ODBC connection...
> > >
> > > All constructive suggestions appreciated.
> > >
> > > Stephen
> > >
> > >
> Yahoo! Mail
> > > Use Photomail to share photos without annoying attachments.
> 20060125This posting was submitted
> with HTML in it
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> > 20060125This posting was
> submitted with HTML in it
> > 20060125This posting was
> submitted with HTML in it
>
> 20060125This posting was submitted
> with HTML in it


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org

Top
#133406 - 03/15/06 01:31 AM Re: AR System ODBC Driver and SCRIBE [Re: tlockwood]
black_123 Offline
old hand

Registered: 07/10/04
Posts: 851
Axton,

Flaky? Really? You have had problems with it working, not working,
and working again for some unknown reason?

Limited...yes.. by Remedy design. (AKA: Working as designed) However,
I have not had problems with it being "Flaky".

--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.



On 3/15/06, Axton wrote:
> Do keep in mind that Remedy's ARODBC driver is flaky at best.
> Supported ODBC call types are extremely limited.
>
> Axton Grams


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org

Top
#133407 - 03/15/06 02:58 AM Re: AR System ODBC Driver and SCRIBE [Re: tlockwood]
michiel_beijen663 Offline
journeyman

Registered: 03/09/05
Posts: 147
** If you want to see if the SCRIBE system is logging in to the server you can also turn on the user logs on the AR server and look if there are any entries in there.
If someone connects through the ODBC driver you'd have to see an entry in the user.log

Regards,
Michiel


On 3/15/06, Joe DeSouza wrote:

**
I do not think its flaky too, you might need to do certain things that may not be very clearly documented to get it to work, but once you get it to work it is pretty consistent.

The problem with SCRIBE seems to be more of how SCRIBE is handling the driver.. They could try running a network snoop to see if SCRIBE is sending any packets at all forward to the server while attempting to log on to the Remedy server via the ODBC, and if not it would mean there is something wrong with SCRIBE itself... not the ODBC driver as he says it works well with other apps...

Joe


Carey Matthew Black < black.123@GMAIL.COM > wrote:

Axton,

Flaky? Really? You have had problems with it working, not working,
and working again for some unknown reason?

Limited...yes.. by Remedy design. (AKA: Working as designed) However,
I have not had problems with it being "Flaky".

--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.




On 3/15/06, Axton wrote:
> Do keep in mind that Remedy's ARODBC driver is flaky at best.
> Supported ODBC call types are extremely limited.
>
> Axton Grams




Relax. Yahoo! Mail virus scanning helps detect nasty viruses! 20060125This posting was submitted with HTML in it




20060125This posting was submitted with HTML in it

Top
Page 1 of 2 1 2 >