Unable to connect SQL Server 2008 .Net

Question

i m unable to connect to database engine with win authentication

i m using sql server 2008

i m able to connect to analysis and integration services, and i m getting the foll err:

"Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The module was expected to contain an assembly manifest. (mscorlib)."

 I tried to apply the latest SQL service pack,but issue isn't resolved

Answer 1

Hi LeeTrj,

>> Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The module was expected to contain an assembly manifest. (mscorlib).

Regarding to the error that  can't find the assembly which is one of the basic .NET assemblies.

Some clarification with you, have you installed .net framework 3.5 sp1? If you installed, could you try a re-install/repair/uninstall-reinstall of.NET Framework 3.5 SP1 and try again to see if that helps.

You could download .net framework verification tool in order to automatically perform a set of steps to verify the installation state of one or more versions of the .NET Framework on a computer.

Based on my research, someone download the latest SP for SQL Server 2008 which fixed this error message. Could you verify you applied the Cumulative update package 3 for SQL Server 2008 Service Pack 3? If not you can get from here.

---

Regards, Amber zhang

Answer 2

Check out these resources:

#1) - Make sure SQL Server service is running:

http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

#2) - Check ports, firewalls, etc.

http://blog.sqlauthority.com/2008/08/09/sql-server-fix-error-1326-cannot-connect-to-database-server-error-40-could-not-open-a-connection-to-sql-server/

---

Ryan Shuell

Answer 3

plz refer the below given link, it may help you out.

http://amargalla.com/Blog/sql-server/168-unable-to-connect-to-sql-server-2008