Problems with perl and database access since microsoft cerurity patch

[michael]

Hi,
we use a NT Server with IIS 4, rented from an provider.
On this we use a sybase sql anywhere 5.5.04, connected via odbc. The
software is written in perl using WIN32.
Sine the MS03-26 security update done by the provider we have no more
access to the database.
Starting the databse with dbsrv50.exe the base starts. Connecting with
the scripts from the local CMD works without problems.
But do it from a browser it doesnt work.
In the sql.log the error message says"Microsoft ODBC Driver Manager,
The server appears to be not available.
In the perl error logs the error message says: can't call method "SQL"
on an undefined value....
In the page http://www.roth.net/perl/odbc/faq/ we found the tip to
check the system DSN, there is everything fine.

The application is very needfull, so pleas help.
Thanks to you all
Michael (Wuppertal, Germany)

 

[James Willmore]

we use a NT Server with IIS 4, rented from an provider.

On this we use a sybase sql anywhere 5.5.04, connected via odbc. The
software is written in perl using WIN32.

OT: Have you checked the Sybase SQL Anywhere site?

Sine the MS03-26 security update done by the provider we have no
more access to the database.

OT: Did you read the README (or similar) file that came with the
patch? Check the Microsoft site?

In the perl error logs the error message says: can't call method
"SQL" on an undefined value....
In the page http://www.roth.net/perl/odbc/faq/ we found the tip to
check the system DSN, there is everything fine.

Perl Related --
I take it you are talking about the DBI trace file that you set up in
the script when you say "perl error logs"? If you are using the DBI
module, you can use the trace method to create a trace file. This
file is useful in finding out what's going on with the script as it
relates to the various DBI methods.

You may want to write a simple script to just connect to the DSN,
making sure you set up a very verbose trace file, to see what's going
on. Simple if you're using the DBI module - consult the user
documentation if you are not. You could also see if you can connect
with another application. If you can, then the way the script is
connecting may not be correct. If you can't, see the above comments
pertaining the the Sybase and Microsoft sites.
-- Perl Related

HTH

Jim