Microsoft OLE DB Provider for ODBC Drivers error 8007000e

Microsoft OLE DB Provider for ODBC Drivers error '8007000e'
[Microsoft][ODBC Microsoft Access Driver] System resource exceeded

I recieve this error every time I execute SQL statement form ASP page on an Access database.
Could any one help me diagnosing this problem and how to avoid seeing such error messages.

ThanksI FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p|||Originally posted by Khalid
I FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p

I have this problem (about access database sending "Resources Exceeded Error") my largest table has 350,000+ Registers. Might this be causing the problem? I tried deleteing 10,000 registers aout of the table but it didn't work.

It just happened after more than 1 year of mu application running perfectly fine.

You can see the error in: http://www.citaris.com/checarplayer.jhtml

Please let me know if you need any other information.

Best regards and thank you very much,.

Alexis.
acastanares@.yahoo.com|||Originally posted by Khalid
I FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p Khalid, can you help me out? I've been getting this error for a few weeks now. Thanks|||Khalid,
It would be most helpful if you'd post the solution here, rather than make everyone who has this problem email you for it.

VRWL :rolleyes:

Originally posted by Khalid
I FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p|||I received lately a lot of emails asking about this famous error problem.
this is my solution I have discovered:

ASP is full of bugs, as I discovered lately, but these bugs can be solved by writing code.

My problem was due to Database connections, it seem to me I was doing the perfect thing, opening connections, recordsets, executing queries and finally I destroy every object I create.

THE PROBLEM
===========
If you open only one connection (as I used to do), and run more than one query or recordsets at the same time, what is happening? ASP does not allow you to run more than one query through the same connection at the same time, (though it seems that it is working) so how come? Since ASP does not allow that, it creates its own connections to run the further queries you are executing, and after you are done with them, ASP is not destroying the connections it creates. If you are not destroying your connection objects as well, so you are helping the problem to come up.

WHAT IS HAPPENING
==================
unclosed objects will create a resource leak in memory, and as the times goes, more objects are not closed, and more memory resources are consumed until it reaches to the maximum. And guess what, the famous message will show up! :rolleyes:

SOLUTION
=========
-Define a connection for every query by its own.
-Create you connection object and destroy them your self, don't let ASP do any thing by its self. :D

Hope this information be helpful for every body.

Cheers

;)|||Yes but... Why if i have two servers, one with a single PIII 500 Mhz and 256 Mb Ram and other with Dual PIII 1 ghz an 1 Gb Ram... with the same web page and with the same Operatin System, I got the problem in the Dual PIII and not in the oldest server?|||Hi,
after reading an article, I am using a jdbc:odbc bridge with an excel file setup as a user dsn. This is to import and export from our java applciation and jdbc database to excel. On XP and 2003 server machines, there is no problem. However, on 2000 server machines, they all get 'system resources exceeded' message and fail to do anything.

Can anyone help with identifying the underlying problem and recommend a solution ? Is there a a buggy MS component or something that needs updating? HELP!!!

thanks in advance,
Neil|||iamneil
As I have described previously, you are getting this message because your application is causing memory leak. This happens due to many causes, I have discovered that in my ASP application, IIS is opening more connections when I try to run more than SQL statement at the same time on one connections, so IIS is creating its own connections and it is not closing those connections when done with them.
If the application is working on heavy traffic those unclosed connections will be consuming the resource of the system untill it reaches the maxium.

So try to find out where is your bug that causes a memory leak.

Check out your application and tell me more about it.

Good luck|||Need Help with this issue.

Pretty Sure that the Problem is that there is a Memory Leak within the Page. It randomly just started Popping Up Non-Stop about Temporary Disk Space.

But here's where I need help - I'm a new webmaster at one of AAA Auto Clubs Divisions, and the Previous webmaster loved ASP Scripting. I personally favor PHP, because I have more experience with it.

But The Employees Here need to get this working up and running ASAP -

It's Pretty Obvious that The Script Used is from ASP Calendar -- But I can't just simply Download another Version of ASP Calendar and Overwrite the File because the Files Have Been Modified to Work Better for the Employees Uses.

Here Is the Exact Error Message I Am Receiving

Microsoft OLE DB Provider for ODBC Drivers error '8007000e'
[Microsoft][ODBC Microsoft Access Driver] Not enough space on temporary disk.
/Calendar/calendar.asp, line 222

Here is the Coding For calendar.asp



--
6 hours trying to find what this error code was from, how it was happening, and trying to find the resource to fix it was Extremely Frustrating.

So if you can help in anyway, it will be greatly appreciated. Plus if you throw in some Educational snippits (comments in the code) of What this part of the script does and what this part of the script does. It would help tremondously!|||<!-- #include file ="dsn.asp" -->
<!-- #include file="adovbs.inc" -->
<%
' Name: ASP Calendar
' Author: Manohar Kamath
' Version: 1.0
' Copyright Manohar Kamath. Original calendar copyright Wrox Press
%>
<%
' catch department and status name from login page
Dim Dept, intStat, strEvents
Dept=Request("Dept")
intStat=Request("intStat")
strEvents=""
%>
<%
'------------------
' This function finds the last date of the given month
'------------------
Function GetLastDay(intMonthNum, intYearNum)
Dim dNextStart
If CInt(intMonthNum) = 12 Then
dNextStart = CDate( "1/1/" & intYearNum)
Else
dNextStart = CDate(intMonthNum + 1 & "/1/" & intYearNum)
End If
GetLastDay = Day(dNextStart - 1)
End Function

'----------------------
' This routine prints the individual table divisions for days of the month
'----------------------
Sub Write_TD(sValue, sClass)
Response.Write " <TD ALIGN='RIGHT' WIDTH=14% HEIGHT=80 VALIGN='top' CLASS='" & sClass & "'> " & sValue & "</TD>" & vbCrLf
End Sub

' Constants for the days of the week
Const cSUN = 1, cMON = 2, cTUE = 3, cWED = 4, cTHU = 5, cFRI = 6, cSAT = 7

' Get the name of this file
sScript = Request.ServerVariables("SCRIPT_NAME")

' Check for valid month input
If IsEmpty(Request("MONTH")) OR NOT IsNumeric(Request("MONTH")) Then
datToday = Date()
intThisMonth = Month(datToday)
ElseIf CInt(Request("MONTH")) < 1 OR CInt(Request("MONTH")) > 12 Then
datToday = Date()
intThisMonth = Month(datToday)
Else
intThisMonth = CInt(Request("MONTH"))
End If

' Check for valid year input
If IsEmpty(Request("YEAR")) OR NOT IsNumeric(Request("YEAR")) Then
datToday = Date()
intThisYear = Year(datToday)
Else
intThisYear = CInt(Request("YEAR"))
End If

strMonthName = MonthName(intThisMonth)
datFirstDay = DateSerial(intThisYear, intThisMonth, 1)
intFirstWeekDay = WeekDay(datFirstDay, vbSunday)
intLastDay = GetLastDay(intThisMonth, intThisYear)

' Get the previous month and year
intPrevMonth = intThisMonth - 1
If intPrevMonth = 0 Then
intPrevMonth = 12
intPrevYear = intThisYear - 1
Else
intPrevYear = intThisYear
End If

' Get the next month and year
intNextMonth = intThisMonth + 1
If intNextMonth > 12 Then
intNextMonth = 1
intNextYear = intThisYear + 1
Else
intNextYear = intThisYear
End If

' Get the last day of previous month. Using this, find the sunday of
' last week of last month
LastMonthDate = GetLastDay(intLastMonth, intPrevYear) - intFirstWeekDay + 2
NextMonthDate = 1

' Initialize the print day to 1
intPrintDay = 1

%>

<html>
<head>
<meta HTTP-EQUIV="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Vacation Schedule</title>
<style TYPE="text/css">
TD.NON {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#C0C0C0; font-weight :normal;}
TD.TOP {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#0000FF; font-weight :bold;}
TD.Some {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :normal;}

A.NOEVENT:Link {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :normal; text-decoration: none;}
A.NOEVENT:Visited {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :normal; text-decoration: none;}

A.EVENT:Link {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :bold; text-decoration: none;}
A.EVENT:Visited {font-family :Tahoma, Verdana, Arial; font-size :12px; color :#000000; font-weight :bold; text-decoration: none;}

A.NORMAL:Link {font-family :Verdana, Arial; font-size :12px; color :#0000FF; font-weight :normal; text-decoration: none;}
A.NORMAL:Visited {font-family :Verdana, Arial; font-size :12px; color :#0000FF; font-weight :normal; text-decoration: none;}
</style>
</head>

<body LEFTMARGIN="3" BGCOLOR="#FFFFFF" TEXT="#000000">
<p> </p>
<h2 align="center">Vacation Schedule Calendar</h2>
<h3 align="center"><%=Dept %></h3>
<p align=center><a href="http://links.10026.com/?link=default.asp">Choose a different department/branch</a></p>
<FORM ACTION="<% =sScript%>?Dept=<% =Dept %>&intStat=<% =intStat %>" METHOD=GET >
<font face="Verdana, Arial" size="2">

<div align="center">Select month and year:
<SELECT NAME=MONTH>
<OPTION VALUE=1 SELECTED>Jan
<OPTION VALUE=2>Feb
<OPTION VALUE=3>Mar
<OPTION VALUE=4>Apr
<OPTION VALUE=5>May
<OPTION VALUE=6>Jun
<OPTION VALUE=7>Jul
<OPTION VALUE=8>Aug
<OPTION VALUE=9>Sep
<OPTION VALUE=10>Oct
<OPTION VALUE=11>Nov
<OPTION VALUE=12>Dec
</SELECT>
<SELECT NAME=YEAR>
<option value="2006" selected>2006</option>
</SELECT>
<input type="hidden" name="Dept" value=<% =Dept %>>
<input type="hidden" name="intStat" value=<% =intStat %>>
<input type="submit" name="Submit" value="Go!">
<! INPUT TYPE="Image" NAME="" src="http://pics.10026.com/?src=images/go.gif" BORDER="0" WIDTH="35" HEIGHT="20">
</div>
</font>
</FORM>
<table ALIGN="CENTER" BORDER="1" CELLSPACING="0" CELLPADDING="2" BGCOLOR="White" BORDERCOLOR="Gray" width="75%">
<tr><td>
<table BORDER="1" CELLPADDING="1" CELLSPACING="0" BGCOLOR="#FFFFFF" width="100%">
<tr HEIGHT="18" BGCOLOR="Silver">
<td WIDTH="14%" HEIGHT="18" ALIGN="LEFT" VALIGN="MIDDLE">
<div align="center"><a href="http://links.10026.com/?link=<% =sScript%>?month=<% =IntPrevMonth %>&year=<% =IntPrevYear %>&Dept=<% =Dept %>&intStat=<% =intStat %>"><img src="http://pics.10026.com/?src=images/prev.gif" WIDTH="14" HEIGHT="14" BORDER="0" ALT="Previous Month"></a></div>
</td>
<td WIDTH="*" COLSPAN="5" ALIGN="CENTER" VALIGN="MIDDLE" CLASS="SOME"><font size=+1><b>
<% = strMonthName & " " & intThisYear %>
</b> </font></td>
<td WIDTH="14%" HEIGHT="18" ALIGN="RIGHT" VALIGN="MIDDLE">
<div align="center"><a href="http://links.10026.com/?link=<% =sScript %>?month=<% =IntNextMonth %>&year=<% =IntNextYear %>&Dept=<% =Dept %>&intStat=<% =intStat %>"><img src="http://pics.10026.com/?src=images/next.gif" WIDTH="14" HEIGHT="14" BORDER="0" ALT="Next Month"></a></div>
</td>
</tr>
<tr>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Sunday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Monday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Tuesday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Wednesday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Thursday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Friday</td>
<td ALIGN="center" CLASS="SOME" WIDTH="14%" HEIGHT="15" VALIGN="BOTTOM">Saturday</td>
</tr>

<%

' Initialize the end of rows flag to false
EndRows = False
Response.Write vbCrLf

' Loop until all the rows are exhausted
Do While EndRows = False

' Start a table row
Response.Write " <TR>" & vbCrLf
' This is the loop for the days in the week
For intLoopDay = cSUN To cSAT
' If the first day is not sunday then print the last days of previous month in grayed font
If intFirstWeekDay > cSUN Then
Write_TD LastMonthDate, "NON"
LastMonthDate = LastMonthDate + 1
intFirstWeekDay = intFirstWeekDay - 1
' The month starts on a sunday
Else
' If the dates for the month are exhausted, start printing next month's dates
' in grayed font
If intPrintDay > intLastDay Then
Write_TD NextMonthDate, "NON"
NextMonthDate = NextMonthDate + 1
EndRows = True
Else
' If last day of the month, flag the end of the row
If intPrintDay = intLastDay Then
EndRows = True
End If

dToday = CDate(intThisMonth & "/" & intPrintDay & "/" & intThisYear)

' Open a record set of schedules
Set Rs = Server.CreateObject("ADODB.RecordSet")

sSQL = "SELECT * FROM tEvents WHERE " & _
"Start_Date =#" & dToday & "# " & _
"AND (Dept='" & Dept & _
"' OR Dept='all')" & _
" ORDER BY Start_Date"

' Open the RecordSet with a static cursor. This cursor provides bi-directional navigation
Rs.Open sSQL, sDSN, adOpenStatic, adLockReadOnly, adCmdText

If NOT Rs.EOF Then

bEvents = True
Do While NOT Rs.EOF

' build list of events for day
'If logged in as manager or during initial entry period, include delete option, else display only names
If intStat = 2 AND Rs("Dept") <> "all" Then
strEvents = strEvents & Rs("Event_Title") & "<a href='delete.asp?Event_ID=" & Rs("Event_ID") & "&Dept=" & Dept & "&intStat=" & intStat & "'><font size=-2 color=red>DEL</font></a><br>"
Else
strEvents = strEvents & Rs("Event_Title") & "<br>"
End If

Rs.MoveNext

Loop

Else

bEvents = False

End If

Rs.Close
Set Rs = Nothing

' If the event flag is not raise for that day, print it in a plain font
If bEvents = False Then
Write_TD intPrintDay, "SOME"
Else
Write_TD intPrintDay & "<br>" & strEvents, "SOME"
strEvents = ""

End If

End If


' Increment the date. Done once in the loop.

intPrintDay = intPrintDay + 1
'clear list of events
strEvents = ""
End If

' Move to the next day in the week

Next
Response.Write " </TR>" & vbCrLf

Loop

%>
</table>
</td></tr>
</table>|||I FOUND IT!
I FOUND THE SOLUTION.

If there is any one interested in this subject or suffering from it, contact me and I will tell him about the million dollar problem solution.

:p

I experiencing the same problem I can not find the solution. Please let me know how to solve

Microsoft OLE DB Provider for ODBC Drivers error 80040e14

Hi guys, it's nice to join the forum. Can someone can help me?

After 2 years of using a program, i suddenly got this error. I tried
re-installing SQL but im still getting the message.

Microsoft OLE DB Provider for ODBC Drivers error '80040e14'

[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL
xplog70.dll, or one of the DLLs it references. Reason: 193(error not
found).Albert (albert@.extremerack.com) writes:
> Hi guys, it's nice to join the forum. Can someone can help me?
> After 2 years of using a program, i suddenly got this error. I tried
> re-installing SQL but im still getting the message.
> Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot load the DLL
> xplog70.dll, or one of the DLLs it references. Reason: 193(error not
> found).

That's an error on the SQL Server side, occurring when calling some
extended stored procedure, which is implmented by the xplog70.dll. I
don't know what exactly is in this DLL, but it appears that xp_logevent
is there.

If there is no requirement for high availability, the easiest may be
to restart SQL Server or even reboot the SQL Server machine to see if that
helps.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Microsoft OLE DB Provider for ODBC Drivers error 80040e07

Microsoft OLE DB Provider for ODBC Drivers error '80040e07'

[Microsoft][ODBC SQL Server Driver][SQL Server]The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.

Our SQL - INSERT INTO tbl_WAAGUsage (logindate,logintime,countryname,subscriberid,ipad dress) VALUES ('2/16/2004','9:50:01 AM','Albania',62,'123456789')

Hi,

I was wondering if somebody could help me... the following error message appears when I run an asp page... I did a google search and nobody appears to have had a solution to the particular problem I have... it's completely baffling but I'm hoping it's a simple setting.

Firstly, I'm sure the coding the correct as the asp page runs on two different servers correctly. I recently got a new server and the script does not appear to work with the Date function in asp on this new server. I outputted the SQL to the browser and then ran it through the Query Analyser(QA) and guess what, it worked! But when I run the asp page the above error crops up... now when I run the SQL through QA and alter the date value in the format 'dd/mm/yyyy' the above error appears in QA.. if I've lost you at this point let me know...

The way ASP passes the Date value to my SQL DB appears to be confused and it's really confusing me as it works perfectly on two servers and not the new one... the new server runs newer versions of O/S and SQL so I'm not sure that is the case... I've changed the date settings on the server so they all three servers match each other... so I have no where else to turn... any help and pointers would be much appreciated!

Regards

Steveuse convert(datetime,variable,formattype) for your variables to first convert them into datetime format and then insert.|||ok... i'll try and see what the results are...

thanks!

Originally posted by Enigma
use convert(datetime,variable,formattype) for your variables to first convert them into datetime format and then insert.|||I don't think there is a Conver() function in VBScript, however there is a FormatDateTime function which I used... didn't produce the results I wanted unfortunately, still comes up with an error... it's the case of the same code producing different results on different servers and my guess is there could be a setting to change on the servers... I'm trying to match up the settings and so far no luck...

could you enlighten me?|||Convert is a function in SQL server , not in VB ... use this function in your insert query.|||Two webservers make this page work, and the third one has problems? Have you checked (or had an admin check) the regional settings on the bad box?|||ah hah...

I'm very enlightened!! Thanks alot for that... solves all my date problems now!!

Cheers

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
Hi all,
I am getting this error while trying to insert a record into the database ta
ble. We are using SQL SERVER 2000/ODBC/ASP combination.
I would really appreciate if somebody could help me regarding this.
thank you.
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...Could be different things. The first thing to check for
would probably be locking, blocking issues on SQL Server.
You can use sp_who2 to identify blocking. You can use
sp_lock to see what types of locks are occurring, you can
also query sysprocesses in master. You'd probably want to
start with these and go from there.
-Sue
On Tue, 18 Oct 2005 11:12:24 -0700, latha
(rc_forum@.hotmail.com) wrote:

>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>[Microsoft][ODBC SQL Server Driver]Timeout expired
>Hi all,
>I am getting this error while trying to insert a record into the database t
able. We are using SQL SERVER 2000/ODBC/ASP combination.
>I would really appreciate if somebody could help me regarding this.
>thank you.
> ****************************************
******************************
>Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
>Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resourc
es...sql

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver]Timeout expired
Hi all,
I am getting this error while trying to insert a record into the database table. We are using SQL SERVER 2000/ODBC/ASP combination.
I would really appreciate if somebody could help me regarding this.
thank you.
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
Could be different things. The first thing to check for
would probably be locking, blocking issues on SQL Server.
You can use sp_who2 to identify blocking. You can use
sp_lock to see what types of locks are occurring, you can
also query sysprocesses in master. You'd probably want to
start with these and go from there.
-Sue
On Tue, 18 Oct 2005 11:12:24 -0700, latha
(rc_forum@.hotmail.com) wrote:

>Microsoft OLE DB Provider for ODBC Drivers error '80004005'
>[Microsoft][ODBC SQL Server Driver]Timeout expired
>Hi all,
>I am getting this error while trying to insert a record into the database table. We are using SQL SERVER 2000/ODBC/ASP combination.
>I would really appreciate if somebody could help me regarding this.
>thank you.
>************************************************* *********************
>Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
>Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Location: p:\sql\ntdbms\storeng\drs\include\record.inl:1447 Expression: m_SizeRec > 0 && m_SizeRec <= MAXDATAROW SPID: 68 Process ID: 952

Getting the above error when accessing a particular viewI think the some there is some bugs inside the view. if you post the view. i will try

Microsoft OLE DB Provider for ODBC Drivers error 80004005

Hi everybody
My problem with sql server is the following one:
I've got my backoffice manager application done with asp technology
that works on sql server installed on Win2000 and running on IIS5.
what I've done is simply doing a backup of my db and moving the asp
application on another server: Windows 2003 with IIS6 and sql server
vers.8.
Then I tried to set up everything as in the beginning on the previous
machine(Win2K), but I'm getting this error:

Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]Server SQL inesistente o accesso
negato.
(translated would be "SQL Server doesn't exist or access denied")
/sitowebsite/bom/login.asp, line 13

...where in the line 13 is set the connection to the database:
Conn.Open Application("DBsource")

which should be driven by what is set inside the global.asa file:
Application("DBsource")="Provider=SQLOLEDB;server=127.0.0.1;database=db_nam e;uid=db_uid;pwd=db_pwd;"
Application("WS_DB_TYPE") = ( "SQLSERVER" )

I tried to restore the database just not losing information and nothing
happens.
I tried also to create a new user and modify the properties as it
should be from the previous settings in the db(db_owner,...etc), still
nothing.

any clue is appriciated.
many thanks in advance.ziottt (t.giommi@.gmail.com) writes:

Quote:

Originally Posted by

My problem with sql server is the following one:
I've got my backoffice manager application done with asp technology
that works on sql server installed on Win2000 and running on IIS5.
what I've done is simply doing a backup of my db and moving the asp
application on another server: Windows 2003 with IIS6 and sql server
vers.8.
Then I tried to set up everything as in the beginning on the previous
machine(Win2K), but I'm getting this error:
>
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]Server SQL inesistente o accesso
negato.
(translated would be "SQL Server doesn't exist or access denied")
/sitowebsite/bom/login.asp, line 13

This error message that the application cannot reach the SQL Server
you are trying to connect to. Thus, users or backups have no importance,
because you don't reach that far.

Quote:

Originally Posted by

...where in the line 13 is set the connection to the database:
Conn.Open Application("DBsource")
>
which should be driven by what is set inside the global.asa file:
>
>Application("DBsource")="Provider=SQLOLEDB;server=127.0.0.1;database=db_nam
>e;uid=db_uid;pwd=db_pwd;"

And SQL Server is running on the same server as the web server? Have you
verified that SQL Server is actually running?

Diclaimer: I don't know ASP, so if there are any problems with that
global.asa, I can't tell.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Microsoft OLE DB Provider for ODBC Drivers

I am using an system ODBC created to access data on an AS/400.
I can access the data fine, using the following query.
SELECT F0101.* FROM CRPDTA.PILGRIM.CRPDTA.F0101 as F0101
where the first CRPDTA is the DSN name, PILGRIM is the AS/400 catalog,
the second CRPDTA is the SCHEMA, and F0101 is the file name.
When I try to save this query as a view, I receive the following error.
The operation could not be performed because the OLE DB provider
'MSDASQL' was unable to begin a distributed transaction.
[OLE/DB provider returned message: [IBM][Client Access Express ODBC
Driver (32-bit)]Option type out of range.]
OLE DB error trace [OLE/DB Provider 'MSDASQL'
ITransactionJoin::JoinTransaction returned 0x8004d00a]
Can anyone help?
PMGBoy
On several occasion a bug in the ODBC driver causes all sorts of problem
in the client. Try using any third party software, such as WinSQL
(http://synametrics.com/winsql) and see if you get the same behavior.
This would eliminate the possibility of a buggy driver.
jeff.jones@.papermagic.com wrote:
> I am using an system ODBC created to access data on an AS/400.
> I can access the data fine, using the following query.
> SELECT F0101.* FROM CRPDTA.PILGRIM.CRPDTA.F0101 as F0101
> where the first CRPDTA is the DSN name, PILGRIM is the AS/400 catalog,
> the second CRPDTA is the SCHEMA, and F0101 is the file name.
> When I try to save this query as a view, I receive the following error.
> The operation could not be performed because the OLE DB provider
> 'MSDASQL' was unable to begin a distributed transaction.
> [OLE/DB provider returned message: [IBM][Client Access Express ODBC
> Driver (32-bit)]Option type out of range.]
> OLE DB error trace [OLE/DB Provider 'MSDASQL'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]
> Can anyone help?
> PMGBoy
>

Microsoft OLE DB Provider for ODBC Drivers

I am using an system ODBC created to access data on an AS/400.
I can access the data fine, using the following query.
SELECT F0101.* FROM CRPDTA.PILGRIM.CRPDTA.F0101 as F0101
where the first CRPDTA is the DSN name, PILGRIM is the AS/400 catalog,
the second CRPDTA is the SCHEMA, and F0101 is the file name.
When I try to save this query as a view, I receive the following error.
The operation could not be performed because the OLE DB provider
'MSDASQL' was unable to begin a distributed transaction.
[OLE/DB provider returned message: [IBM][Client Access Express O
DBC
Driver (32-bit)]Option type out of range.]
OLE DB error trace [OLE/DB Provider 'MSDASQL'
ITransactionJoin::JoinTransaction returned 0x8004d00a]
Can anyone help?
PMGBoyOn several occasion a bug in the ODBC driver causes all sorts of problem
in the client. Try using any third party software, such as WinSQL
(http://synametrics.com/winsql) and see if you get the same behavior.
This would eliminate the possibility of a buggy driver.
jeff.jones@.papermagic.com wrote:
> I am using an system ODBC created to access data on an AS/400.
> I can access the data fine, using the following query.
> SELECT F0101.* FROM CRPDTA.PILGRIM.CRPDTA.F0101 as F0101
> where the first CRPDTA is the DSN name, PILGRIM is the AS/400 catalog,
> the second CRPDTA is the SCHEMA, and F0101 is the file name.
> When I try to save this query as a view, I receive the following error.
> The operation could not be performed because the OLE DB provider
> 'MSDASQL' was unable to begin a distributed transaction.
> [OLE/DB provider returned message: [IBM][Client Access Express
ODBC
> Driver (32-bit)]Option type out of range.]
> OLE DB error trace [OLE/DB Provider 'MSDASQL'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]
> Can anyone help?
> PMGBoy
>sql

Microsoft Drivers for Accessing data from Unix.

Are there any microsoft provided ODBC drivers that can be installed on Unix
side for accessing SQL Server data? OR they are only available from third
party.
Regards,
MZeeshan
MS does not provide an ODBC driver that works on Unix. However, you can
get that from Data Direct. Microsoft does make a JDBC driver though.
MZeeshan wrote:
> Are there any microsoft provided ODBC drivers that can be installed on Unix
> side for accessing SQL Server data? OR they are only available from third
> party.
>
|||Hi MZeeshan,
Thanks for your post.
Unfortunately, I am sorry to say that we do not support ODBC drivers for
UNIX officially. However, I have noticed here is a very good article from
MVP Erland Sommarskog for your reference
Connecting to MS SQL Server from Unix
http://www.sommarskog.se/mssql/unix.html
Hope it helps.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Microsoft Drivers for Accessing data from Unix.

Are there any microsoft provided ODBC drivers that can be installed on Unix
side for accessing SQL Server data? OR they are only available from third
party.
Regards,
MZeeshanMS does not provide an ODBC driver that works on Unix. However, you can
get that from Data Direct. Microsoft does make a JDBC driver though.
MZeeshan wrote:
> Are there any microsoft provided ODBC drivers that can be installed on Uni
x
> side for accessing SQL Server data? OR they are only available from third
> party.
>|||Hi MZeeshan,
Thanks for your post.
Unfortunately, I am sorry to say that we do not support ODBC drivers for
UNIX officially. However, I have noticed here is a very good article from
MVP Erland Sommarskog for your reference
Connecting to MS SQL Server from Unix
http://www.sommarskog.se/mssql/unix.html
Hope it helps.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Messed up SQL 2000 - Error Code 193

Somehow my SQL Server 2000 installation got messed up and refuses to run. I
narrowed it down, I believe, to a problem of the DLL drivers for SQL Server
being out of sync with the location the Registry had for them.
When I now attempt to create a SQL Server ODBC connection, I get:
"The setup routines for the ODBC Driver could not be loaded due to System
Error Code 193." I then get a message about the translator files failing.
I tried installing the latest MDAC, but it says my operating system already
has MDAC and won't install them.
Anyone ever see this...and have any ideas on fixing this and getting my SQL
Server running again?
Much thanks,
B. Rosman
Chicago, IL
Rosman Computing said (on or about) 12/10/2006 03:28:
> Somehow my SQL Server 2000 installation got messed up and refuses to run. I
> narrowed it down, I believe, to a problem of the DLL drivers for SQL Server
> being out of sync with the location the Registry had for them.
> When I now attempt to create a SQL Server ODBC connection, I get:
> "The setup routines for the ODBC Driver could not be loaded due to System
> Error Code 193." I then get a message about the translator files failing.
> I tried installing the latest MDAC, but it says my operating system already
> has MDAC and won't install them.
> Anyone ever see this...and have any ideas on fixing this and getting my SQL
> Server running again?
> Much thanks,
> B. Rosman
> Chicago, IL
I ran into a similar problem with the ODBC Setup. In my case the SQL
Server was not affected because it was running on a server and the
ODBC Setup problem occurred on the client.
As I recall, the situation came about because the client PC had a
newer version of MDAC on it than the one on the SQL Server
installation disc. When I used the SQL Server installation disc to
install the SQL Server tools on the client, the ODBC Setup programs
went out of sync and when I tried to either create a new ODBC
connection (or modify an existing one) I got an error about not being
able to load the setup routines.
I was never able to resolve the problem. Since I only had one
application that needed to access SQL Server and it already had a
valid connection, it wasn't a big problem. When I needed to make a
second connection to a different db (test instance), I just looked at
the various registry settings for the existing one and duplicated them
for the 2nd. I no longer have the problem because that client PC was
recycled and I made sure that the SQL Server tools were installed on
the new one before I did anything like upgrading MDAC.
|||I was able to fix it anyway. I installed the SQL Server 2000 Server Pack, and
that automatically installed the SQLSRV32.DLL into the system directory. It
worked after doing that.
Thanks,
Bill r.
"DGA" wrote:

> Rosman Computing said (on or about) 12/10/2006 03:28:
> I ran into a similar problem with the ODBC Setup. In my case the SQL
> Server was not affected because it was running on a server and the
> ODBC Setup problem occurred on the client.
> As I recall, the situation came about because the client PC had a
> newer version of MDAC on it than the one on the SQL Server
> installation disc. When I used the SQL Server installation disc to
> install the SQL Server tools on the client, the ODBC Setup programs
> went out of sync and when I tried to either create a new ODBC
> connection (or modify an existing one) I got an error about not being
> able to load the setup routines.
> I was never able to resolve the problem. Since I only had one
> application that needed to access SQL Server and it already had a
> valid connection, it wasn't a big problem. When I needed to make a
> second connection to a different db (test instance), I just looked at
> the various registry settings for the existing one and duplicated them
> for the 2nd. I no longer have the problem because that client PC was
> recycled and I made sure that the SQL Server tools were installed on
> the new one before I did anything like upgrading MDAC.
>

Messed up SQL 2000 - Error Code 193

Somehow my SQL Server 2000 installation got messed up and refuses to run. I
narrowed it down, I believe, to a problem of the DLL drivers for SQL Server
being out of sync with the location the Registry had for them.
When I now attempt to create a SQL Server ODBC connection, I get:
"The setup routines for the ODBC Driver could not be loaded due to System
Error Code 193." I then get a message about the translator files failing.
I tried installing the latest MDAC, but it says my operating system already
has MDAC and won't install them.
Anyone ever see this...and have any ideas on fixing this and getting my SQL
Server running again?
Much thanks,
B. Rosman
Chicago, ILRosman Computing said (on or about) 12/10/2006 03:28:
> Somehow my SQL Server 2000 installation got messed up and refuses to run.
I
> narrowed it down, I believe, to a problem of the DLL drivers for SQL Serve
r
> being out of sync with the location the Registry had for them.
> When I now attempt to create a SQL Server ODBC connection, I get:
> "The setup routines for the ODBC Driver could not be loaded due to System
> Error Code 193." I then get a message about the translator files failing.
> I tried installing the latest MDAC, but it says my operating system alread
y
> has MDAC and won't install them.
> Anyone ever see this...and have any ideas on fixing this and getting my SQ
L
> Server running again?
> Much thanks,
> B. Rosman
> Chicago, IL
I ran into a similar problem with the ODBC Setup. In my case the SQL
Server was not affected because it was running on a server and the
ODBC Setup problem occurred on the client.
As I recall, the situation came about because the client PC had a
newer version of MDAC on it than the one on the SQL Server
installation disc. When I used the SQL Server installation disc to
install the SQL Server tools on the client, the ODBC Setup programs
went out of sync and when I tried to either create a new ODBC
connection (or modify an existing one) I got an error about not being
able to load the setup routines.
I was never able to resolve the problem. Since I only had one
application that needed to access SQL Server and it already had a
valid connection, it wasn't a big problem. When I needed to make a
second connection to a different db (test instance), I just looked at
the various registry settings for the existing one and duplicated them
for the 2nd. I no longer have the problem because that client PC was
recycled and I made sure that the SQL Server tools were installed on
the new one before I did anything like upgrading MDAC.|||I was able to fix it anyway. I installed the SQL Server 2000 Server Pack, an
d
that automatically installed the SQLSRV32.DLL into the system directory. It
worked after doing that.
Thanks,
Bill r.
"DGA" wrote:

> Rosman Computing said (on or about) 12/10/2006 03:28:
> I ran into a similar problem with the ODBC Setup. In my case the SQL
> Server was not affected because it was running on a server and the
> ODBC Setup problem occurred on the client.
> As I recall, the situation came about because the client PC had a
> newer version of MDAC on it than the one on the SQL Server
> installation disc. When I used the SQL Server installation disc to
> install the SQL Server tools on the client, the ODBC Setup programs
> went out of sync and when I tried to either create a new ODBC
> connection (or modify an existing one) I got an error about not being
> able to load the setup routines.
> I was never able to resolve the problem. Since I only had one
> application that needed to access SQL Server and it already had a
> valid connection, it wasn't a big problem. When I needed to make a
> second connection to a different db (test instance), I just looked at
> the various registry settings for the existing one and duplicated them
> for the 2nd. I no longer have the problem because that client PC was
> recycled and I made sure that the SQL Server tools were installed on
> the new one before I did anything like upgrading MDAC.
>