I am having a problem getting all the perl modules and database stuff
installed correctly on my Red Hat 8.0 server. I was wondering if anyone
might be able to help.
I have installed all the MD4, MD5, LDAP, DBI modules without any problems.
I am now working on getting the FreeTDS and DBD-Sybase
Title: RE: (RADIATOR) FreeTDS DBD-Sybase Install
I've never managed to get DBD::Sybase to pass all of its tests, but the install has then worked fine.
Instead of using the standard tests, might I suggest you roll your own - a swift perl script that tests a representative sample of the sort
RE: (RADIATOR) FreeTDS DBD-Sybase InstallI found this information on the
internet.
There is an open source project - FreeTDS, http://www.freetds.org/ - to
create an interface to TDS-compliant database servers such as Sybase and,
MS SQL. MS SQL 7.0 speaks TDS version 7.0, but will also speak TDS
I found this out from the author of the DBD::Sybase module. He posted this
to the FreeTDS mailing list back in October 2002. He is specifically
talking about the errors that are generated when you run the 'make test'
option on the DBD::Sybase module using FreeTDS.
No. I haven't followed things
Tim Jung wrote:
I found this out from the author of the DBD::Sybase module. He posted this
to the FreeTDS mailing list back in October 2002. He is specifically
talking about the errors that are generated when you run the 'make test'
option on the DBD::Sybase module using FreeTDS.
So it
Is there any way to have the Radiator evaluate multiple rows and select the
one that matches from the result of an AuthSelect in an AuthBySQL clause?
I want to be able to have multiple different services for the same username
and it would be VERY nice if Radiator could select the row with the
Ok I have all the DBD Sybase SQL stuff and FreeTDS installed now. It
appears that it connects to my database server but it never replies back to
any of the requests. Below are the debug sessions of what I am seeing.
Anyone have any ideas as to what the problem might be?
Tim Jung
System Admin
Hello Tim -
Thanks for sending the debug output.
As far as I can see, Radiator is calling the database but never getting
a response.
I would check the MS-SQL logs to see what is happening on that side.
You might also want to turn on debugging in the DBD and FreeTDS modules.
BTW - another
Tim,
What does your config look like? Also, what does your freetds.conf look
like?
David Birkbeck
Network Engineer
IKANO Communications
mailto:[EMAIL PROTECTED]
(801)415-8022 Phone FAX
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On
Behalf Of Tim Jung
Sent:
Ok I went and looked at the configurations you mention and made a few
changes. One of them was to try and use domain login rather than server
login. It should not have made a difference, since there is both a rodopi
NT account and SQL account, but all of a sudden I get a lot more
information from
I just went and looked in the MS-SQL and in the Rodopi AbacBill database
there is a stored procedure called Interface_VircomDetails and another
called Interface_VircomUsers. I now have no idea why it says it couldn't
find these stored procedures. Is there somewhere I was suppose to tell it
what
Hello Rickard -
The standard AuthBy SQL clause will only process the first row returned
by the query, so in your case I would run a query that included a
reference for the service required. You could chain together two AuthBy
SQL clauses to first find the service description and then the
Hello Tim -
In what you show below, there is no DBSource, DBUsername or DBAuth
(they are commented out).
These *must* be set to enable access to your database (the values must
match what has been configured in your database).
regards
Hugh
On Thursday, Feb 6, 2003, at 12:11
If you look you will see this:
# Heres how you might connect to the Rodopi MS-SQL
# database from Unix using DBD-Sybase
DBSourcedbi:Sybase:Rodopi
DBUsername rodopi
DBAuth secret
These are
Hi Tim -
Quite right - my apologies (been looking at too many configuration
files :-/).
I have copied this mail to Mike for further comments.
Mike - could you take a look at the trace 4 debug below?
regards
Hugh
On Thursday, Feb 6, 2003, at 16:32 Australia/Melbourne, Tim Jung wrote:
If
Hello Tim,
Hmmm, it appears that the Interface_VircomUsers stored procedure is not
present in your database (or perhaps you dont have permission to run it).
Can you confiirm whether or not such a stored procedure exists in your
dbi:Sybase:Rodopi database (it should have been installed by the
I can confirm that all the supposedly missing or not found stored
procedures are in fact in the AbacBill database. The rodopi user in
MS-SQL is the owner of those databases. When I tried to login only via
server login it appeared to lockup and stop responding. If I logged in via
domain login to
If I try and login as the sa or turn off/disable the NT rodopi account
and still tell it to do a domain login, so it is forced to use the SQL
rodopi account right? I get this error message:
DBI connect('Rodopi','rodopi',...) failed: Server message number=18452
severity=14 state=1 line=0
Hello Tim,
this is looking increasingly like a MS-SQL permissions issue. I am noty very
expert in all the ways you can authenticate access to MS-SQL, but I do know
that named pipes work differently to TCP-IP (which is what the connection
across the network will use).
You might like to run the
Hello Tim,
On Thu, 6 Feb 2003 05:59 pm, Tim Jung wrote:
If I try and login as the sa or turn off/disable the NT rodopi account
and still tell it to do a domain login, so it is forced to use the SQL
rodopi account right? I get this error message:
Im not sure.
Perhaps you should use a password
Ok I setup a whole new user just in SQL and made it also the owner of the 2
Rodopi databases. I can connect with the new account linux and
authenticate, but I still get all the can't find stored procedure errors. I
even double checked to see what permissions the sa account had on those 2
Rodopi
21 matches
Mail list logo
