I'm scheduling a T-SQL job with SQL Agent. The job uses PRINT to write out various progress and status messages as it runs. I created an Operator, and set a Notification when the job fails -- will that send me the entire output of the job, or just the error message?
View 1 RepliesHi guys, I'm trying to figure out why i'm having issues with the SQL server agent trying to start.
the error i get is 14258 cannot perform this operation while sqlserveragent is starting. try again later. sql-dmo(odbc sqlstate:42000)
any ideas how to fix this. I start the service as a domain user that is an admin on the server. but when i run a job it gives me the above error.
thanks.
I have a replication Push Subscription configured that works most of the time but I get occasional errors satating that "The process could not connect to the Subscripber 'xxxx'". The details are
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
(Source: PYRRXNDAL341WIN (Data source); Error number: 18452)
This happens randomly and when it does fail, I can either what for the next occurence in the schedule or I can start the agent manually and it completes successfully. I can also ping the other box when it happens. I've looked at the event logs and don't see anything going on around the times the distribution agent is having the problems.
Any suggestions on where to start looking for more detail?
Hello to all,I've fallow problem. I've a sp called as a job of SA each minute. Thisruns pretty nice, but from time to time, the job is aborted, and Idon't know why.Considering my logging, which is implemented in DB, I know, in whichpoint it is happening, but I don't know the exact error.This one is for sure any SQL server exception.I wanted to track this error, but reading all news, and help, andperforming some tests, I've find out, that this is almost likeimpossible, to catch the error in t-sql code (for example in this sp),and wirte it to any table for futher review.Reading great documentation from Erland Sommarskog, I know, there isno way to catch this error in t-sql, because, usualy the sql terminatesexecution of the code immieadetly (so I found it also by my tests).Now, my question is: sice I'm calling this sp continously in ServerAgent as a job scheduled to be called each one minute, is it any way,to trap this error on this level? In SA? and THEN save it somewhere inmy db?I'm calling the sp as a 'command' in job step as 'execsp_name_of_procedure'.If I'll try like this:declare @err intset @err = 0exec sp_name_of_procedureset @err = @@errorif @err <> 0begininsert into tbl_logger (sql_error, msg) values (@err, 'SQL raised anerror')endwill it work, or the sql will assume the whole code as a one batch, andwill terminate after call of sp?Thank you in advance for reply.GreatingsMateusz
View 2 Replies View RelatedI've got a very simple package that truncates some rows from a table. The packages utilizes configurations as described in a post I made on this forum yesterday http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3062343&SiteID=1.
When the package is deployed and installed on the prod server, it runs successfully from the Execute Package Utility, utilizing the configurations as expected, removing the rows from the target table.
When the package is run from the SQL Agent on prod, it completes successfully without errors, but the rows in the prod table remain. On the "Data Source" tab in the job, the correct connection string shows pointing at the prod database (picked up from a config file on the prod server).
Curiously, the job appears to run the truncate against the test db table - I tested this by putting rows in the target tables on both test and prod. When the package is run from SQL Agent, the test rows are removed. When run from the Execute Package Utility on prod, the prod rows are removed. Huh?
Again, the Data Source tab in the Job on prod shows the prod db connection string and the package removes the rows correctly from the prod table when run from the Execute Package Utility on prod.
Does anyone have any thoughts on this behavior when using the Job Agent to execute a package?
Thanks!
Jamie Pick
I've deployed an ssis package to the database server through the manifest file over the network..
The package runs great when testing through vs.net on my client.
I've added the package to a job step in the sql server job agent.
When I test the new job, the package step fails, but there is no error or log information in the job history.
Wwhere can I get error information? And/or How can make SSIS error information more verbose in the job history?
Thanks for any help or information.
Hi There - is it possible to output the SQL that a SQLDataSource
control is generating. I am having a difficult time diagnosing
errors such as the following:
Keyword not supported: 'unicode'.
Any help is appreciated.
Hi,
I have more than 80 databases on my publisher (SQL Server 2000 SP4), I tried to enable Transaction Replication on all of those databases instantly through some T-SQL programming and DTS Packages. Every thing works fine until the snapshot agents starts to take sanpshot from the publisher databases. As soon as their snapshot agents start for those 80 databases, they start giving the deadlock error. All 80 snapshot agents starts at the same time.
Error Message:
Transaction (Process ID xxx) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Error Detail:
Transaction (Process ID xxx) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
(Source: Server_Distribution (Data source); Error number: 1205)
---------------------------------------------------------------------------------------------------------------
WHY???
Hi,
I've just installed SQL 2005 SP2 Rollup 3 Package (Build 3186) on a 2 node X64 W2K3 Cluster.
Everything went fine, although after the install, the SQLAgent Services of my instances started to complain about delegation not enabled for the domain account used for the SQLAgent Service.
SPN's were already registered, so I've enabled unconstrained delegation & no errors anymore..
Apparently we're obliged to enable delegation as soon as this hotfix is installed
(maybe due to fix 938086 included in it ?)
To make this setup more secure, we would like to enable constrained delegation.
This does not seem to work, as soon as we choose constrained delegation by adding the SPN of the clustername to the domain user account we're running with & restart the sql agent, it fails with the same error as when no delegation was configured:
! [298] SQLServer Error: 22022, CryptUnprotectData() returned error -2146892987, 'The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.' [SQLSTATE 42000]
! [442] ConnConnectAndSetCryptoForXpstar failed (0).
Summary:
With Unconstrained delegation enabled for computer account & user account, everything goes fine.
As soon as constrained delegation is chosen, by adding the SPN's to the domain user account of SQL Agent, SQL agent fails to start.
We use a domain account for the SQL Agent.
This account has an 2 SPN registered on it
MSSQLSvc/<FQDN SQL instance network name>:1433
MSSQLSvc/<FQDN SQL instance network name>
Connections to SQL go fine, authorization scheme is Kerberos even when SQL Agent fails to start due to this delegation failure.
Domain account has "act as part of operating system" & "impersonate a client after authorzation"
Anyone an idea ?
I have been using SSIS for about two months now and one of the main difficulties I have had is migrating Sql Agent SSIS jobs around environments.
Usually, the SSIS fails because of permissions to file systems, data bases, etc, but until now, I have had to discover these almost by guessing because the job history never game me any useful information. Also, from what I see, the SSIS logs have been unreliable, at best.
What I have done lately is creating Operating System (CmdExec) Steps as part of the job (not SSIS steps) and inserting the output of dtexec.exe into the history.
This seems to give me information that has been really hard to get, otherwise.
My question is (I am no DBA or ETL expert), is this the best way of getting the output of the package when debugging migration issues? Why doesn't the SSIS Steps have a similar feature of outputting useful info to the job history?
Hi,
View 5 Replies View Related
Hello,
I have created a package that runs without problem.
I run the package with the command dtexec /F "package_name.dtsx" > package_name.txt.
Then I run the same package from SQL Server Agent, everything is OK
Then, I tried to edit the command line to have the output file, but I got an error.
The command line is:
dtexec /F "package_name.dtsx" MAXCONCURRENT "-1" / CHECKPOINTING OFF /REPORTING E > package_name.txt.
(MAXCONCURRENT "-1" / CHECKPOINTING OFF /REPORTING E are created by default)
How can I do?
Thank
Hi All,
I have a requirement of logging the failure and the error of a job executing a SSIS package to text file.
However, when I go to job step -> Advanced, in the section "SQL Server
Integration Services Package" where that info to setup logging is, it
is blank and just says:
"There are no options for this command type"
Any ideas?
I thought that this might not be supported in Standard Edition as I am running standard edition. Then I checked on two other servers, where I have Enterprise edition with SP2. On one of the installations, I am able to give the log file, the other one still shows,
"There are no options for this command type"
What is the problem? Both of them I am using the sysadmin role account. I have proxy account created on both the SQL instances. I don't think this is the problem, but still I checked this.
Can anybody help me?
Regards,
Virendra
Hi,
I've created a stored procedure that creates a script to create a number of objects within the database (based on what existing objects are in the database). From Management Studio, this works fine, and the output is exactly as I want it.
I'm now trying to create a job that will execute this stored procedure, and deposit the results into a file somewhere on the server. When the job runs, the script is created in the correct place and is essentially ok.
However, there are a couple of questions I'd like to ask.
Why does SQL Server Agent put a header at the top of the output file? I was hoping to be able to use that output file 'as is' and execute it automatically to recreate my objects when required. (Obviously, I can manually remove the header, but this is an inconvenience in this situation). How do I stop it?
Also, when executed from SSMS, the output is correctly line-spaced. But, the output from the scheduled job adds an extra line between each line of text, which is, again, inconvenient. Why does it do this, and how can I prevent this (again, without manually editting the output)?
Any thoughts and help greatly appreciated.
Cheers
Simon
Hi,
I have stumbled on a problem with running a large number of SSIS packages in parallel, using the €œdtexec€? command from inside an SQL Server job.
I€™ve described the environment, the goal and the problem below. Sorry if it€™s a bit too long, but I tried to be as clear as possible.
The environment:
Windows Server 2003 Enterprise x64 Edition, SQL Server 2005 32bit Enterprise Edition SP2.
The goal:
We have a large number of text files that we€™re loading into a staging area of a data warehouse (based on SQL Server 2k5, as said above).
We have one €œmain€? SSIS package that takes a list of files to load from an XML file, loops through that list and for each file in the list starts an SSIS package by using €œdtexec€? command. The command is started asynchronously by using system.diagnostics.process.start() method. This means that a large number of SSIS packages are started in parallel. These packages perform the actual loading (with BULK insert).
I have successfully run the loading process from the command prompt (using the dtexec command to start the main package) a number of times.
In order to move the loading to a production environment and schedule it, we have set up an SQL Server Agent job. We€™ve created a proxy user with the necessary rights (the same user that runs the job from command prompt), created an the SQL Agent job (there is one step of type €œcmdexec€? that runs the €œmain€? SSIS package with the €œdtexec€? command).
If the input XML file for the main package contains a small number of files (for example 10), the SQL Server Agent job works fine €“ the SSIS packages are started in parallel and they finish work successfully.
The problem:
When the number of the concurrently started SSIS packages gets too big, the packages start to fail. When a large number of SSIS package executions are already taking place, the new dtexec commands fail after 0 seconds of work with an empty error message.
Please bear in mind that the same loading still works perfectly from command prompt on the same server with the same user. It only fails when run from the SQL Agent Job.
I€™ve tried to understand the limit, when do the packages start to fail, and I believe that the threshold is 80 parallel executions (I understand that it might not be desirable to start so many SSIS packages at once, but I€™d like to do it despite this).
Additional information:
The dtexec utility provides an error message where the package variables are shown and the fact that the package ran 0 seconds, but the €œMessage€? is empty (€œMessage: €œ).
Turning the logging on in all the packages does not provide an error message either, just a lot of run-time information.
The try-catch block around the process.start() script in the main package€™s script task also does not reveal any errors.
I€™ve increased the €œmax worker threads€? number for the cmdexec subsystem in the msdb.dbo.syssubsystems table to a safely high number and restarted the SQL Server, but this had no effect either.
The request:
Can anyone give ideas what could be the cause of the problem?
If you have any ideas about how to further debug the problem, they are also very welcome.
Thanks in advance!
Eero Ringmäe
Ok,
I have a network folder called A
I have a SharePoint (2007) Document Library site called B. Web Client is enabled on the server and B is mapped as a Drive (let's call it Y for this discussion)
I want to move documents in A to B. Easy enough, right? Not so....
I first started by creating a batch file that issues a COPY \A \Y /Y at the command prompt. Viola! Worked Great!
I then moved that command to a SQL Agent job as a CMDExec statement (exact same statement) and attempted to run it.....CRASH! It found the files in A but then said "The system cannot find the path specified"
Ok, so I tried it in SSIS. CRASH! Checked the error log. Same thing...
So I then checked the account under which the SQl Agent was running (special domain account for all our SQL Servers). Thinking it might mater I changed it to run under my name (I'm in Domain admin). I also ensured I had permissions to the SPS 2007 library as well. (I did).
Ran again! CRASH! Same error....
So, I created a batch file , placed thec ommand in the batch file and ran that from the command prompt! Viola! Worked Great.
So, I was thinking of how ingenious I was as I pasted my C:RootCopy.bat into my SQL Agent job. With a big grin on my face I right clicked and picked "Start Job at step".......CRASH! Same error.
Does anyone have any ideas on this ???????????????
Thanks,
Stephen
I am trying to get SQL Server 2000 to report errors of jobs we have running on our SQLServer.
We have installed Office2000 Outlook, but we keep getting the same error when we try to test it:
Error 18025: xp_test_mapi_profile: failed with mail error 0x80040111
The Exchange is on a different server, we have the Profile set up on the server, not the PC's, they just pull a copy of the Mailbox.
Any assistance would be greatfully appreciated.
Hi All,
I have an issue with Reporting Services that I have been unable to fix or find any answers to. I hope you guys can help. I have a list of 10 reports that run during the period of 1-4 each morning. They are scheduled to run on each database at a different time (5 databases in all). So there should be 50 reports at the end of the night. I wrote a report that looks for the last status of a report that shows that it wasn€™t successful. The only thing it tells me is this:
Failure writing file ABC Production Report: An error has occurred during report processing.
When there is a login error then I get that message so I know it isn€™t that. Also reports can error out one night and then work the next night. When I look at the time that the error status was written I see that it took 4 seconds from run time.
Does anyone have a clue what this means or better yet how I can get all of these reports to work consistently?
Thanks,
Sandie
I'm looking for a tool that can read the SQL Agent tables and generate a chart or graph of when jobs are scheduled. This could be used to determine when a job can be scheduled without interfering with other jobs, or to determine
where a maintenance window might exists.
The chart could be for a particular day, or week or month. It could be for a single database or all databases on a server. The tool could also read job history and display a graph of execution time (with success and failure displayed in different colors).
I don't know of anything like this in existence. I've looked at the stored procs supplied with SQL Server that help generate the data for the Enterprise Manager's GUI. I see thinks like the job schedule frequency information hardcoded in the stored procedure, instead of table driven. That's scary!
SQL Probe software is cool, but it doesn't do the reporting I'm looking for.
When running the following:C:Program FilesMicrosoft SQL Server80ToolsBinn>rsactivate -c"C:Program FilesMicrosoft SQLServerMSSQLReportingServicesReportServerRSRepo rtServer.config" -tI get the following error:Failure starting the web service:System.Exception: The local NT Service is disabled 0x80090005 --->System.Exception: 0x80090005--- End of inner exception stack trace ---atMicrosoft.ReportingServices.RSActivate.RSActivate. RpcActivateService(Int32clientType)at Microsoft.ReportingServices.RSActivate.RSActivate. InstanceMain()at Microsoft.ReportingServices.BaseCmdLine.CommandLin eMain(String[]args, BaseCmdLine instance)Any insight into this. What am I doing wrong.
View 1 Replies View Relatedhi,
I set up Reporting Services about 9 months ago when I installed Microsoft CRM 3 (Dynamics?), but these problems have only just started occurring. Lost count of how many hours have been wasted looking for answers!
Apologies if this rambles on like a cheap book but i don't want to miss out any of the detail..
CRM stops working within an hour of IIS starting up, but if somebody logs in to CRM before it goes down then it's fine for the rest of the day. However the next day it's back to square one. Looking through Event logs it seems to be caused by SQL Reporting Server, because;
Report Server errors show it starting up after IIS, but within an hour throws up "Exception: System.Runtime.Serialization.SerializationException - Message: Unable to find assembly 'Microsoft.ReportingServices.Diagnostics". It's at this point that IIS stops responding altogether, hence CRM stops working.
Running iisreset from the command line makes IIS work again, but this becomes a pain in the backside running it every morning before my colleagues get in. I have set up a schedule to run it for me, which works, but as i said if nobody logs in within the hour (which does happen at least once a week), then CRM won't work until i manually run iisreset again.
Also Reporting Services Configuration Manager does not start properly, so i can't even go through that to see if it's a config problem - when launching it i get an alert box with "An unknown error has occurred in the WMI Provider. Error Code 800706B3". That's with the default server name already in the box, but no matter what server name or IP I try to get it to connect to, it just will not have it. Also that error code seems to be unique to me, since not one webpage exists with the same code.
Other things i've gone through;
- SQL Server Configuration Manager shows everything Running, including Report Server
- SQL Management Studio shows all CRM & Reporting Services databases exist and are online.
- The Report Server error log shows this: "w3wp!library!1!29/03/2008-12:34:00:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerServiceUnavailableException: The Report Server Windows service 'ReportServer' is not running. The service must be running to use Report Server."
- http://localhost/ works fine.
- http://localhost/Reports/ shows up a .Net error page with Security Exception error: "The application attempted to perform an operation not allowed by the security policy".
- http://localhost/ReportServer/ shows up a page with "localhost/ReportServer - / ---- Microsoft SQL Server Reporting Services Version 8.00.1038.00" which i assume is lacking correct content.
- When CRM was configured the setup wizard moaned that it could not use the existing Reporting Services database or IIS directories, so for that purpose there are two more virtual directories in IIS..
- https://localhost/ReportsSQL/ shows up an error: "Unable to connect to the remote server"
- https://localhost/ReportServerSQL/ shows up an error: "Reporting Services Error - The Report Server Windows service 'ReportServer' is not running. The service must be running to use Report Server. (rsReportServerServiceUnavailable)"
- While trying everything i am logged in as server admin
- Software specs: Windows 2003 Small Business Server (SP2), SQL Server Standard 2005 (9.0.3054 / SP2), all patches from Microsoft Update (not just Windows Update) have been applied.
If you managed to read this far then thank you.. I'm nearly bald with frustration so if someone could please suggest things worth looking into or trying, that would be very much appreciated.
Cheers
How do I enable remote errors for Reporting Services 2005?
View 5 Replies View RelatedOur users tend to generate a lot of one-time reports through Reporting Services. The problem is that this seems to generate a lot of Jobs in SQL Agent. So many, in fact, that we'd like to set up a job to delete them periodically (nightly or weekly). I could go in & delete them through SS Management Studio but I'd like to manage it automatically. Let me state up front that I have limited experience with Reporting Services so if my questions seem basic, forgive me.
First, is there a way to avoid creating a SQL Agent job if this is a non-scheduled report? That would be optimal then there would be nothing to clean up.
Barring that, what's the "Best Practice" for doing this automatically? I found the jobs listed in msdb.dbo.sysjobs and other sysjob* tables. Is it reasonable for me to delete from these various tables (sysjobs, sysjobactivity, sysjobhistory, sysjobschedules, sysjobsteps, & sysjobstepslogs) if the job was generated by reporting services (i.e. sysjobs.description containing 'report server process') and no schedule exists (i.e. sysjobactivity.next_scheduled_run_date IS NULL)? What damage could this cause? Is there anything else I need to take into account?
Thanks,
Pat Brickson
I put a similar post on experts-exchange....
What I am looking to do is create a reporting framework that uses SQL Server and outputs as XML (only because that could be consumed by various clients).
I also want to create title, subtotals, etc., and even page breaks of I can.
I want to do this all in T-SQL so new reports can be added by DBA's rather than have the developer re-code, re-compile, re-distribute, etc.
I think on the DB side it would be as easy as creating a table that is a 'catalog' of available reports with their names, etc., and a set of stored procs that would run the reports.
Has anyone ever done anything like this, or in some better way?
Thanks.
I've build a few reports in visual studio, they work and they don't work, in a minute I can run them next minute I can't and I get this errors in event viewer every time they can't be run:
Report Server (MSSQLSERVER) cannot load the SQLPDW extension.
Report Server (MSSQLSERVER) cannot load the TERADATA extension.
Hello All,
I just performed a fresh install of MSSQL 2005 Server Developer Edition on my XPSP2 machine along with MSSQL 2005 SP1 and I noticed that errors are not being reported in the Windows Event Viewer. Is there a way to enable/disable logging here?
I need to view these logs because when the tasks > 'copy database' task fails it submits its error in the Windows Event Log however since I reinstalled MSSQL 2005 these log entries don't appear here.
thanks in advance.
I manually build my url for my reports. In the url I build, I can specify the output format I would like it to automatically use when the report opens. However, it always first opens the dialog box to either Save, Open, or Cancel. Is there anyway to bypass this and just open it in the format I have coded in the url? Thanks.
View 2 Replies View RelatedWhen I try to install sql server 2014 on my machine,all the features were installed but except Reporting services-Native and error occurred as shown below.
Error details:
§ Error installing SQL Server Reporting Services
Updating permission setting for folder 'C:WindowsTemp' failed. The folder permission setting were supposed to be set to 'DA;OICI;0x1200af;;;S-1-5-80-4063824523-3130906261-2263067808-2545249320-213050741)'.
Error code: 0x84CF0003
Is it possible to use a stored procedure that outputs xml to render a report? If so, any tips on how to go about it will be very much appreciated.
Thanks,
Nick.
Does anyone know how i can go about merging preexisting pdf files and SQL server reporting services output. Can this be done in reporting services? For example, I have 5 pages from a pdf files which is created from another 3rd party software provider. I then i have output from sql reporting services. How can i merge these two outputs and deliver it over .Net/ ASP framework?
thanks
I have a report that uses a stored procedure as a dataset.The stored procedure accepts four parameters, which I have defined in the report. works fine in query builder and SSMS.
When I run the report I get an error stating a parameter is missing. I tried deleting parameters and recreating not luck.
I just created my first report using sql server reporting services
Now I am having some data discrepancies, trying to figureout how I can troubleshoot this issue.
The report has been created against the stored proc, when I run the stored proc within the sqlserver, I get 3 rows, but when I run the report I get only 1 row. I am kind of confused, how can I troubleshoot this issue, Thanks.
I am working on SSRS 2008 R2 in BIDS. The report's data source is from Stored Procedure which is running good in SQL Server 2008 R2.
The stored procedure has an output parameter, which I don't know how to set in BIDS, so when I try to add the data source to the report, a mistake is shown up.
So my problem is:
1. How to set the output parameter correctly, so the data source(stored procedure) can be run as good as it were in SQL Server 2008 R2.
2. How to get the output parameter value in BIDS which will be used to set the title of table dynamically.