Moving from Win2000 to XP - ODBC problem

[Guest]

I have had an intranet site hosted on a PC running Windows2000 for *ages* that connects to a SQL server database. The site uses ASP / VBScript. I came to move it onto a XP (sp2) machine and static pages work fine but anything that accesses the backend DB gives me this error message;
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
/workload/dept_colours.asp, line 5

All the files are copied verbatim (including the connection file below)
Dim MM_connPathData_STRING
MM_connPathData_STRING = "dsn=pathnet_data;"

Both PCs are logged into Windows with the same user so there shouldn't be a differing permissions. The DSN for the database (using Windows NT authentication) is set up identically on both machines so I'm at a loss as to why one works and one doesn't )-:

Funnily enough, when setting up the ODBC on the new machine the 'test data source' button claims that it can connect to the db OK!!

Is there some difference between the 2 OSs that means that my 'old' set up no longer works? If so, what should my 'connection' file look like?

[Newsgroup_User]

S J Harris wrote:

> I have had an intranet site hosted on a PC running Windows2000 for
> ages that connects to a SQL server database. The site uses ASP /
> VBScript. I came to move it onto a XP (sp2) machine and static pages
> work fine but anything that accesses the backend DB gives me this
> error message; Error Type:
> Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> '(null)'. Reason: Not associated with a trusted SQL Server
> connection. /workload/dept_colours.asp, line 5

It is best to use connection strings when you can. On the OSBC, have
you tested it on the new machine?

>
> All the files are copied verbatim (including the connection file
> below) Dim MM_connPathData_STRING
> MM_connPathData_STRING = "dsn=pathnet_data;"
>

And this is the name on the new machine?

> Both PCs are logged into Windows with the same user so there
> shouldn't be a differing permissions. The DSN for the database (using
> Windows NT authentication) is set up identically on both machines so
> I'm at a loss as to why one works and one doesn't )-:
>
> Funnily enough, when setting up the ODBC on the new machine the
> 'test data source' button claims that it can connect to the db OK!!
>
Hmmm? Again look at using connection string instead. I find them much
easier to transport and troubleshoot when moving between machines.


> Is there some difference between the 2 OSs that means that my 'old'
> set up no longer works? If so, what should my 'connection' file look
> like?

None I know of.


--