ODBC error

Dear all,
We are using Ipswitch email application “ICS 2006’ with SQL 2000
enterprise edition as database. Occasionally web mail users are facing the
below
error on their web page.
‘ERROR [HY001][Microsoft][ODBC Microsoft Access Driver] Not enough space on
temporary disk. ERROR [IM006][Microsoft][ODBC Driver Manager] Driver’s
SQLSetConnectAttr failed ERROR [HY001][Microsoft][ODBC Microsoft Access
Driver] Not enough space on temporary disk.’
The problem gets rectified only after we restart the IIS service on the mail
server. What could be the reason for this problem? Kindly provide me with
your suggestions.
Regards
Ram
It's an error from MS Access - the cause depends on what you
are doing in Access, what version of Access, etc.
Try posting on one of the Access forums or newsgroups.
-Sue
On Sat, 17 Feb 2007 20:59:08 -0800, Ram
<Ram@.discussions.microsoft.com> wrote:

>Dear all,
> We are using Ipswitch email application ICS 2006 with SQL 2000
>enterprise edition as database. Occasionally web mail users are facing the
>below
>error on their web page.
> ERROR [HY001][Microsoft][ODBC Microsoft Access Driver] Not enough space on
>temporary disk. ERROR [IM006][Microsoft][ODBC Driver Manager] Drivers
>SQLSetConnectAttr failed ERROR [HY001][Microsoft][ODBC Microsoft Access
>Driver] Not enough space on temporary disk.
>The problem gets rectified only after we restart the IIS service on the mail
>server. What could be the reason for this problem? Kindly provide me with
>your suggestions.
>Regards
>Ram
>

ODBC error

Dear all,
We are using Ipswitch email application “ICS 2006’ with SQL 2000
enterprise edition as database. Occasionally web mail users are facing the
below
error on their web page.
‘ERROR [HY001][Microsoft][ODBC Microsoft Access Driver] Not en
ough space on
temporary disk. ERROR [IM006][Microsoft][ODBC Driver Manager] Dr
iver’s
SQLSetConnectAttr failed ERROR [HY001][Microsoft][ODBC Microsoft
Access
Driver] Not enough space on temporary disk.’
The problem gets rectified only after we restart the IIS service on the mail
server. What could be the reason for this problem? Kindly provide me with
your suggestions.
Regards
RamIt's an error from MS Access - the cause depends on what you
are doing in Access, what version of Access, etc.
Try posting on one of the Access forums or newsgroups.
-Sue
On Sat, 17 Feb 2007 20:59:08 -0800, Ram
<Ram@.discussions.microsoft.com> wrote:

>Dear all,
> We are using Ipswitch email application ICS 2006 with SQL 2000
>enterprise edition as database. Occasionally web mail users are facing the
>below
>error on their web page.
> ERROR [HY001][Microsoft][ODBC Microsoft Access Driver] Not en
ough space on
>temporary disk. ERROR [IM006][Microsoft][ODBC Driver Manager] D
rivers
>SQLSetConnectAttr failed ERROR [HY001][Microsoft][ODBC Microsof
t Access
>Driver] Not enough space on temporary disk.
>The problem gets rectified only after we restart the IIS service on the mai
l
>server. What could be the reason for this problem? Kindly provide me with
>your suggestions.
>Regards
>Ram
>sql

ODBC Connection using Alternate windows credentials

Hi,
We have a server in a workgroup that users in our active directory
will need to access.
How can we configure an odbc connection to use a different username
and password (windows not sql) than the one they are currently logged
on on as. (The application we are using only supports windows
authentication not sql)
example : I am logged onto my workstaion a 'Jane', but i Need to use
user id 'janey' to connect to the odbc, and i dont want to have to
log
on to the workstation as janey
Hi
Unless you are logged on as the user you wish to authenticate as I don't
think you can do this!
John
"zach" <neopotent@.gmail.com> wrote in message
news:5e0669bb-e86f-4610-8713-5bd06084daa1@.a23g2000hsc.googlegroups.com...
> Hi,
> We have a server in a workgroup that users in our active directory
> will need to access.
>
> How can we configure an odbc connection to use a different username
> and password (windows not sql) than the one they are currently logged
> on on as. (The application we are using only supports windows
> authentication not sql)
>
> example : I am logged onto my workstaion a 'Jane', but i Need to use
> user id 'janey' to connect to the odbc, and i dont want to have to
> log
> on to the workstation as janey
>

ODBC Connection using Alternate windows credentials

Hi,
We have a server in a workgroup that users in our active directory
will need to access.
How can we configure an odbc connection to use a different username
and password (windows not sql) than the one they are currently logged
on on as. (The application we are using only supports windows
authentication not sql)
example : I am logged onto my workstaion a 'Jane', but i Need to use
user id 'janey' to connect to the odbc, and i dont want to have to
log
on to the workstation as janeyHi
Unless you are logged on as the user you wish to authenticate as I don't
think you can do this!
John
"zach" <neopotent@.gmail.com> wrote in message
news:5e0669bb-e86f-4610-8713-5bd06084daa1@.a23g2000hsc.googlegroups.com...
> Hi,
> We have a server in a workgroup that users in our active directory
> will need to access.
>
> How can we configure an odbc connection to use a different username
> and password (windows not sql) than the one they are currently logged
> on on as. (The application we are using only supports windows
> authentication not sql)
>
> example : I am logged onto my workstaion a 'Jane', but i Need to use
> user id 'janey' to connect to the odbc, and i dont want to have to
> log
> on to the workstation as janey
>

ODBC connection prompting for 'sa' password

We use Pivot Tables in Excel to provide users with reports. The Pivot Tables connect to SQL Server via an ODBC connection. In the ODBC connection, SQL Server authentication is specified and the 'sa' user name and password are entered. In prior versions
of Excel, the password would be saved in the Pivot Table. However, in Excel 2003 the user is prompted to enter the 'sa' password in order for the pivot table to update. Is there a way to have Excel 2003 pivot tables function as they did in prior versio
ns so that the password in the ODBC connection does not have to be re-entered?
Don't know much about Excel. But can you create another account (not sa)
to access the DB? This way you can keep your sa password secret.
Eric
Mike wrote:

> We use Pivot Tables in Excel to provide users with reports. The Pivot Tables connect to SQL Server via an ODBC connection. In the ODBC connection, SQL Server authentication is specified and the 'sa' user name and password are entered. In prior versio
ns of Excel, the password would be saved in the Pivot Table. However, in Excel 2003 the user is prompted to enter the 'sa' password in order for the pivot table to update. Is there a way to have Excel 2003 pivot tables function as they did in prior vers
ions so that the password in the ODBC connection does not have to be re-entered?
Eric Li
SQL DBA
MCDBA

ODBC Connection Problem

Hello,
I have an install of SQL that my users cannot connect to with an ODBC
connection. I have created Windows User logins on the SQL server through
Enterprise Manager, and have assigned them access to one specific database.
The specific user accounts have public, db_datareader and db_datawriter
permissions to the database. When the users attemtpt to create their ODBC
connections they receive an access denied message. What other permissions do
I need to give these users? Do they need any other permissions to the actual
server the SQL instance resides on?
Thanks,
JBaileyJBailey,
Please let me know the following:
- These accounts that you created to access that datbase, can they connect
and query the database from query analyser?
- Also, could you please created a UDL to test for connectivity (this gives
us a good idea if the odbc connection is ok). Also it could be that we
arent passing the correct 'connection string'?
Create a text file and name it <anything>.UDL. Rt-click the UDL file and
select Properties. The Connection tab contains all the fields exposed to
the application, and you choose the appropriate items to be filled in to
successfully "Test Connection" before you are able to use it. Once the Test
button works, click on OK and open up the UDL file in Notepad. Its just a
text file, and contains a provider string that you should be able to paste
into your application or whichever application is calling the sql server.
Cheers!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql

ODBC connection failed, but...

Running a database using sql server. User, rights, password set up on the server side and is functioning fine on the users normal desktop. But here is the problem. When the user goes to a different desktop they have never been on before and a new user profile is created on that desktop, they are unable to access the database. When using the front end (access), an odbc connection failure popup occurs when trying to retrieve data. The wierd part is that the odbc connection was set up under admin tools just like it is setup on the working desktop. Also the connection tests successfully. This leads me to believe that it is a desktop side problem and not server side. It is only a problem when a new user profile is setup on a desktop that the user has never been on before.

Any help would be appreciated.

Barry

What is the error the user is getting from the failing desktop - does it say "SQL Server does not exist or access denied"?

Is the SQL Server installed as a default instance listening on the default TCP port 1433 (as opposed to a named instance or a non-default port)?

If the answers are "yes" and "yes", try running

telnet <serverName> 1433

If it reports an error there is an underlying network connectivity problem between the desktop and the server.

If it gives a blank screen the netowkr connectivity works, and further information about your environment and the error may be needed.

You can also follow the checklist posted at

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

|||

Under odbc datasource manager sql setup the libraries is named pipes and the pipes are Serv01and server is serv01, and alias is serv01 as they should be. TCP/IP is Server Serv01 and port is dynamically determined. The exact same setup works under my windows login for myself to access the databse, but will not work when logging in my secretary on my laptop. By the way her name and password are setup correct in the odbc datasource manager. She is able to access the database from her normal workstation though.

The only error we get is odbc connection failure when accessing from the front end at my station. By the way, if I login to her station and go through the sql setup under the odbc manager, I have the same problem at her station that she has at mine.

I'll follow the checklist you posted to see if it helps, but it has to be a local software problem. We'll see though.

Thanks

|||

Nothing like solving your own problem. Well it appears that the naming under the odbc setup manager is highly specific and is not just a name. The problem was that when it asked for a name during setup, "Training Manager" was entered instead of "TrainingManager" without the space. I did not realize that there was connectivity value associated with the name at that point in the setup. The "test connectivity" at the end of the setup will say "successful" with the name written either way, but actually connection to and retrieval of info from the database from front end software will fail.

Hope this helps someone else down the road.

|||

I got the same problem, I am using 2003 server with SQL server 2000. With the same user, I can logon into server but can't create odbc connection beside "SA" login with blank password. This problem happened on our desktop too. Moveover, this problem extend to the application server "Great Plain - Dynamics 9.0". If the user was created on the server side, user can not login properly, unless user's password to be re-entered on the desktop(Windows XP).

I am woundering is the problem caused by encoding issue (Unicode or ASCII). Is there anyone can help?

sql

ODBC Connect from MS Access to SQL Server 2000-Viable?

How viable is it to use MS Access as a front end (via ODBC) to a SQL Server
2000 database?

The users would access via the internet using a netgear vpn setup.

Thanks,

Paul SPaul Stanial wrote:
> How viable is it to use MS Access as a front end (via ODBC) to a SQL Server
> 2000 database?
> The users would access via the internet using a netgear vpn setup.
> Thanks,
> Paul S

I've seen this configuration more as an afterthought. What I mean is
that someone uses Access to design an application, complete with Forms
and Reports. Afterwards, they wish to put the data in SQL Server, but
they don't want to redo their Forms and Reports. From those projects
that I've moved the data to SQL Server, things have worked really well.

That being said, if this was a new application, I'd be deploying
something web-based (since you indicated that your users would access
via the internet). With many of the web-based tools out there, you can
quickly create applications as well.

HTH,
Brian

--
================================================== =================

Brian Peasland
dba@.remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.

"I can give it to you cheap, quick, and good. Now pick two out of
the three"

ODBC and Enterprise Manager (still) don't show databases with users other than sa

I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
and only one of them developed this problem. When trying to set up a
new ODBC setting using any other login than sa, it doesn't show any
databases besides the system db's. When logging in with Enterprise
manager (all other logins except sa), the Databases list shows 'No
items'. All logins work fine with Query Analyzer. I already recreated
missing guest accounts in some of the databases, but that didn't help.
I've also installed the latest MDAC (2.7 SP1) and after that didn't
correct the problem, I installed SP3a. It's still not working.
I'm thinking about reinstalling SQL Server, but my client doesn't like
the idea. So if anyone has any idea what might help, I'd be greatful.
Thank you!
br,
AnnaAnna
Firstly you need to have SQL SP3 if you have not applied the patch to stop
the SQL Slammer on the server.
Are you using ODBC/ Query Analyzer from the server or the client?
I am getting a few problems as well after install MDAC 2.71 which has
somehow deleted my ODBC drivers from the Drivers tab window.
Regards
Z
Is the SQL a named instance?
"Anna N." <amnikol@.hotmail.com> wrote in message
news:6e225598.0307160146.5fadd9f2@.posting.google.com...
> I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
> and only one of them developed this problem. When trying to set up a
> new ODBC setting using any other login than sa, it doesn't show any
> databases besides the system db's. When logging in with Enterprise
> manager (all other logins except sa), the Databases list shows 'No
> items'. All logins work fine with Query Analyzer. I already recreated
> missing guest accounts in some of the databases, but that didn't help.
> I've also installed the latest MDAC (2.7 SP1) and after that didn't
> correct the problem, I installed SP3a. It's still not working.
> I'm thinking about reinstalling SQL Server, but my client doesn't like
> the idea. So if anyone has any idea what might help, I'd be greatful.
> Thank you!
>
> br,
> Anna|||FYI:
First, I would try determine if it is an Server or Client Problem. ( The
Server has both Client and Server DLLs on it.)
To see if it is an client problem try to make the ODBC from a machine
without the problem to the Server with the problem.
If the problem is NOT there then it is an client problem.
If the problem is there confirm it by making an ODBC connect to one of the
Good Servers from the same test client.
If it is an server problem, I have nothing to suggest.
( Note my company spent over 40 man hours on an "Server Problem" that
turned out to be an client DLL issuse in SQL SP3)
If an client problem.
First check the version of SQLSRV32.dll ; is the correct one.
Link to version of SQLSRV32.dll
http://support.microsoft.com/default.aspx?scid=http%3a%2f%2fsupport.microsoft.com%2fservicedesks%2ffileversion%2fdllinfo.asp&fp=1
Then, I would try running the component checker ( on the MDAC ).
Link to info on component checker
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307255
Link to download componet checker
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en
Tim S
"Zenduce" <james@.zenduce.net> wrote in message
news:%238XHwp4SDHA.1664@.TK2MSFTNGP11.phx.gbl...
> Anna
> Firstly you need to have SQL SP3 if you have not applied the patch to
stop
> the SQL Slammer on the server.
> Are you using ODBC/ Query Analyzer from the server or the client?
> I am getting a few problems as well after install MDAC 2.71 which has
> somehow deleted my ODBC drivers from the Drivers tab window.
> Regards
> Z
>
> Is the SQL a named instance?
> "Anna N." <amnikol@.hotmail.com> wrote in message
> news:6e225598.0307160146.5fadd9f2@.posting.google.com...
> > I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
> > and only one of them developed this problem. When trying to set up a
> > new ODBC setting using any other login than sa, it doesn't show any
> > databases besides the system db's. When logging in with Enterprise
> > manager (all other logins except sa), the Databases list shows 'No
> > items'. All logins work fine with Query Analyzer. I already recreated
> > missing guest accounts in some of the databases, but that didn't help.
> > I've also installed the latest MDAC (2.7 SP1) and after that didn't
> > correct the problem, I installed SP3a. It's still not working.
> >
> > I'm thinking about reinstalling SQL Server, but my client doesn't like
> > the idea. So if anyone has any idea what might help, I'd be greatful.
> > Thank you!
> >
> >
> > br,
> > Anna
>|||"Zenduce" <james@.zenduce.net> wrote in message news:<#8XHwp4SDHA.1664@.TK2MSFTNGP11.phx.gbl>...
> Firstly you need to have SQL SP3 if you have not applied the patch to stop
> the SQL Slammer on the server.
I already have SP3a installed, as you can see from my original post.
> Are you using ODBC/ Query Analyzer from the server or the client?
Several clients.
> I am getting a few problems as well after install MDAC 2.71 which has
> somehow deleted my ODBC drivers from the Drivers tab window.
This problem emerged BEFORE installing MDAC 2.71, as you can see from
my original post.
> Is the SQL a named instance?
No.
- Anna|||"Tim S" <stahta01@.juno.com> wrote in message news:<XamRa.4637$C71.307@.fe01.atl2.webusenet.com>...
> First, I would try determine if it is an Server or Client Problem. ( The
> Server has both Client and Server DLLs on it.)
It is most definitely a server problem. I wouldn't have posted a
question without making sure where the problem is exactly.
- Anna