471,306 Members | 839 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,306 software developers and data experts.

MSSQL 2000 logon failure after .NET2 Framework installation

I Hope to see any opinions on this problem:

After installing Net framework 2 on one of our Win2003 Web server I have
experiencing trouble accessing MS SQL 2000 database.
Configuration is:
ASP.NET application is running on WEB server with application pool security
account set to “Network Service”.
This application accessing MS SQL 2000 server databases located on another
Access permitions on databases set for “webserver$“computer account.

There are two MS SQL server instances on one computer. ASP.NET application
accessing database in one SQL (A) instance and database in another SQL (B)
instance (naming instance).
On SQL(A) instance there is “Linked Server” configured and pointing to SQL
(B) instance.

There are number of SQL views on SQL (A) instance having
SQL(A)instance.database… “
in it. So we able to request linked data from two server instances in one
SQL view.

Everything works fine on .NET 1.1.
After installing “.NET 2 framework” everything was working for some time
but after about a day I started receive “Logon failure for webserver$ ” on
I am still able to request data from both databases but not from these
linked views.

I guess this begun after some “optimizations of .NET 2” I have seen in event

After uninstalling .NET2 framework off the server and reinstalling ASP.NET
everything starts working again.

Excuse my English please.

Thank you for help in advance.
Nov 20 '05 #1
0 1094

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Marty Cruise | last post: by
reply views Thread by robpimentel | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.