.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Accessing SQL Server via ODBC on 64-bit Windows 7

Posted By:      Posted Date: October 19, 2010    Points: 0   Category :Sql Server
I inherited an app written in Visual C++ 6.0 Pro and it uses ODBC to talk to a SQL Server 2005.  This works fine on XP and 32-bit Win7 systems.  I've installed the app on my Win7 x64 system and it also works fine except that when it tries to open any of the same SQL Server tables it dies.  This is also true on a remote 64-bit Win7 system.  This happens when the app tries to make a connection to SQL Server on a CDatabase::OpenEx due to an Unhandled Exception with an "MFC Application has stopped working" error message.  Not surprisingly, when I build and run the app on the Win7 system the same thing happens.  Another piece to the puzzle is that on my Win7 system when I try to add a new CRecordset class for a DB on the server, the New Class wizard can't "see" any of the DBs there even though I have my system data source correctly defined in my ODBC Data Source Admin.  I can see the databases when I try to create a new class on my XP system though.  I can access the DBs on the server via my MS SQL Server Management Tool on both Win7 and XP though.  The version of ODBC running on the Win7 system is 6.1.  When I go to my Control Panel for adjusting my computer settings it lists "ODBC (32-bit)" which is where I set up my System DSN.  I'm wondering if it really is 32-bit.  Any idea

View Complete Post

More Related Resource Links

ODBC connection to SQL Server 2005 Standard (on windows xp) with Windows authentication does NOT wor

I reviewed lots of postings, still could not find an answer. If I choose Windows authentication: - with TCP/IP and "Dynamically determine port" checked, I get the following error "The user is not associated with a trusted SQL Server connection; - with Named Pipes, Server Name & Pipe Name as "VSAXAONG", I get two errors, one after the other on the same pop-up:       Connection failed  SQL State 01000  SQL Server Error 1385 [Microsoft] [ODBC SQL Server Driver] [Named Pipes] ConnectionOpen (Connect()).       Connection failed  SQL State 08001 SQL Server Error 17 [Microsoft] [ODBC SQL Server Driver] [Named Pipes] SQL Server does not exist or access denied. If I choose SQL Server authentication and fill in the password - the ODBC connection works fine. I have to say that I created two different logins on the server, one for Windows authentication, and one for SQL Server authentication - both for the same Windows user name. I would appreciate any help I can get on this.  Thank you all in advance.

SQL Server 2005 Express ODBC connection error with Windows Vista Business

I have a SQL Server 2005 Express Edition installed on a Windows Server 2003 domain machine. When I do a connection with a client running Windows XP through the SQL 2008 ODBC driver I have no problem.  The problem is when I try to establish a connection using a client running Windows Vista Business Edition which is a member of the domain. Please help me to solve this issue.

Thanks in advance
Danilo Bucheli Sánchez

Windows 7 Home accessing SQL Server running on a WindowsXP Pro machine

I have a client running a program that uses SQL Server 2005 Express running on a WindowsXP Pro machine.  It runs just fine on the WindowsXP machine, even under several different Windows logins that SQL Server has been told are permitted.  Using a Windows 7 Home Premium machine, in trying to set up the ODBC driver to point the program to the SQL Server database on the WindowsXP machine, an error is returned indicating that it is not permitting a connection for the client machinename\Guest.  Of course, the Windows 7 machine is logged on with the same login name and password as is permitted on the WindowsXP machine, but apparently the Win 7 Home machine is not transmitting that login and password allowing the login to SQL Server to be validated through the use of Windows NT 2000 authentication.  This always works with a WindowsXP Pro workstation.  Is my problem that their workstation machine is running a HOME version, or is there some other solution to make the Win7 machine transmit the real login and password instead of trying to log in as Guest?  Networking is letting the Win 7 machine explore shared files and folders in the XP machine since those are not requiring a valid ID and password.

Problem connecting using ODBC from Windows Server 2008R2 x64




I have strange problem: when I'm trying to create new “System DSN” (ODBC Data Source Administrator) using either SQL Native Client or “integrated” SQL Serve source I’m getting next:

Connection failed:

SQLState: '08001'

SQL Server Error: 1326

[Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [1326].

Connection failed:

SQLState: 'HYT00'

SQL Server Error: 0

[Microsoft][SQL Server Native Client 10.0]Login timeout expired

what strange for me – is that I can create this Data Source either on the other machine (Windows XP there) or on the server host (Server 2008 x64)…

Windows Firewall turned off on that host and I have no idea what to check next…

Any help appreciated.


Best regards...

ODBC from Windows 7 client to SQL 2008 R2 server


I get an intermittent error when trying to connect to the SQL backend.  I am using the SQL Server Native Client 10.0 for my connection and it was created with no problems.  I am using it to access Dynamics GP 2010 data on the SQL backend.  SOMETIMES when logging into GP I will get a message (after about 5 minutes) stating that my login info could not be verified.  Other times I get in just fine.  When I try to troubleshoot this by "configuring" my DSN, I sometimes get stopped when trying to obtain default setting (or testing the connections) - other times it flies right thru without errors.  I am able to use the same ODBC connection (except that it is the SQL Native Client) from Windows 2008 servers, workstations running XP; but not reliably from my 32-bit Windows 7 machine. 

Any ideas?  Thanks in advance.

Hal Steinkopf.

Accessing SharePoint 2010 Data with Server-Side APIs

Accessing SharePoint data in server-side solutions is one of the most common tasks that you will perform as a SharePoint developer. SharePoint 2010 provides powerful server-side APIs that enable you to retrieve, add, edit, and delete SharePoint data programmatically. SharePoint 2010 also includes the new LINQ to SharePoint technology that enables you to work with SharePoint data efficiently and easily.

Word Automation Issue in Windows Server 2008 Hosting



The problem I am posting here is that I was facing nearly 2 weeks around. Any body comes with this stuff please help.

Word Automation in sample ASP.NET(C#) application.

I am using Microsoft.Office.Inetrop.Word Assembly for automation. Here I am reading a XXX.dot template file and fill the contents with dynamic data.

When i am executing my code in localhost:someportnumber the automation is working fine and I could get expected result and when I am hosting in my inetmgr(Windows XP is my OS) it is also working fine.

But the problem is that when I am hosting in my production server(Windows Server 2008 Standard Edition) I am not able to perform automation and results in the following error.

Data: System.Collections.ListDictionaryInternal
Message: Word has encountered a problem.
Source: Microsoft Word

The code gets failed in the following line:

ApplicationClass wordApp = new Microsoft.Office.Interop.Word.ApplicationClass();

Document wordDoc = wordApp.Documents.Add(ref oTemplate, ref oFalse, ref oMissing, ref oMissing); // Error in this line

I cannot able to proceed further. Can anybody please help me in solving this issue?

Thank you.

With Regards,


No ASPNET User in Windows Server 2008?


I have been looking everywhere online regarding this, but have not found a clear answer.


I have an ASP.Net app running on Windows Server 2008, it's basically a reporting app using Crystal Reports. I have encountered a roadblock in regards to rendering some pages. When I run the app in Visual Studio(on the same 2008 machine) everything works perfectly. Yet when I publish it and run it live the reports will not display correctly, I get a message saying Failed to render page.


I looked this error up in the Crystal Reports website and the fixes they have there refer to giving the windows "aspnet" user full access rights to certain folders on the machine. I would be happy to do this, however there is no aspnet user in Windows Server 2008.


I installed the server and set its role to be Web Server. I also checked all the options regarding ASP.Net and IIS 6 compatibility. Yet there is no ASPNET username anywhere.


Did I set the server up wrong? or do I have to do something within ASP.Net to  create this user and then give it rights? 

Not working on Windows Server 2008




I had the CSS friendly adapters working great on our old server (windows server 2003 - 32bit) and now we have moved to a 64 bit environment and now I can not get the CSS friendly adapters to work.

We are using SharePoint 2007.

Is there another work thru for 64bit environment.

I notice windows server 2008 has a directory  C:\Windows\Microsoft.NET\Framework64 would I be using the browser file in this directory???

Please help!

{ End Bracket }: Customize Windows Home Server


Chris Gray discusses custom applications he's developed for Windows Home Server and explores applications for energy savings.

Chris Gray

MSDN Magazine July 2008

Built For Speed: Develop Turbocharged Apps For Windows Compute Cluster Server


This article explores the services provided by Compute Cluster Server 2003 and the tools provided by Visual Studio 2005 that will help you develop High-Perfomance Computing applications.

Rich Ciapala

MSDN Magazine April 2006

Windows Server 2003: Discover Improved System Info, New Kernel, Debugging, Security, and UI APIs


There's a lot to say about Windows Server 2003. First of all, it's the first operating system with built-in .NET Framework support, and it's the first 64-bit OS from Microsoft. But wait, there's more! There are lots of new features and APIs in this version as well. For instance, Windows Server 2003 features Hot Add Memory and a number of other arcane new tidbits. There are new APIs for handling threads, directories, and files, and new features like the low fragmentation heap for managing memory and system information. There's vectored exception handling and new UI APIs as well.OS internals expert Matt Pietrek takes a look at the additions he finds most interesting and useful so you'll have a good place to start when you dive into Windows Server 2003.

Matt Pietrek

MSDN Magazine June 2003

Security Briefs: Exploring S4U Kerberos Extensions in Windows Server 2003


Building Web sites that provide services external to the corporate firewall is tricky. Usually it's not desirable to grant corporate domain accounts to external clients, and from a purely practical standpoint Kerberos does not work well over the Internet due to the typical configuration of client-side firewalls.

Keith Brown

MSDN Magazine April 2003

How can Install Office 2007 on Windows server 2008 R2 64 bit machine in WSS 3.0

I have  64 bit machine  and Windows server 2008 R2 has installed. i have successfully install WSS 3.0  , but  when i tried to install  office 2007 ,  one  error  has  come  "OS is not compatible "  i thought  it was asking  for 64 bit office  2007   and i go through the  google and R&d find no 64 bit office is available ,  i have used   excel .dll in my custom code  so my problem is that   how can  install office 2007  on 64 bot OS 2008 r2  machine .  if anyone can help   me  , please let me know . thanks in advance

Office Sharepoint Server Search not working but Windows Server Search is.

I am having an annoying Issue with the Sharepoint 2007 Enterprise search functionality. I cannot get the Search Centre to work, the out of the box webparts crash the page except the Searchbox when the others are closed. The event viewer shows up numerous Errors (Office Sharepoint Server - EventID 7080) returns with and the same when trying to add a search related web part (e.g. core.results, federated etc). EventID 6398 - Timer is a regular as is 7080. Details below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).

Remote connections are connected, I am not 100% on the Instance name, (how would I go about checking this?)

Also I cannot access the link to SharedServices1 - Open Shared Services Admin site (not clickable), guess it's permissions but I seem to have full site permissions, I think I need SSP-Admin to make more edits to the Search, maybe this is related :s

Both Search Servers are runnig, I have tried everything I can think of to fix this and allow the Search Centre to work.

I am running Sharepoint 2007 on SQL Server 2008.

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend