.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

Migration of DSN use for SQL Server access from Windows SP-3 clients to Windows 7 64 bit client

Posted By:      Posted Date: September 02, 2010    Points: 0   Category :Sql Server
We have numerous apps which use a named DSN using SQLSRV32.dll for an ODBC connection from our Windows XP-Pro SP3 32 bit machines client access to remote windows 2003 based SQL servers (mix of 2005 and 2008).  On migrating to Windows 7, this dll will not allow the apps to use the newly constructed DSN (using SQLSRV32.dll with ODBC), even though a test connection is sucessful (abbeit much slower than seen on the XP-Pro machines).  What must I use on the Windows 7 64 bit machine to allow a DSN to be used by the migrated apps?  - I have descerned through Google that WDAC is now the tool to use, but I am cluless how to use it. - The expectations from the app on the Windows XP-Pro and on the Windows 7 64 bit machines is to use a DSN to connect to SQL servers on Windows 2003. I would appreciate any advice, and thanks!

View Complete Post

More Related Resource Links

How to host self hosting wcf in Windows Server and access from client


  Am developing a windows application. i am using SqlServer in my server and WCF as connecting bridge between the Server and client. My client want to run the WCF in server as self hosting and they will access the wcf from the client. Is it possible?. How can i achive this.

Remote access to SQL-Server 2008 R2 on Windows Server 2008 denied

Hello, after successful installation of SQLServer 2008 R2 and providing my account as a 'sysadmin' I failed to access the server from a management studio of a SQL-Server 2005 release installation. The TCP/IP access is enabled and the server is configured to allow access from remote connections.  The error message reads a follows: ' A network-related or instance-specific error occured while establishing a connection to SQL Server. The server was not found or was not accessible. Verify ... (Provider: Named Pipes Provider, error 40 - Could not open a connection to SQL Server)(Microsoft SQL Server, Error:2)' Accessing the SQL-Server by the management studio from the local host works fine but trying to acces by command line using the '-E' parameter fails. Is there any additional configuration on the operation system level needed to open a SQL-Server 2008 instance to be selected by other members of  domain groups from the non-local host? Thank you for the answer  

SQL server client tool installation on windows XP?

Hi My desktop is Windows XP sp3 and have office 2010, sql express 2005 management studio and Visual studeio 2008 sp1 installed.  We have a SQL R2 server installed last week.  I was able to use sql 2005 management studio to connect to the new sql 2008 R2.  Question is when i try to install 2008 R2's client tool using the 2008R2 iso image.  It look for windows installer 4.5 as prerequisite.  It fail in installing windows installer 4.5 with msg saying I am not the administrator and it require administrator right.  But I am logging in as administrator on local pc.  I also confirmed with our IT/Server guys and they confirmed that I have the admin right.  Then, I tried the following steps: a) reboot, log in as administrator locally b) checked eventviewer, no error/warning msg that stand out to me c) turn off symantec antivirus d) download windows installer 4.5 (WindowsXP-KB942288-v3-x86.exe   - install it locally   - run as administrator to install All the above steps seems not working, I am kind of out of idea.  Could some on please kindly help out.  All I need is the 2008 management studio and profiler install on my PC.  thank you, Ted.  

How to access RAM above 32gb on Windows 2003 Server Standard x64?

My employers went and maxed out their database server for RAM to 64gb from 32gb. It's running SQL Server 2005 x64 on Windows 2003 Server Standard x64. As far as i'm aware of, 32gb is the RAM limit for the OS but does sql server have the ability to see beyond this limit? I'm about to ship the RAM back... Any insights would be greatly appreciated!

Windows WCF client with internet proxy server showing error The server committed a protocol violatio


Our team trying to create a windows application(c#) to call a WCF service using internet proxy server

Showing exception "The server committed a protocol violation. Section=ResponseStatusLine" while calling WCF service

Please give suggestion to solve this problem/any alternative solution


//Code for creating proxy
public static DevicesServiceClient CreateProxy()
var proxy = new DevicesServiceClient("BasicHttpBinding_IDevicesService");

BasicHttpBinding binding = new BasicHttpBinding();
.Security.Mode = BasicHttpSecurityMode.None;

TCP Error Code 10060 when attempting to access WCF Service hosted by WIndows Service from client run


Hello all,

We have a Framework 3.5 WCF Service which is in turn hosted in a Windows Service using Net.Tcp Binding. SvcUtil is used to generate the proxy which is used instead of a service reference in the client code. We are also using Tcp Port Sharing. The endpoint address is net.tcp://HostMachineName/MyServicePath. The service logs to the Event log and everything works perfectly on the same machine.

When attempting to run the client from a different machine we are getting TCP Error Code 10060 errors. Below is the error message:

System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://HostMachineName/MyServicePath. The connection attempt lasted for a time span of 00:00:20.8592415. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 111.22.333.444:808.  ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 111.22.333.444:808... The IP Address displayed was the correct IP Address for the HostComputerName.

Has anyone encountered this problem? Also, client specs say no config files, so anything that wo

Net.TCP Endpoint; Windows Authentication security; client can connect to a server at localhost but n


Hey all, so here's what going on:

I have a WCF Service that I have setup as a Windows Service.  Everything works perfectly when I attempt to use the system with all of the components (i.e. server and clients) on the same machine.  However, when I try to connect my client from a different system, I get an error that is trying to tell me that the server rejected the client's credentials.

I need the client to the able to connect from a different machine.  I want to implement a SQL Role Provider kind of credentialing in the future, but for now, I just need it to work.

What I have tried
I have looked around online and read a few other posts as well some things in the MSDN KB and I have either not found the answer, or not understood it.

  • I have tried setting the <security mode="Transport"> to "None" with the hope that that would disable the accreditation entirely.  All it did was result in a different error saying that there was an error that might have been caused by an invalid message.  I have also tried a few other configurations with this element in the app.config file; to no success.
  • I have read some things about Impersonation, but I am not quite sure I understand how to implement it

WSS 3.0 seach fail after migration from Windows Server 2003 with SQL 2000 to Windows Server 2008 wit


Hello we have a WSS 3.0 on a Windows Server 2003 with a single site, and we are trying to migrate it to another server with Windows Server 2008. All database are on a Microsoft SQL Server 2000.

We installed WSS 3.0 from scratch on the new server. We put the default databases on a server with Microsoft SQL Server 2008.

Then we made a backup in the production server with the following command: stsadm -o backup -url https://portal -filename musa.bak

After that we restored the backup in the new server with the following command:  stsadm -o restore -url https://uymvd18 -filename c:\sharepoint\portal-2010-10-05-21-00-06.dat -overwrite

(portal is the name of the old server and uymvd18 is the name of the new one)

Everything worked ok, but the when we try to do a search in the new se

Login is valid, but server access failed. Windows App can't login unless assigned SysAdmin.


I put a similar plea for help in the ADO forum but haven't gotten responses. I have a feeling this is a better place to put this post. If someone thinks it should go elsewhere please let me know.

I've been stuck on this problem for a day and a half. I wrote a windows form application in C# that works flawlessley for myself and the other network admins. As soon as a normal user tries to use it it fails.

Our environment has XP workstations. SQL Server 2005 Enterprise Edition, on Windows 2003 server.

My application makes several connections but I wrote it so that it would test and give give meaningful error mesages every time it tried to connect to SQL server. The very first connection it tries to make fails, which thankfully forces the application to exit before ay other connections are made. This first piece is very simple. It runs a stored procedure that adds the user name and the current time to a table. For normal users, I instantly get the error "Login failed for Domain\User". When I looked at the SQL Server logs, I see [Error :18456, Severity:14, State: 11.] which is telling me that the Login is valid, but server access failed.

We suspected it was a domain rights issue since the network admins can run the aplication successfully, but as it turns out the network admins and developers all have the SQL role "sysadmin". If

Login is valid, but server access failed. Windows App can't login unless assigned SysAdmin.


I'm not sure if this belongs here or in a SQL Server forum.  It's an ADO.NET application though so I'm posting it here first.

Here is our environment.  XP workstations.  SQL Server 2005 Enterprise Edition, on Windows 2003 server.

We are putting together our first C# windows-based SQL application.  We want to install it on 50 to 100 workstations.  The first piece is very simple.  It starts by running a stored procedure which adds the user name and the current time to a table.   

If I put a test user into the SQL Server role [sysadmin] it works flawlessly.  If the user is not assigned that role I get the error "Login failed for Domain\User".  When I looked at the SQL Server logs, I see [Error :18456, Severity:14, State: 11.] which is telling me that the Login is valid, but server access failed.  Obviously, I don't want to give all our users sysadmin rights.


Essentially, we're trying to figure the minimum security settings that will allow our windows users to read, write, and delete from tables in a database, and execute stored procedures.  We thought we understood the security settings but we're missing something.  I don't know how to start with "sysadmin" and remove priveleges one at a time.

Here are a few things w

WCF Windows Auth (NTLM) Problem when Client and Server are on the same machine


I have WCF service being hosted in IIS with windows auth enabled, it is running under NetworkService account .  I have a simple method on my WCF service which just reflects the identity of who is calling it.


public string RefelctIdentity()



return HttpContext.Current.User.Identity.Name;


I am using IIS to authenticate the user and pass me the WindowsPrincipal in the HTTP context.

I am consuming the WCF service witha client used in a WindowsService that is being run under the NetworkService account.  When the WindowsService.  When running b

C#, sockets, Windows and port 21 : A simple Client-server using TCP; connection dies after transfer



I have a thread on Stackoverflow here:


In short: 

In a very VERY simple Client-Server solution the TCP connection dies after sending 65535 bytes. This only happens when I am connected on port 21. If I change the server port to for example port 22 the connection does not die.

I am posting the simple code here for reference.


using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Net;
using System.Threading;
using System.Net.Sockets;

namespace tWorks.Samcom.PassSocketPoller
  public class PollerTest2
    private IPAddress _sutiSocketIpAddr;
    private int _sutiSocketPort;

    private Thread pollerThread = null

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.

SQL Server Install Materials Cannot Access Windows Installer


We are getting the following error when trying to install SQL Server (2005 and 2008) software on a Windows Server 2008 R2 Enterprise machine:

"The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer in not correctly installed. Contact you support personnel for assistance."

We had installed SQL Server 2005 previously, but are now trying to install other components from the SQL Server installation materials.  We get the same error with the SQL Server 2005 and 2008 installers.

In our reasearch we've found references to corrupt or missing files and incorrect registry entries, and from the advice in those posts we have:

- Reregistered msi.dll
- Reregistered msiexec.exe
- Checked that the image path registry setting is correct
- Compared MD5 values for msi.dll and misexec.exe to those from a functioning server.
- imported registry settings from; Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msisrver, from a properly functioning server


but have not been able to correct the issue.

We were

Client can't connect to WCF on deployment machine Windows 2003 Sp2 server .NET 3.5



I have a WCF service hosted in a Windows service application.  I have a Windows Form client that connects to it.  I am using net.tcp binding for two endpoints.   It all works fine in my environment, but when I deploy it on my cutomer's machine the client does not get a response from the service.

I ran netstat -na and I can see the endpoints listening.  I can even see the connection ESTABLISHED when my client runs the first method.  But my client times out and receives a "Could not communicate with XXX service.  This request operation sent to net.tcp..... did not receive a reply within the configured timeout (00.01.00) The time alloted... etc"

I tried removing all security from the configuration file, but that did not make a difference.

I reinstalled .NET Framework 3.5

I added     System.Net.ServicePointManager.DefaultConnectionLimit = 200 as suggested in another post.

I am creating a trace for the client and the server.  The server does not log any activity of a connection.  The client is catching a communication exception.

Any insight would be greatly appreciated.  What else can I try to see why the client is not able to chake hands with the server on this particular machine?

Many thanks,



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,


Using windows authentication to access SQL when using ASP.NET 4.0 via COM+


I am using SQL Server 2008 under windows authentication, front end is ASP.NET which uses COM+ to access database.

COM+ components are configured to run as domain user.

When looking through the logs (SQL Profiler), I can see the login name as the configured identity instead of windows indentity.

I have got Website running under "Intergrated Windows Authentication" and database is running locally on webserver.

Web configure contains entry for <identity impersonate="true"/>.

My connection string is

connectionString="data source=db01\test01;initial catalog=test; integrated security=SSPI;persist security info=False; Trusted_Connection=Yes"

Any ideas?




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