When i give PortalUser a sysadmin server role, it works. But i don't want to give PortalUser a sysadmin role. Any suggestions? Is sysadmin role required to access a remote server using Sql server authentication?
I have installed a SQL Server 2005 Standard Edition instance with SSIS on Window Server 2003 x64. From my PC, I am able to connect to the Integration Services on the server using Windows Authentication but not with a local SQL login - and the option to change authentication methods is greyed out.
Is it possible to remotely connect to SSIS using a SQL login rather than a Windows login? If so, any ideas or references for configuring it as such?
Hi all,For testing purposes I created a local database using SQL Server 2000. I want to connect to this database using following code:mySqlConnection = New SqlConnection("server=(local)SQLExpress;Integrated Security=SSPI;database=TestDbInge;UID=IVANSARK;PWD=test") mySqlCommand = New SqlCommand("SELECT Voornaam FROM Personen", mySqlConnection) mySqlConnection.Open() I'm getting the message below: System.Data.SqlClient.SqlException: Cannot open database "TestDbInge" requested by the login. The login failed. Login failed for user 'IVANSARKASPNET'. It's the same when I don't add the userid and password part to the connectionstring. What am I doing wrong?? And where does "IVANSARKASPNET" come from? Shouldn't I be anonymous? Please help.Regards, Inge
I have been using SQL Server 2012 developer edition for quite a while without problems. But now when I try to connect I get this error:
Cannot open user default database. Login failed. Login failed for user 'D8700Ken'. (Microsoft SQL Server, Error: 4064)
I suspect that I caused this problem myself but I don't know how to recover from it. Here is what I did:
1: Used SSDT in Visual Studio to change the set default database from 'master' to 'DTNSQL' (My first SSDT experiment!) 2: Used SQLSMS to rename the 'DTNSQL' database to 'DTNSQL01'. 3: Logged out of SQL Server - then tried to log back in.
I have read that the solution to this problem is to "login using another Login."
I don't seem to have "another Login". How to find an existing Login or create a new Login.
Hi everyone, I am trying to open a connection to my SQL Server via ASP.NET(VB.NET), but I get the following error message:Server Error in '/test' Application. --------------------------------------------------------------------------------
Login failed for user 'sa'. 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 'sa'.
Source Error:
Line 92: 'Put user code to initialize the page here Line 93: Line 94: SqlConnection1.Open() Line 95: If SqlConnection1.State = ConnectionState.Open Then Line 96: Label4.Text = "SQL Connection is open"
[SqlException: Login failed for user 'sa'.] System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) System.Data.SqlClient.SqlConnection.Open() test.WebForm1.Page_Load(Object sender, EventArgs e) in c:inetpubwwwroot estWebForm1.aspx.vb:94 System.Web.UI.Control.OnLoad(EventArgs e) System.Web.UI.Control.LoadRecursive() System.Web.UI.Page.ProcessRequestMain()
-------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032
The account itself works fine, I am able to log in to the server successfully, for example there are no problems when I use the same user name and password for the Query Analyzer. What could be the cause of the error mentioned above?
I am trying to create a CLR project in my Visual Studio 2010 with SQL Server 2012. I can build my empty project succesfully, but if I try to deploy it, I get such an error...Beginning deployment of assembly SimpleCLRIntegrationNew.dll to server xxxxxxxxx : di_test
C:Program Files (x86)MSBuildMicrosoftVisualStudiov10.0TeamDataMicrosoft.Data.Schema.SqlClr.targets(96,5): error : Could not connect to server "xxxxxxxxxx: di_test": Login failed for user 'di_test'..
I originally posted this issue on the SSIS forum and it was suggested I cross post here. I'm trying to connect to the MSDB database on a remote SSIS server using the integration services connection listed in the drop down box on SQL Server 2005 Management Studio. Every connection attempt ends with an 'Access Is Denied' error message. I have full db_dtsadmin rights on the remote server. We followed the MSDN whitepaper on connecting to a remote SSIS server (the section on eliminating the Access Is Denied error - configuring rights for remote users). Nothing works, I always get the generic access denied error message. Are there other permissions that need to be assigned in conjunction with db_dtsadmin to get this to work? I wonder if there is something simple we're overlooking.
I€™m using a Script Component in SSIS to call a Web Service. The web service is wrapped, using the wsdl tool. The package works, on my local enviroment. Script component calls the web service and returns the data. I€™ll move the web service to another server, web service as Anonymous access is enable. Deployed the Package on a SQL server. But, when excuting the package I get the below error. I can view and invoke the web method and see data even. SSIS is running under a NT AUTHORITYNetworkService account. I know that the problem is permission, but how would I resolve the issue.
Error: OnInformation,SERVER,DOMAINSqlAdmin,MISPackage,{190832FB-4FF1-4ECD-BF53-4A49864089B4},{D7BF27CD-BDF1-418A-ABFE-BA0A24B921FB},3/14/2007 10:59:11 AM,3/14/2007 10:59:11 AM,0,0x,System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetRequestStream() at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at ScriptComponent_6386cd9eab6a49e7b1a90f69dcc24beb.Service.GetMISAccounts() at ScriptComponent_6386cd9eab6a49e7b1a90f69dcc24beb.ScriptMain.CreateNewOutputRows()
The following error occurred when trying to connect to 2012/2014 SSIS Server using SSMS remotely. Local connection works fine.Using the info from below link does not resolve the problem. Â Permissions are granted through DCOM. If this cannot be resolved, packages will have to stored on filesystem instead. URL....Connecting to the Integration Services service on the computer "" failed with the following error: "Class not registered".
This error can occur when you try to connect to a SQL Server 2005 Integration Services service from the current version of the SQL Server tools. Instead, add folders to the service configuration file to let the local Integration Services service manage packages on the SQL Server 2005 instance.
I moved my web and DB to a new server. I am trying to use a private network between my servers to connect to my DB.
I backed up my DB on the old server, copied it to my new server, then restored it.
I then went into Security > Login and set up a User Name & Password and set the db as the default db, made that user the owner, etc.
I went to my web server, changed my connection string to this:
Code:
sConString = "Driver={SQL Server};" & _ "Server=tcp:MYSERVERNAME;" & _ <!-- The server name --> "Address=xxx.xxx.xxx.xxx,1433;" & _ <!-- The Private IP Address between servers --> "Network=DBMSSOCN;" & _ <!-- Telling it to use TCP --> "Database=DBNAME;" & _ <!-- The name of the DB I am connecting to --> "Uid=UNAME;" & _ <!-- The user name to login with --> "Pwd=UPWD;" <!-- The Users Password -->
(Obviously I changed the critical info above, but this is the format I used)
I cannot seem to login to the DB. I get the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'UNAME'.
/(file path), line 5
I have read the following article and it appears I have everything right. http://support.microsoft.com/?scid=kb;en-us;827422&spid=2852&sid=332
Somehow I cannot seem to connect/login to get the proper access. Can anyone help? Anyone see anything I am doing wrong? Anyone have any suggestions?
Thanks for the help in advance. I am trying to get this done tonight so it is running in time for the morning.
Help! Cannot connect to Database, login failed for user... I have been looking for a fix for this for some time, however I have yet to find one. I am running msde-2000 and I have a programm that I wrote with VB.Net 2003 that works fine when I am in Debug Mode, however when I deploy the application, and try to connect to the MSDE SQL-Server I get an error that states, "Cannont Connect to database TCON1, Login failed for user Amanda,
Is that possible to execute SSIS packages from a remote SQL Server 2005 in another domain at local computer (Windows XP)?
Can I use SQL authentication to connect to the remote SSIS? My problem is, the user who execute the SSIS is not allow to access to SQL server directly. Is that possible to code everything in a batch file instead?
I tried to use web services to execute the remote SSIS but it always return "authentication error"?
I have a question regarding ASP.NET 2.0 reading available packages (calling "GetDtsServerPackageInfos" on the "Application"-Object which returns "Microsoft.SqlServer.Dts.Runtime.PackageInfos") from a remote SSIS server (not running them). It seems to me that I am experiencing either a security/delegation issue or that I am trying to do something that is not possible...
The setup is the following.
I have two machines, A and B. A runs IIS 6/ASP.NET 2.0 and B runs SQL Server and SSIS. They belong to the same domain. IIS runs the application pool with the webapplication in question under the "Network Service" account and A is trusted for delegation to B. At the moment its trusted when using Kerberos and for MSSQLSrvc and rpcss; but I tried "all" and many more as well.
I configured IE to use Windows Authentication and set the URL to belog to the Intranet (to enable kerberos authentication).
My ASP.NET webapplication now tries to read (in the sense explained above) the available packages on the SSIS machine (B). The packages are stored on the filesystem, not in mdsb. But I feel that this does not matter, since ASP.NET is accessing them through "the SSIS service" which can access packages in msdb or/and on the filesystem?
What happens now is that
a) everything works, when I fire up IE on A and access the webapplication. The user I have on A is a local admin. b) I get "E_ACCESSDENIED" when I start IE as regular User on A c) I get "E_ACCESSDENIED" when I access the webapplication from any other machine than A (IE6 or IE7)
My main question is: is it possible to do what I want to do? The other question is, why does everything work when I access the webapplication from A, but not from any other machine? The second thing makes me think it could be a delegation issue (double hop and SSIS don't seem to go togethe too well). But still, I could not find any resource telling me that this is impossible And frankly, I do not fully understand delegation and/or Kerberos.
I would greatly appreciate if anybody had a pointer or something for me. Regards scherand
Btw: Thanks to Caddre for his (her?) first help and pointing me to this forum.
Hi, I have an ASP.Net web application running in groupnamewebservername. I am trying to connect it to the remote database server groupnamedatabaseservername using the ASPNET user id. The remote database is SQL Server 2005 and the web server has IIS 6.0 installed. My web.config connection entry has username as "groupnamewebservernameaspnet" and I have a database user in remote database server under the login name groupnamewebservername$. When I try to connect, I keep getting the following error: System.Data.SqlClient.SqlException: Login failed for user 'groupnamewebservernameaspnet'.
Could you please let me know what I am doing wrong here? Thanks. Regards, Gayathri.
I followed the steps outlined in a blog I found to setup SS2005 express for remote connections. Everything appeared to go smooth until I actually tried to logon ;)
I have Sql Server 2005 Express installed on my WinXP PRO machine at home (no domain). I have opened the ports on the firewall, etc.
When I try and login from the SQLCMD command line tool I get a Login Failed error. Here is the connection string that I'm trying to use: SQLCMD -S **.***.**.*SQLEXPRESS -U Steve -P MyPassword
The error: Login failed for user 'Steve'.
When I use Management Studio Express on the same machine running Sql Server, it shows the User name: NEVERSTILLSteve
'NEVERSTILL' is the name of my computer.
If I try and use that same username with a remote connection I get the same error.
I have googled for the error and msg code, but nothing fitting my situation is coming up.
Hello everyone,When I try to connect to database I get this error message: Login failed for user 'databaseadmin'.My connection code is:Dim MyConnection As New SqlConnection( _ "server=(local); database=news; UID=databaseadmin; PWD=111111;")I've tried "server=localhost:3066", and "server=." and many many other ways, but it's still not working! I don't know what other things should I try now... I asked the support people of my web host, and their answer is:"Mysql database usename and password is corect one. It seems that there is problem with the script code."Please would anybody help me with this? Thank you very much!
I created a SSIS package using VS2005 with the "ProtectionLevel" set to "DontSaveSensitive" . I executed the package and it completed without an error. I then built the package and deployed it to the SSIS inside the folder "MSDB". I run the pakage in SSIS and it worked perfectly. Then I created a job in SQL Server Agent and have it run in a per-set schedule. It failed to run withthe following error:
Message Executed as user: SRVSOUDB01SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:11:02 PM Error: 2008-05-12 22:11:03.17 Code: 0xC001401E Source: STDM Connection manager "Target_AS_STDM.abf" Description: The file name "\Svmppodb01OLAP DataSql DataBackUpAS_STDM.abf" specified in the connection was not valid. End Error Error: 2008-05-12 22:11:03.17 Code: 0xC001401D Source: STDM Description: Connection "Target_AS_STDM.abf" failed validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:11:02 PM Finished: 10:11:03 PM Elapsed: 0.422 seconds. The package execution failed. The step failed.
The error mentioned the step in SSIS Package that requires to copy the backup of the OLAP database file "AS_STDM.abf" from the Source Server location (local processing server SRVSPOYDB01) to the Targer Server location (remote production server SVMPPODB01) "Svmppodb01OLAP DataSql DataBackUpAS_STDM.abf". This step worked in the SSIS(SRVSOUDB01) when executing there. Why it is not working in Sql Server Agent(SRVSOUDB01). It also works in VS 2005.
I installed SQL 2005 Developer addition on my Vista laptop. When I open Management Studio to connect to the local instance of the DB, I get the error below. Why can't I access? Is there something with Vista that is prohibiting?
Thanks
TITLE: Microsoft SQL Server Management Studio ------------------------------
Login failed for user 'xxxx'. (Microsoft SQL Server, Error: 18456)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
hi, so i have a new box and I'm trying to get my websites and SQL Server 2005 Standard Edition working on it, but the pages give me the following error when I try to load them: "Cannot Open Database "XXXX" requested by login. The login failed. Login failed for user 'xxx'" Everything seems exactly the same settings and user-wise from my old box to my new one, but nevertheless everything I've tried gives me the same error. I've tried creating new users in SQL Server and giving them appropriate permissions to my database. I've even tried just using the built in 'sa' account. Nothing seems to change the error, except when I give it the incorrect password then it just says 'login failed' This leads me to believe that i'm successfully logging into the SQL Server, but it doesn't want to give me access to the database I'm requesting access too. But "apparently" the account i'm using should have access to the database. If nothing else the 'sa' account should, but that didn't work either. I'm stumped. Any ideas?
I have written a VB component to execute a SSIS package stored in SQL server.
I am using the Microsoft.sqlserver.dts.dtsclient, dtsconnection/dtscommand
and executereader and everything works perfect on the local machine. This is descibed in a msdn site .
But my customer have a remote SQL server and want no extra BI clients/SQL server clients etc on the client machine, only an ordinary windows client and network connection to the SQL server.
My question is: Can you still use dtsclient or do you have to do in some other way?
Sql server agent is running under a domain account that is a member of administrators and domain users amongst others, and the package is executed as the service account. Connecting to servers on the same domain works and when I run it from the msdb package store in ssis (ssis runs under the network service account ...) it will connect to the pop server as well. Permissions, fiddly proxies .. the answer's out there somewhere
SSIS package "Clear.dtsx" starting.Error: 0xC0202009 at Clear, Connection manager "10.11.60.30.msdb.sa": An OLE DB error has occurred. Error code: 0x80040E4D.An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'sa'.".Error: 0xC00220E4 at Execute Package Task: Error 0xC0202009 while preparing to load the package. An OLE DB error has occurred. Error code: 0x%1!8.8X!..Task failed: Execute Package TaskWarning: 0x80019002 at Clear: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.SSIS package "Clear.dtsx" finished: Failure.
trying to connect to sql server 2005 over the internet. (its a third paty hosting company i'm using)
so i have to connect via tcp/ip using sql server authentication.
my laptop is running vista.
the version of sql server 2005 on my laptopis developer edition with service pack 2.
it worked fine from windows xp and the connection details are valid as it runa fine from .net on the hosting website.
i have added sql serer managemnt studio to the exceptions list in the firewall.
ihave made sure tcpip is enabled in the sql server connection management console.
i have also enabled it in the cliconfg tool
firewall on/off seems to make no difference.
its almost enough to make you turn to oracle and thats saying something considering how long i've been in the microsoft camp...
the error returned is: Login failed for user 'SQL2005_152092_garethbowen'. (.Net SqlClient Data Provider)
------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
------------------------------ Server Name: 'xxxx',1433 Error Number: 18456 Severity: 14 State: 1 Line Number: 65536
i connect to remote Integration Service. i configure server for remote connection( on component services and DCOM config , ... ) .and now i can connect to Integration Service remotely and correctly.
but when i expand Stored Package and then click to expand MSDB this error will hapen:
login failed for user ... .(microsoft sql native client )
I have a pretty simple SSIS package that fast loads a 100 million record table into a SQL Server 2008 table on a daily basis. This normally runs fine and completes in about 1 hour. As this is perhaps one of our largest running SSIS packages, about once every 2-3 weeks this SSIS will fail/drop connection. Once it fails, the large number of records will start rolling back. This rollback process can take 1+ hours so I cannot even restart the failed SSIS package immediately. This is a problem.
I am looking for a solution or option so I do not have to wait on that rollback to restart this particular, long running SSIS package. Is there an option/setting to leave the partial data set committed and not rollback? Then I could just restart the SSIS package immediately or set it the SSIS to auto-restart 1 time on failure. The first step in the SSIS does a truncate of the destination table.
We are trying to take advantage of the new Security Context for SSIS but users are unable to connect remotely to the SSIS Service unless they have been added to the Administrators Users Group on the server. I have tried adding them to Guests, Power Users, Remote Desktop Users, Users and SQLServer2005DTSUser$machine but the user is unable to connect.
The message received when the user is unable to connect is:
Cannot connect to 192.x.x.x Additional Information -> Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) -> Connect to SSIS Service on machine "192.x.x.x" failed: Access is denied
What is the list of permissions and privileges that a user that does not belong to the server's Administrator group and have sysadmin server role, must have to allow them to create and run a package through SSIS.
Have just tried my sql server 2005 connected asp classic website on II7 for the first time and have gotten some errors. First off I have unchecked show friendly errors in IE and have enabled ASP to send error messages to the browser.
My error I get is when I execute a basic .asp page:
Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "mydatabasename" requested by the login. The login failed. /index.asp, line 10 which is dbConnect.Open cstring
from this peice of code:
sub dbOpen() set dbConnect = Server.CreateObject("ADODB.Connection") cstring = "DSN=mysqldsn; Trusted Connection=yes" dbConnect.Open cstring end sub
I have gone into ODBC and have setup both a user dsn and file dsn that equals mysqldsn and points to my database (I know you only need to set up one DSN but I'm not sure which)
I also notice under mywebsite home panel there is a connection string option. Do I do anything with that?
i'm using the Enterpirse library logger to write logs into a database. When choosing connection string i choose the database i want in the "connection properties" dialog box and push 'Test connection' button. everything goes well.
then i open the SQL Server Management studio express and connect to the databse to check some things, from that point on , when i push the 'Test Connection' button in the Enterprise library i get the error:
"cannot open user default database. Login failed. login failed for user My'server/MyuserName'"
even when i close the sql server manager , it is still stuck - the connection test doesn't work anymore.... it only work when i restart the computer.
I notice when I copy an SSIS package 'A' to a new package 'B', the new package 'B' will generate a "login failed for user" message in the data flow components. To copy I "save copy of Package 'A' as."
Some config info:
Package ProtectionLevel = EncryptSensitiveWithPassword Connections are Data Sources Connection strings with password are stored using PackageConfigurations to an SQLServer table. I've verified Package 'A' is in fact using the config table (e.g. it is not using a password or user stored in the package) Data connectios are all SQLServer Native OLE DB Client The account is an SQLServer account (not integrated security)
The original Package 'A' works flawlessly and I get success when I test the connections in Package 'B'.
But executing package 'B' I get: The error message I get is: [Connection manager "MyConnection"] Error: An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'dwuser'.".
Does anyone know why this would occur and/or how to work around it? I saw another thread where a potential workaround is to create a new data flow task and copy all the data flow components to that task. That won't work well for us because the data flow is moderately complex and when you copy and paste it, SSIS completely re-orders the layout.
This is a typical data warehouse ETL setup where there is a master package that executes child packages (e.g. 'A', and 'B' mentioned above) that each perform the ETL for a specific dimension or fact table.
We have a SQL 2000 Active/Passive cluster running on Windows 2000. On one node, everything logs in fine (second node is powered off). I can use local authentication fine in OSQL (-E) and even see my connection in SQLEM current activity as [DomainUser] for the NT account which I am logged in as. Then I bring the second node online and initiate a failover. SQL Server starts but Cluster Admin cannot connect and starts throwing this Anonymous Logon error. I open a command prompt and try the same OSQL (-E) local login and sure enough it is also giving the Anonymous Logon connection user. I do not understand why the failover to a second node is causing the Trusted Connection Local authentication to switch to Anonymous instead of the [DomainUser] which I am using. Any help is appreciated. John.
I have a script component. What it does, it queries the a table using a connectionstring assigned to it in the Connection Managers Editor (which is an ado.net adapter). this works fine when i'm using a windows login in the ado.net connection manager. But when i changed my connection to use SQL server login, I encounter this error:
OnError,,,Add new records to Dim_T_Status (Case),,,10/14/2007 5:54:47 PM,10/14/2007 5:54:47 PM,-1073450910,0x,System.Data.SqlClient.SqlException: Login failed for user 'CS_REPORT'. at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e) at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper90 wrapper, Int32 inputID, IDTSBuffer90 pDTSBuffer, IntPtr bufferWirePacket) OnError,,,LOAD AND UPDATE OCEAN Dimension Tables,,,10/14/2007 5:54:47 PM,10/14/2007 5:54:47 PM,-1073450910,0x,System.Data.SqlClient.SqlException: Login failed for user 'CS_REPORT'. at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e) at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper90 wrapper, Int32 inputID, IDTSBuffer90 pDTSBuffer, IntPtr bufferWirePacket) OnError,,,LoadOCEANDimensions,,,10/14/2007 5:54:47 PM,10/14/2007 5:54:47 PM,-1073450910,0x,System.Data.SqlClient.SqlException: Login failed for user 'CS_REPORT'. at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e) at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper90 wrapper, Int32 inputID, IDTSBuffer90 pDTSBuffer, IntPtr bufferWirePacket)
All the logins with sysadmin role are locked out in one of the SQL server. Also in that instance Logon trigger is implemented which allows only certain users with Windows Authentication to logon.
This server is converted into single user mode by using command prompt. Now we are attempting to connect to SQLServer using command sqlcmd -S FTCPU3239 (since we do not have any other login) and create a new login with sysadmin role but are refused due to logon trigger. it says Login failed for login 'DomainNameUserName' due to trigger execution.
