-2147467259 from Database

[Ranjeet_Singh]

I am using SQL server(x86), XP SP3, LV2011 and its 32bit also using UDL file to connect to database.

when manually configuring the UDL file then I am able to access database also test connection succedded. When I use the UDL file in my application to connect to database then it generates the error 

-2147467259 

any suggestion?

[mikeporter]

What did the message that went with the error code say? Also, did you try Googling the error code (in Hex)?

Mike...

[Ranjeet_Singh]

Yes I tried googling it. Its says it might possible because of architecture issue(64 or 32 bit). But my PC and all application is of 32 bit. 

I have seen this error first time in which I am able to confirugre te UDL file and not able to access my database. 

In same PC I am able to access database using UDL but not from my application. Method of calling is correctt

I am attaching my UDL as well as my error code

[thoult]

There are a number of errors that return that error code. The text is more revealing. Are you trying to use Windows integrated security (SSPI) in the UDL?

[Ranjeet_Singh]

No I am using SQL mode

[Ranjeet_Singh · Accepted solution]

This problem is solved.

Creating UDL file again in same PC in which application is running, solved the problem.

[mikeporter]

Ah. So the UDL wasn't correct. Could you post the UDL that worked for you?

Mike...

[thoult]

I'd wager it was either a hardcoded user/pass or poorly implemented SSPI, judging from the error message.

[mikeporter]

The thing people don't appreciate is that a UDL is just a text file and so can't get "corrupted" like a binary file can.

Because it's a text file uou can open a UDL with Notepad and see the connnection string that is was defined. This could be a case of something not being setup right in the file, or perhaps permissions on the file itself were configured incorrectly.

Mike..