The event log is showing a ton of failed sa logins. The server is connected
to the net. I am assuming this is a dictionary attack to get the sa
password. I am trying to find out if this is an inside attempt or from the
outside. While the profiler will tell me which program or script is sending
it, how do I find out which ip address(s) from the net is doing this?
--
John Dalberg
SQL 7 profiler has an event in the Misc. category of Failed Login. It does not, or at least I cannot get it to, produce any output when a failed login occurs. Any hints?
I tried this because every week or so I get this in the error log:
Login failed for user 'Admin'.
It occurs several hundred times within a minute or so. It obviously has to be an automated process as you couldn't click a button or press a key 13 times a second.
The login does not exist as a SQL login so I can't tell which database it is trying to get at. Any suggestions gratefully received.
Simon
We're using a canned app that only uses SQL Server logins (it will NOT use Windows logins to access SQL Server)
SQL Server logins seem to lack even the most rudimentary security features such as expiring passwords and automatic disabling after a set number of failed logins. Bad. Bad Microsoft.
Has anyone figured out a way to graft this on after-the-fact?
I can do it in an awkward fashion by auditing failed logins and going back to read the error log, but this isn't real time by any stretch.
Hi,
I need to be able to get info about failed login attempts which need to be running all the time and logging info such as hostname , application name, host machine, etc. The best way I can see to do this is by crerating a trace. Then loading the info from the trace into a table for later use by using fn_trace_gettable. But this requires that the trace be stopped and the definition removed for the trace file to be populated.
Is there a way to be able to log this info constantly into a table without having to stop and then recreate another trace. Also it requires that the table created by the function is dropped.
Anyone any idears?
Thanks
HI guys,
I just restored a database on a new server with a backup(complete backup stored in backup device) from another database on another server using the "with move" option. In fact here was my process:
Alter database ngauge SET SINGLE_USER WITH ROLLBACK IMMEDIATE
restore database ngauge
from disk = 'C:Program FilesMicrosoft SQL ServerMSSQLBACKUPgauge1.BAK'
with move 'NGAUGE' to 'C:Program FilesMicrosoft SQL ServerMSSQLDatagauge_Data.MDF',
move 'NGAUGE_Log' to 'C:Program FilesMicrosoft SQL ServerMSSQLDatagauge_Log.LDF'
Alter database ngauge SET READ_WRITE
it worked.
But it did not move the 98 or so users/logins...from the source database
what is going on??? what am I doing wrong??!!
Please help!
'W
Hi,
We are running MSSQL 2000 on a reasonably powerful dedicated Win2k system Dual 2.4 Xeon Procs, 2 GB of RAM, Ultra 160 SCSI disks.. blah blah blah.
Our primary use this database server is for our Coldfusion Application servers. We host about 50 or so databases.
Of late, we have been experiencing random failed logins for certain databases. These failed logins are logged to the event log on the server. They randomly; queries executed against a datasource configured on our application servers trying to get data from the database fail with a login failure when other times they will succeed. I am confused about this issue. Could an issue where the SQL Server is overloaded cause a login failure for a database?
Errol Neal
I just applied instcat.sql to my SQL Srvr 2k sp4. At first it broke my replication with some cursor errors. Applying the latest instcat.sql fixed the problem, however one of the distribution agents would not start (i'm not sure if instcat had anything to do with it) giving me a "Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. The process could not connect to distributor 'DistributorName'. The step failed." error.
Any suggestions would be greatly appreciated!
Thanks!
I was checking the logs because of some failing backups and found literally hundreds of enties for failed logins for user sa. This is does not seem to be related to the failed backups, because even after fixing the problem (disk space), the entries continue to pile up.
Needless to say, the information provided in the log is a bit sparse: date and time, source (Login), message (Login failed for user 'sa'.). If that is actually enough to go on, then there must be some way of cross-referencing this information with that found somewhere else. Is there a 'somewhere else' or are there other things I need to do in order to track this down?
I don't suspect any malicious intent, but I'm not ruling it out. My main concern at this point is twofold: to gain a better understanding of system management; to identify and correct the failed login.
Any recommendations, whether tools, documentation, or otherwise are very much appreciated.
Ron.
ok, first, I know... I forgot to run a backup of the master database, and I forgot to run a script to caputure logins. Not that that is out of the way... I need to recreate the logins under the Securities tab below the databases. All the company databases have the user names and passwords assigned to them, but they are not able to login, because they are not able to authenticate to the SQL server first.
Is there a script that someone has that will copy the company database security info for the users and recreate them in the SQL security tab?
I know that I can rebuild them manually, but I need to delete them first in the application software, then delete them from the databases, and then recreate them in the application software... and as simple as that sounds... it is a slow moving process.
Any assistance would be greatly appreciated.
Thanks,
John
Hello,
I would move a Database to another server. I try to use DTS but I have problems with this process because DB have big tables, I think. I try to use DETACH and ATTACH procedures but logins doesn't export. And more, in new server there are already logins from another DBs.
What's the best way to solve this problem?
Please, help
Thanks
I am a systems analyst and work with an app that runs against 2 SQL Server DBs. Though I have some familiarity with SQL Server and SQL, I am not a DBA.
The app executable is tied to a Windows service.
When we install the app, we run a process that builds 2 dbs to include:
Tables, indexes, stored procedures, views and user accounts.
SQL Server is set up for mixed mode authentication.
Normally, the dbs run off the local db user accounts which are tied to local logins with the same names.
We have a client that wants to remove our standard logins so that they can run on only a Windows login.
I know I should be able to tie the db users to a Windows login.
And I can do the same for the service.
But I am at a loss as to how to get this done.
How do you associate db users with a Windows login?
When I have tried sp_change_users_login I get an error that the Windows login does not exist. (Though I have added the Windows account to the DB.)
Hope this all makes sense.
I get the following error when I try to run my scheduled job.
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Any ideas Thanks in advance
Reddy
Dear all,
I've built SSIS package and made a job to execute it automatically but it always returns an error. The job returns OK but when we looked at the Log File viewer, it conatins this error log :
Key not valid for use in specified state
Failed to decrypt protected XML node "DTS Password" with error
What's wrong with the package ?
Thanks in advance.
Best regards,
Hery
Full message:
Connection handshake failed. An OS call failed: (8009030c) 0x8009030c(The logon attempt failed). State 66
Under these conditions, setting trustworthy on on the sending and receiving databases will solve this issue
1) Communicating between multiple instances
2) Using Kerberos security (NT Authentication, i.e. not certificates)
I wrote an application using Visual Studio 2005 beta 2 which uses a SQL Express .mdf file, included in the project, for the database. After installing Visual Studio 2005 RC and the SQL Express that comes with it (I followed all of the uninstall instructions first) I can no longer add a SQL Express database to any of my projects, nor can I open the SQL Express database in my original project. When I try either of these tasks, I get the "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed." I read the thread which dealt with this error, and changed the connection string for the database file that had worked before to User Instance = false. The moment I click Test Connection or OK, I get the error: "An attempt to attach an auto-named database for file C:<path to project>EngSQL.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share." (<path to project> is actually a full path, I didn't want to type the whole thing out. :) ). A search for this error turns up a solution of setting User Instance = false, which puts me in a catch 22 position.
View 80 Replies View RelatedI have log shipping set up between 2 SQL 2000 SP1 Servers on Win 2000. The db is small 10 meg, and when the restore job on the backup server fails I am getting "sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." as the message, the maint paln on the primary server show no error. Anyone seen this before? The restore has worked 3 out of 5 times
View 2 Replies View RelatedMany a times see the below error in SQL Error log.
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: ]
Is this something to do here?
Note: If I run the below statement I know that the SQL Error log entry will go off, but wanted to know the real significance of this error?
CREATE LOGIN [NT AUTHORITYANONYMOUS LOGON] FROM WINDOWS
Hi,
I am administering several SQL Servers running SQL Server 2005 SP2 Build 3042.
I have a common maintenance plan that runs on each of the servers. The maintenance plan runs
fine on all the servers except for one. On the one server the Database Integrity check fails with the following error:
Check Database integrity on Local server connection
Databases: <list of databases>
Include indexes
Task start: 2008-02-21T00:05:42.
Task end: 2008-02-21T00:05:46.
Failed0) Alter failed for Server €˜XYZ€™
I created a test maintenance plan to just do the integrity check and selected one database only and this also failed with the same error message. I ran this test maintenance plan and configured it for each of the databases in question and it failed each time.
If I run the DBCC manually against the databases they all report fine.
I read some of the post that talked about the €œAllow Updates€? being set incorrectly but that does not apply to my problem since my configured and run values are set to 0.
Does anyone know what the problem could be?
Hi all help needed from your End.
I have a re-indexing stored procedure,yester day night it got failed
"Executed as user: CONNECTSRVmyadmin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed."
what may be the reason..
[Source - chn_employee_vew_test_txt [1]] Error: Data conversion failed. The data conversion for column "Column 42" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
[Source - chn_employee_vew_test_txt [1]] Error: The "output column "Column 42" (136)" failed because truncation occurred, and the truncation row disposition on "output column "Column 42" (136)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
I using Locale (People's Republic of China) and code page of 936 (Simplied Chinese GBK) with header row delimiter {CR}{LF}.
I am using flat file import method.
Whenever the server process the Column 42 with value "11,Nanjing Rd.W, China" which contain 'comma' or '.' it will hit error importing with above message. When i manually change the column value to non comma or '.' (11 Nanjing Rd W China) in the flat file it is ok.
I am using SQL server 2005.
Please advise what need to be done to avoid this error ?
Thanks in advance and any idea or suggestion is very much appreciated as i have try to solve this issue for over a week but still not able to find any answer on it.
Please help.
regards,
kong
I am running the Sept CTP. I have created a SSIS package that pulls data from a text file and inserts into a database. When I run the package on the DB server it runs fine. I have moved the package the the web server (we are attempting to kick off the package from a web site) and we get connections errors. We are running the package using dtexec from the command line.
View 7 Replies View Related[Source - chn_employee_vew_test_txt [1]] Error: Data conversion failed. The data conversion for column "Column 42" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.".
[Source - chn_employee_vew_test_txt [1]] Error: The "output column "Column 42" (136)" failed because truncation occurred, and the truncation row disposition on "output column "Column 42" (136)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
I using Locale (People's Republic of China) and code page of 936 (Simplied Chinese GBK) with header row delimiter {CR}{LF}.
I am using flat file import method.
Whenever the server process the Column 42 with value "11,Nanjing Rd.W, China" which contain 'comma' or '.' it will hit error importing with above message. When i manually change the column value to non comma or '.' (11 Nanjing Rd W China) in the flat file it is ok.
I am using SQL server 2005.
Please advise what need to be done to avoid this error ?
Thanks in advance and any idea or suggestion is very much appreciated as i have try to solve this issue for over a week but still not able to find any answer on it.
Please help.
regards,
kong
when i right click and execute the package from the Management Studio, it runs fine, everytime. When i schedule a job to execute it, it fails, everytime.
"The package execution failed. The step failed."
i have made sure that the package and job ran using credentials with more than enough access to everything. Still, with no luck. PLEASE! I am at my wits ends here, and the boss is getting antsey...
Any and all help is greatly appreciated...
Anthony
Hi,
Im trying to installed SQL SP1 and I get 'cancelled' status on the Database Services product.
If I open the SQL9_Hotfix_KB913090.log I see a bunch of 'Failed to read" errors. Im not very good at debugging SQL Logs, could you please assists me or tell me where to look?
02/15/2007 15:09:58.436 ================================================================================
02/15/2007 15:09:58.436 Hotfix package launched
02/15/2007 15:09:59.405 Product discovery successfully completed during the install process for MSSQLSERVER
02/15/2007 15:09:59.405 SP Level check successfully completed during the install process for MSSQLSERVER
02/15/2007 15:09:59.421 Product language check successfully completed during the install process for MSSQLSERVER
02/15/2007 15:09:59.421 Product version check successfully completed during the install process for MSSQLSERVER
02/15/2007 15:09:59.421 Command-line instance name check completed during the install process
02/15/2007 15:09:59.421 Baseline build check completed during the install process
02/15/2007 15:10:21.892 Attempting to install instance: MSSQLSERVER
02/15/2007 15:10:21.892 Attempting to install target: DEV08
02/15/2007 15:10:21.892 Attempting to stop service: SQLSERVERAGENT
02/15/2007 15:10:25.893 Successfully stopped service: SQLSERVERAGENT
02/15/2007 15:10:25.893 Attempting to stop service: MSSQLServer
02/15/2007 15:10:27.893 Successfully stopped service: MSSQLServer
02/15/2007 15:10:27.893 Attempting to check for locked files: sqlrun_sql.msp
02/15/2007 15:10:27.909 Attempting to check for locked files: \DEV08D$KitsSQL2005_StandardSP1HotFixSQLFilessqlrun_sql.msp
02/15/2007 15:10:27.909 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out
02/15/2007 15:10:39.520 MSP returned 1602: The user cancels installation.
02/15/2007 15:10:39.567 Successfully checked file: \DEV08D$KitsSQL2005_StandardSP1HotFixSQLFilessqlrun_sql.msp
02/15/2007 15:10:39.567 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
02/15/2007 15:10:39.567 Failed to read registry key: PendingFileRenameOperations
02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
02/15/2007 15:10:39.567 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll
02/15/2007 15:10:39.582 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll
02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll
02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL
02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll
02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll
02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplrec.dll
02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
plisapi.dll
02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:WINDOWSassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll
02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll
02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
plhtfin.sql
02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe
02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMsnapshot.exe
02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplmerg.exe
02/15/2007 15:10:39.598 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe
02/15/2007 15:10:39.598 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe
02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe
02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll
02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll
02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll
02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll
02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL
02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5
C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll
02/15/2007 15:10:39.613 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll
02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
02/15/2007 15:10:39.613 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll
02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll
02/15/2007 15:10:39.629 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
02/15/2007 15:10:39.629 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
02/15/2007 15:10:39.645 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0
C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll
02/15/2007 15:10:39.645 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0
C:Program FilesCommon FilesSystemole dbxmlrw.dll
02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
02/15/2007 15:10:39.645 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
02/15/2007 15:10:39.660 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
02/15/2007 15:10:39.676 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml
02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll
02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll
02/15/2007 15:10:39.676 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033
C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml
02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
02/15/2007 15:10:39.676 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0
C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0
C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe
02/15/2007 15:10:39.692 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll
02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
02/15/2007 15:10:39.692 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
02/15/2007 15:10:39.707 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
02/15/2007 15:10:39.723 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe
02/15/2007 15:10:39.723 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0
C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL
02/15/2007 15:10:39.723 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe
02/15/2007 15:10:39.738 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll
02/15/2007 15:10:51.256 The following exception occurred: User canceled patch install Date: 02/15/2007 15:10:51.256 File: depotsqlvaultsetupmainsetupsqlsesqlsedllfilegroup.cpp Line: 865
02/15/2007 15:10:51.256 Restarting SQL Service MSSQLServer since it was previously running
02/15/2007 15:10:51.256 Attempting to start service: MSSQLServer
02/15/2007 15:10:54.944 Successfully started service: MSSQLServer
02/15/2007 15:10:54.944 Restarting SQL Agent Service SQLSERVERAGENT since it was previously running
02/15/2007 15:10:54.959 Attempting to start service: SQLSERVERAGENT
02/15/2007 15:10:58.350 Successfully started service: SQLSERVERAGENT
02/15/2007 15:10:58.350
02/15/2007 15:10:58.350 Product Status Summary:
02/15/2007 15:10:58.350 Product: SQL Server Native Client
02/15/2007 15:10:58.350 SQL Server Native Client (RTM ) - Success
02/15/2007 15:10:58.350
02/15/2007 15:10:58.350 Product: Setup Support Files
02/15/2007 15:10:58.350 Setup Support Files (RTM ) - Success
02/15/2007 15:10:58.350
02/15/2007 15:10:58.350 Product: Database Services
02/15/2007 15:10:58.350 Database Services (RTM 1399 ENU) - Cancelled
02/15/2007 15:10:58.350 Reporting Services (SP1 2047 ENU) - Not Applied
02/15/2007 15:10:58.350
02/15/2007 15:10:58.350 Product: Integration Services
02/15/2007 15:10:58.350 Integration Services (SP1 2047 ENU) - Not Selected
02/15/2007 15:10:58.350
02/15/2007 15:10:58.350 Product: Client Components
02/15/2007 15:10:58.366 Client Components (SP1 2047 ENU) - Not Selected
02/15/2007 15:10:58.366
02/15/2007 15:10:58.366 Product: MSXML 6.0 Parser
02/15/2007 15:10:58.366 MSXML 6.0 Parser (RTM ) - Not Selected
02/15/2007 15:10:58.366
02/15/2007 15:10:58.366 Product: SQLXML4
02/15/2007 15:10:58.366 SQLXML4 (RTM ) - Not Selected
02/15/2007 15:10:58.366
02/15/2007 15:10:58.366 Product: Backward Compatibility
02/15/2007 15:10:58.366 Backward Compatibility (RTM ) - Not Selected
02/15/2007 15:10:58.366
02/15/2007 15:10:58.366 Product: Microsoft SQL Server VSS Writer
02/15/2007 15:10:58.366 Microsoft SQL Server VSS Writer (RTM ) - Not Selected
02/15/2007 15:10:58.366
How do you make Asp.net use something other than the local ASPNET user for data access in sql server
View 3 Replies View RelatedI need to copy 80 logins within the same SQL Server (7.0 SP1) from 80 "old" logins that I'll delete later.
I clearly need to maintain all the security options for the new logins.
Is there a way to do this, adding the logins with the new name and granting all security options? Is there a script that will do this task or can somebody help me in doing that?
Thank you.
Hi,
I have two servers (server1, server2). I was trying to access the data from server1 to server2. I linked the servers and set up the option for data access.
when I run the following command from server1: sp_remoteoption 'server2', 'sa', 'sa', TRUSTED, TRUE
It gives me the following error. How to handle this.
Server: Msg 15185, Level 16, State 1, Line 0
There is no remote user 'sa' mapped to local user 'sa' from the remote server 'server2'.
I appreciate your help.
Thank you.
Eric s.
I have a server that was recently upgraded from SQL 6.5 to 7.0 that contains almost 700 logins using standard security. Is there a limit to the number of logins that SQL will host? The logins/users have all been added using a GUI within an application and does not support NT authentication. Does this cause any known problems in SQL 7? When I right click on the database and go to properties / permissions MMC gets hung up. Also one of the systems analysts is convinced that SQL is dropping permissions (I disagree to this). Any one have any thoughts or experience with large numbers of logins / users?
Linda
Does anyone know of any 3rd party software applications that will make users change their SQL
logins every 3 months?
Thanks,
Heather
Hi!
How can I copy all logins from one SQL server 6.5 to
another one.
Thank you.
Anny.
How can I determine which users are using the database??
Thanks
I am new in sql and have problems about logins.
with sql 2005
1)I create a windows login in my home pc (win xp home sp2) and i can connect server with ssms this new user
but in my office (win xp pro sp2) create a windows login (it is a windows user also) and when try to connect with ssms take error 18456 (user name and pass is true!!!)
2)in my office pc i create a sql login which has no role. but this user can create users and dbs. but in my home pc, user has no role cant do thats...:eek:
Hi everyone,I am new to this forum.I hope some body will help me in this,I am trying this for the past 6hrs.
on my server there are some hundreds of sql logins are there,I need to identify the logins which doesn't associated with either any databases or dbroles,server roles.Later i need to delete those logins.Can any body help me in this.
Thanks in advance.