I am trying to connect to a virtual directory where there is an application
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection (Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.Get PooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUs erList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Ob ject sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPo stBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEve ntHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCol lection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
LizW
The ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.
Showing posts with label virtual. Show all posts
Showing posts with label virtual. Show all posts
Wednesday, March 7, 2012
cannot connect/login error message
I am trying to connect to a virtual directory where there is an application
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application.
----
--
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information abou
t
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnec
tionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUserList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Object sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePo
stBackEvent(String eventArgument) +57
System.Web.UI.Page. RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
LizWThe ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application.
----
--
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information abou
t
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnec
tionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUserList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Object sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePo
stBackEvent(String eventArgument) +57
System.Web.UI.Page. RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
LizWThe ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.
cannot connect/login error message
I am trying to connect to a virtual directory where there is an application
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application
----
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUserList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Object sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
--
LizWThe ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.
that was developed in .asp.net - it is linked to a sql server database. I am
using IIS, Server 2003 and SQL Server 2000 - same server - Any ideas where
this may be coming from? I posted this message under connect and security
sections. Thanks.
Server Error in '/Admin' Application
----
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'NT AUTHORITY\NETWORK SERVICE'.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
ut.hfrp.asap.DAO.BaseDAO.getConnection() +83
[DAOException: Unable to create connection to database]
ut.hfrp.asap.DAO.BaseDAO.getConnection() +154
ut.hfrp.asap.DAO.UserDAO.GetList() +70
ut.hfrp.asap.BusObj.Settings.AirlineSettings.GetUserList() +30
ut.hfrp.asap.ManagerApp.Login.SubmitLogin_Click(Object sender, EventArgs
e) +51
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
--
LizWThe ASP service Account is running under Networkservice Account which
is not priviledged in the SQL Server database. Either you change the
authentication in your application to SQL Server authentication
(Checkout the connectionstrings on www.connectionstrings.com for that)
or you change the service account of ASP to a domain or local account
which has to be priviledged in SQL Server.
HTH, Jens Suessmeyer.
Tuesday, February 14, 2012
Cannot connect to Named Instance
I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
(Windows 2003). I have no problems connecting to the first virtual server by
name or IP address, but I can only connect to the named instance by using
the IP address and specifying a port (192.168.0.1, 1434).
I can connect to the named instance by IP or name from both cluster nodes,
the problem only arises with remote clients. The client machine I am testing
from is running Windows XP SP2, MDAC 2.8
Thanks in advance,
Curtis
Curtis O. Bouknight wrote:
> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).
> I can connect to the named instance by IP or name from both cluster nodes,
> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
>
1433 is the default sql port. The problem could be with the udp listener
which tells the client where the instance is running.
when you installed the named instance you created an alias on both nodes.
Did you remove these, and if so does the sql agent connect with lpc or is it
still using named pipes? If so clean the registry
HKLM\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSo cketNetLib\LastConnect
and restart sql agent and see it fail?
Are both sqlservices running as local admin?
Hans
|||Welcome to my world.
This issue has been ongoing for me with Microsoft for almost a year now.
They have bounced around from it being a SQL Problem, to a network problem,
back to a SQL Problem, now they are looking at an OS problem. If you call
support, be ready to take system dumps, netstats, captures, etc...
One thing you can do to "verify" that you have the problem is to take a
tasklist and a netstat -aon on each node, then match the PID's up. One will
not have a listener on UDP 1434, and the other will. We had the same
scenario for quite some time, then suddenly the other node started exhibiting
the same behavior. We now tell customers to just go directly to the TCP/IP
port for both nodes to solve any confusion down the way.
js
"Curtis O. Bouknight" wrote:
> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).
> I can connect to the named instance by IP or name from both cluster nodes,
> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
> Thanks in advance,
> Curtis
>
>
>
(Windows 2003). I have no problems connecting to the first virtual server by
name or IP address, but I can only connect to the named instance by using
the IP address and specifying a port (192.168.0.1, 1434).
I can connect to the named instance by IP or name from both cluster nodes,
the problem only arises with remote clients. The client machine I am testing
from is running Windows XP SP2, MDAC 2.8
Thanks in advance,
Curtis
Curtis O. Bouknight wrote:
> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).
> I can connect to the named instance by IP or name from both cluster nodes,
> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
>
1433 is the default sql port. The problem could be with the udp listener
which tells the client where the instance is running.
when you installed the named instance you created an alias on both nodes.
Did you remove these, and if so does the sql agent connect with lpc or is it
still using named pipes? If so clean the registry
HKLM\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSo cketNetLib\LastConnect
and restart sql agent and see it fail?
Are both sqlservices running as local admin?
Hans
|||Welcome to my world.
This issue has been ongoing for me with Microsoft for almost a year now.
They have bounced around from it being a SQL Problem, to a network problem,
back to a SQL Problem, now they are looking at an OS problem. If you call
support, be ready to take system dumps, netstats, captures, etc...
One thing you can do to "verify" that you have the problem is to take a
tasklist and a netstat -aon on each node, then match the PID's up. One will
not have a listener on UDP 1434, and the other will. We had the same
scenario for quite some time, then suddenly the other node started exhibiting
the same behavior. We now tell customers to just go directly to the TCP/IP
port for both nodes to solve any confusion down the way.
js
"Curtis O. Bouknight" wrote:
> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).
> I can connect to the named instance by IP or name from both cluster nodes,
> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
> Thanks in advance,
> Curtis
>
>
>
Sunday, February 12, 2012
Cannot connect to Express with Management Studio?
Hi,
I have installed an instance of SQL Server 2005 Developer Edition and another of SQL Server 2005 Express on my computer (Virtual PC, of course!).
Management studio will not let me create a new database in the Express instance. It says the express engine doesn't support full-text indexing. I am aware of this, and do not wish to use this feature. I just need Management Studio to manage my Express database. Is there a workaround for this?
Also, are SQL 2005 dbs "downgradable" to Express? I assume so, but I'd rather be sure of this.
Thanks!
I have installed an instance of SQL Server 2005 Developer Edition and another of SQL Server 2005 Express on my computer (Virtual PC, of course!).
Management studio will not let me create a new database in the Express instance. It says the express engine doesn't support full-text indexing. I am aware of this, and do not wish to use this feature. I just need Management Studio to manage my Express database. Is there a workaround for this?
Also, are SQL 2005 dbs "downgradable" to Express? I assume so, but I'd rather be sure of this.
Thanks!
Hi,
you can use SQL Express Management Studio.|||You mean XM? XM is a joke imho... I think Query Analyzer is a better alternative than XM.|||Hi,
You did ask for a smaller Version of SQL Server Management Studio and not for the best tool to do this job ;)|||I asked for a workaround for using Man Studio with Express, not for a smaller version of management studio.
Anyways... thanks :) The commands I cannot do with MS, I do them with query analyzer. Overall, it seems to work ok.
|||This was an issue to versions of SSMS prior to the June CTP. The June CTP should work fine.
Subscribe to:
Posts (Atom)