Comments on: SQL 2005 error code = 80004003: Invalid Pointer http://itknowledgeexchange.techtarget.com/itanswers/sql-2005-error-code-80004003-invalid-pointer/ Mon, 20 May 2013 18:21:12 +0000 hourly 1 By: pressler2904 http://itknowledgeexchange.techtarget.com/itanswers/sql-2005-error-code-80004003-invalid-pointer/#comment-52934 pressler2904 Fri, 25 Apr 2008 13:58:45 +0000 #comment-52934 Mrdenny – (and all interested parties):

Thanks for the reply – the issue has been resolved…

To answer your questions, the connection was fine when queries were executed via the VM Ware console on the server itself, hence my statement that the database appeared to have been attached successfully.

The resolution of the issues was so obvious (even to a non-DBA like me) that I probably should be assaulted with a clue-stick or two…

When setting up the sql.ini file, for the “database name”, I inserted the actual name of the .mdf file. What I should have done, and what fixed the problem, was enter the name of the .mdf file <alias> as created during initial database configuration. The client side piece of this commercial product leaves the translation between actual file name and alias to the SQL Server.

What clued me in to the issue was the creation and configuration of a .udl file: after entering the server instance name, the database alias was made available in the “Select the database” dropdown area of the “Connection” tab. When comparing the SQL.ini file, I noticed the discrepancy, adjusted the .ini file and **poof** connection established.

As I mentioned, the issue has been resolved and connectivity confirmed as of about 9:00AM this morning EDT

Thanks for the assistance.

pressler2904 (AKA poppaman2)

]]>