I presently have Error Logging turned on for the SQL Executive, but I no longer want it. When I
open up the "Configure SQL Executive" window under the Server menu, the
"Error Log File" field is dimmed and there is no option to turn it off.
I am running a SQL maintenance job on a 40 GB database which performsoptimizations by re-orginizing data and indexes pages. After the jobis finished, a separate job peforming a SQL transaction log backup isrun on the same database, which produces a 30 GB transaction log backupfile. Is there any way to turn off logging during the maintenanceplan, so that when the transaction log backup occurrs it will notproduce a large backup file?
Hi all Can someone tell me what are these Logs mean. If you right click on SQL executive in EM and select Error Log you'll get a list of errors,warnings...etc.
In my Case I get these Errors that are occuring every few seconds. 11/05/98 09:03:10 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:12 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:18 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:28 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:35 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:40 AM DBLIB ERROR HANDLER: LOGIN INCORRECT 11/05/98 09:03:46 AM DBLIB ERROR HANDLER: LOGIN INCORRECT
And Warnings:
11/05/98 09:03:10 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection. 11/05/98 09:03:12 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection. 11/05/98 09:03:16 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection. 11/05/98 09:03:22 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection. 11/05/98 09:03:28 AM DBLIB Message HANDLER: LOGIN FAILED - User: sa Reason: Not Associated with a trusted SQL Server Connection.
I have no clue which security i use on the server and on my workstation. How can one find out which security is being used.
Hi, I want to see my sql executive error log but it grown like anything. How i have to trucate my error log. I cannot stop my server now. i am getting following message. and also suggest me what i have to do not to grow like this means 56.01 mb size. The sql executive error log is 56.01 mb in size and loading it will consume considerble memory and may take several minutes to complete. Now i want to see my executive error log , pls tell me what i have to do.
I just inherited a SQL Server that was set up by a non-DBA. It`s running NT 4.0 and SQL Server 6.50 - 6.50.201 (the vendor hasn`t certified the product on SP4). I am trying to change the SQL Executive Service to use a non-system logon account. The account that I want to use is running SQL Executive on 9 other servers.
I went into Usrmgr and added the account to the administrators group. Made sure that it has rights to: log on as a service, log on as a batch job, increase quotas, act as part of the operating system, replace a process level token.
When I try to change to that id in services, I get the following error:
"cannot set the startup parameters for SQL Executive service. Error 1057 occurred. The account name is invalid or does not exist."
Looking in Technet, I found that if "log on as a service" isn`t set you could get this message but I`ve check/re-checked, had someone else check and it`s set.
I click on menu item SSIS and enable logging to my SQL Database (SSIS log provider for SQL Server). When I run the package it runs fine for the first time. Upon subsequent runs I get the following error.
[Log provider "SSIS log provider for SQL Server"] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E14 Description: "There is already an object named 'sysdtslog90' in the database.".
It seems like I need to drop the table every time to avoid this error. Is there a way I can log all package logs to single table historically? Any weblink or tip is appreciated.
I am developing a package on my local workstation. I have defined two logging service providers. One is for SQL Server and the other is for the Windows Event Log. I am using the Dts.Log method in a script task to write log entries.
Logging is working properly with the SQL Server provider and rows are being inserted into the sysdtslog90 table. However, the only events that are being logged in the Windows Event Log are the package start and end events which I believe SSIS is doing automatically anyway.
Is there something I need to do to enable WIndows Event Log logging other than defining a log provider and making sure it is checked active? Won't SSIS write to two different logs with one Dts.Log call? Any ideas on what might be going wrong with my approach?
I am getting the following error when I log into SQL server using MS SQL Server Management Studio.
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.) (.Net SqlClient Data Provider)".
I tried to allow remote connections using Surface Area Configuration, but it is not allowing me to do so.
I am not sure what I need to do. Anybody, please advice.
I'm using the Execute SQL Task to import error messages into a table. I'm using the following:
"INSERT INTO SSISLog (EventDescription) VALUES (" +@[System::ErrorDescription]+")"
I've got an import task with deliberate errors in the file to be imported to test the error logging task. When I execute it, I get the following messages:
[Execute SQL Task] Error: Executing the query "INSERT INTO SSISLog (EventDescription) VALUES (An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Invalid character value for cast specification". )" failed with the following error: "The name 'An' is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
[Execute SQL Task] Error: Executing the query "INSERT INTO SSISLog (EventDescription) VALUES (There was an error with input column "IssueNo" (94) on input "Destination Input" (68). The column status returned was: "The value could not be converted because of a potential loss of data.". )" failed with the following error: "The name 'There' is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
[Execute SQL Task] Error: Executing the query "INSERT INTO SSISLog (EventDescription) VALUES (The "input "Destination Input" (68)" failed because error code 0xC0209077 occurred, and the error row disposition on "input "Destination Input" (68)" specifies failure on error. An error occurred on the specified object of the specified component. )" failed with the following error: "The name 'The' is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
[Execute SQL Task] Error: Executing the query "INSERT INTO SSISLog (EventDescription) VALUES (The ProcessInput method on component "Destination - tbl_clients" (55) failed with error code 0xC0209029. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. )" failed with the following error: "The name 'The' is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
[Execute SQL Task] Error: Executing the query "INSERT INTO SSISLog (EventDescription) VALUES (Thread "WorkThread0" has exited with error code 0xC0209029. )" failed with the following error: "The name 'Thread' is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Hi, I decided to use the SQL Server log provider to store logging data of all my Integration Services packages. I also created some reports about this data for operating purposes. I have a problem occurs the name of the executing package is not always written to the log,but the name of the single task which failed. But that is not very useful information for operating, because I do not see any chance to get the name of the package by the information which is logged in the sysdtslog90 table in the database which I defined for SSIS Logging.
How do I configure the package to always log the package information into the table, too?
How can I avoid certain messages from SQL Server being recorded into the Event viewer ? For example, every time I truncate the transaction log with 'Backup log with truncate_only', It is being recorded into the Event viewer as an Error. But, I know that it is not an error. How can I avoid this ?
I am running some DBCC checks as a routine maintenance task on my sql server 2000 servers. I am running DBCC CHECKDB, DBCC CHECKCONSTRAINTS and DBCC CHECKCATALOG. I have established a set of procedures and tables to capture the output from the error log after running these DBCC commands. After running all three, it appears the same info captured for CHECKDB is not logged for these two: CHECKCONSTRAINTS and CHECKCATALOG. Does anyone know why these are not logged and if it is even necessary for me to run these 2 extra DBCC checks? If not, can anyone recommend what database consistency checks should be executed on a daily basis for a production database server?
DBCC CHECKDB (DBNAME) executed by lshores found 0 errors and repaired 0 errors. Elapsed time: 0 hours 20 minutes 32 seconds.
I have a small requirement in SSIS Error Logging Mechanism. Presently in my SSIS package i am using a File Connection Manager for creating a Log file. I have a problem on this regard. Every time when i am executing my DTS package, the error log messages are getting appended to my error log at OS level (say D:error_messg.log). And for this reason whenever my DTS package is getting executed the size of the file is keep on increasing and there by killing my disk space.
I have a requirement for this error logging mechanism. At any time my log file should not exceed more than 20MB. Or can we remove the log events a week ago or say more than 2 days or say. Just ensuring the log file do not fill up the disk space eventually.
How can we do this? Any suggestions are greatly appreciated.
Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) If I insert a wrong password I get the same error message. Which means that I don’t have access to the file. I definitely could use some help since from my provider I get none. Thank you Dov Kruman
Hello,I was wondering if there were any built-in objects to handle error handling, in any of the SQL Server objects, or just to use event log or trace or debug or something like that. Or is it not recommended at all to use try.. catch, for whatever reason.Thanks a lot.
I am getting the following error. “The user instance login flag is not supported on this version of SQL Server. The connection will be closed.� Background i created a site on my development machine, and every thing worked, this computer is running sql EX. I uploaded the site to the production server (running sql 2005 standard) and changed the connection string (i have used this connection string with other dB’s to display data only, and it works) but i tried it with the ASPNETDB.mdf in the AppData folder and i get the above message.
Do i have to set some special permissions in the db for it to work. I need to be able to insert, update, and delete in this app.
Just like in DTS where we can add error file so that if the DTS package fails we can see what caused the DTS to fail, likewise do we have anything like error logging file in SSIS. I greatly appreciate your help on this. thanks!!
I have merge replication setup to a bunch of mobile subscribers. I want everything managed from the server and I want everything to run continuously. The reason we want this is that we want subscribers to automatically synchronize data within 60 seconds of plugging into the network from any location. We do not want to write anything to have to detect connectivity and initiate it. We do not want it initiated from a subscriber either. This creates a SEVERE logging issue and has halted a roll out at 2 different customers. We can't get beyond about 60 subscribers on a system that was running 3700 subscribers in SQL Server 2000. The server quite literally freezes and becomes non-responsive 1 - 2 times per day. We've tracked this back to the volume of logging into the Windows event log that is being caused by the replication engine.
When subscribers are disconnected, they throw constant errors, to the tune of 1 error every 2 minutes into the SQL Server error log as well as the Windows event log. This is because someone decided that these should be level 18 errors. There is no error. The publisher could not contact the subscriber, so I want it to simply log an error, shut up, go back to sleep, and then try again. I do NOT want a message in my SQL Server error log and I do NOT want a message in my Windows event log.
We are currently logging over 60,000 messages per day into both the Windows event log and the SQL Server error logs for something that we KNOW is a NORMAL operational state of the system. The merge agent doesn't have a parameter that I can feed it to ignore 14151 errors.
The culprit is in sys.sp_MSrepl_raiseerror. Since it is a system object, I can't override it and change the severity level of the error. So, right now we are stuck and the SQL Server error log as well as Windows event logs are being rendered quite useless on the system.
Does anyone have any idea how I can forcefully change sys.sp_MSrepl_raiseerror or in some other way suppress the logging of 14151 errors from the Windows and SQL Server logs?
How can I copy the error messages when I execute a SSIS package?. The Progress tab or the Execution results tab both dont have the means to copy the results. I would like the errors to be output to a text file under a directory on my drive system (some thing like C:SSISExecResults.txt). Is this possible?. If so how do I configure my package to output the package execution results to a text file?.
Hi all! Does anyone of you know what port number SQL Executive is using? Is it separate from the SQL Server's 1433? I have a user who is behind a firewall. He can connect to sql server but he can not run a task manually. If the task is scheduled it is successful but if he run manually , sql server display "The SQL Executive service is not currently running on <servername>. This prevents task .... from being run." Eventhough the service is running and other jobs are successfully.
Would it be possible the port for SQL Server is open to that user but not the sql executive.
i have both SQL Server 6.5 and 7.0 installed...for some reason i cannot start SQLExecutive while operating on 7.0...when i try to start the service it says 'Yu need SQL version 6.5 or later to start SQL Executive' has ayone come across such an error?
Having issue starting this service on SQL7 SP2. Returns "specific error 109" Any tips on resolution--no help on MS site search. what are ramifications of NOT starting this service if it is a single Server and the SQL application we use does not seem to be affected other than problem loading SP3 and is this related?
When trying to run SQL Executive from the SQL Enterprise manager it run in a dos window ( all scheduled tasks runs fine). PS: the machine in question had sql 6.5 installed , removed and then and then re-installed again. this is when the problem started.
When the embedded DTS package fails at runtime, and logging has been enabled for the package (and all log events selected for reporting on for the package and the task), the DTS error (i.e. any meaningful errors) are not thrown up to/caught by the SSIS/outer level. All you get is something like:
COMException - error returned from a call to a COM component.
Does anyone have any comments &/or know to get errors thrown from within an embedded DTS package, thrown up to the wrapping SSIS package?
I just installed SQL Server 2005 with SP2 on Vista. When I try to login from SQL Server Management Studio, I get the following error message in the log: --- 2007-09-15 18:58:02.23 Logon Error: 18456, Severity: 14, State: 11. 2007-09-15 18:58:02.23 Logon Login failed for user '<computer name><user account>'.[CLIENT: <local machine>] ---
Since I can't login, I can't try some of the stuff I have seen here, such as creating new logins etc.
I installed Analysis Server and Integration Services at the same time. Logging in to them both works fine.
I use windows authentication. I don't know if changing that helps, as I don't know how to change it without logging in in the first place...
I have registered a Sql server on my local machine.
I can adddelete jobs to the Task Scheduler, view job histories etc on that server however, when I try to execute a job on that server using the Task Scheduler, I get the following error message:
"The sqlexecutive servive is currently not running on server <server name>. This prevents the task from running".
I have checked the SqlExecutive service on the server and it is running. I have jobs that get executed each night via the Task Scheduler
Does anyone have any idea of what the problem could be ?