Database Search
TechHome
 |
- !!NEWSFLASH!!
- 1437 or 3437 Extender Load Error
- 3132 error when using DAO
- 521 Attribute string too long
- Access SQL Update
- An SQL Tutorial
- Automated ODBC Data Source creation
- Calling a MS SQL Server 2000 Stored Procedure
- Change database then Update then count rows
- Compact an Access Database
- COMPACT_DB and Password MDB Files
- Continue a SQL Query after a Warning Message from Driver
- Create a System DSN for a TXT File Problem
- Create an SQL DSN with User name and Password
- DSN Connection Strings
- Execute an Oracle stored procedure
- Explanation of ODBC Usage
- Get Installed Driver Information
- Get Parameters from a Stored Procedure
- How Does qBindCol Work
- How to Do a Simple Sql Query
- Invalid Cursor State Error
- MDAC Invalid Object
- Microsoft SQL Server ODBC driver Info
- More on How ODBC Works
- ODBC and Services
- ODBC and SQL
- ODBC DSN Maker
- ODBC DSN Port Configuration
- ODBC Extender with WebBatch problems
- ODBC on 64 bit System
- ODBC SQLDescribeCol Example
- ODBC WHERE Syntax Blank Data
- Pervasive SQL Syntax Error
- Problem Adding System DSN for SQL Server
- Problem Using qConfigData with the Oracle ODBC Driver
- qConnect Crashes with Exit Code -1073741571
- qExecDirect and SQL Questions
- QExecDirect Second handle issue with SQL Server Drivers
- qFetch with Empty Cell
- qFetch with qBindCol and qGetData
- qGetData 50 columns limit
- qLastCode to Check these SQL Return Codes
- Read Information from Lotus Notes
- Retrieving data after a SQL JOIN
- Return Codes in ODBC Extender
- s0022 error from SQL Server Driver
- Specify SQL Server Password in qConfigData
- SQL Server SELECT SUM Statement
- SQL SUCCESS WITH INFO
- Syntax for Insert Into Access
- Updating ODBC.INI File over the Network
- Using WildCards in an ODBC SQL Statement
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
ODBC Extender with WebBatch problems
Keywords: qConnect error ODBC
Question:
I have been trying to use the ODBC Extender with WebBatch 98D and MS Peer Web Services. When I issue the qConnect function from within my WebBatch script the function fails. If I extract all of the WinBatch from this script and execute this outside of the browser environment (i.e. just WinBatch) I get a successful connection. I have checked items such as the DSN and the ODBC dlls are available for the IUSR_machinename account that the PWS WWW service uses but still have had no success.The qConnect function fails with a return error of -1 (SQL_ERROR).
I have run out of ideas now, can anybody help?
Answer:
One option is to try to capture the error. For example:
ErrorMode(@OFF)
retcode = qConnect(hdbc, Datasource, "", "")
ErrorMode(@CANCEL)
err=qerror(hdbc,1)
webout(err,1)
If (retcode != @qSuccess) && (retcode != @qSuccessInfo)
Message("qConnect failed", retcode)
Exit
Endif
The error message returned from the driver, should clear things up.
Reply to Answer:
I have spotted the problem now. The qError function finally helped me track this down.
As part of the profile for the IUSR_machinename account I was including a folder in the PATH environment containing the DLLs required for the DB connection. It seems that the profile definitions are not used when the account is only providing the 'service logon' requirement. I even tried including this folder in the machine PATH environment, which still made no difference. As soon as I put the DLLs in the system32 folder all was well.
Article ID: W12540
Filename: ODBC Extender with WebBatch problems.txt
File Created: 2001:01:09:15:56:46
Last Updated: 2001:01:09:15:56:46