I've created an SSIS package which runs perfect when scheduled as a job.Now I've have a requirement that a mail ought to be sent every time it runs stating if the package was successfully completed or failed.
I've created an SMTP Connection with server name as mx.xxxxxxxx(organization).I've neither checked windows authentication or Enable Secure Socket Layer Options(as suggested in various blogs).
The Job runs fine and sends mail when run manually but is failing when scheduled as a job.
I've tried running it by editing the command line as suggested by many but with no success.
Can you please suggest where I might be going wrong,
Below is the error:
Argument "SMTP" for option "connection" is not valid. The command line parameters are invalid. The step failed.
Since it fails when you run it from your production server, regardless of whether you run it manually or from the job, it is probably related either to connectivity (can your production server connect to the smtp server), or it could be permissions related, if you are using some kind of proxy account on the server that is different from the one you use in your local BIDS.
Related
Recently, there is a host which indicates me the error message :
Get value from agent failed: cannot connect to [] interrupted system call
I do not understand what happens to it, this host uses an agent zabbix on the port 10050.
Except that on my 10 other hosts which are also with a zabbix agent there is no problem, it's really only on one that I have this problem.
I've tried to search on the web but nothing works.
Could it be a problem with the agent installed on the host?
I'm running SSRS 2016 on a local machine for development purposes. I've been running into this error quite frequently and spontaneously, as in I will run a report, then 3 minutes later try running the same report with the same parameters and all of a sudden my config is broken without changes. I start mucking around with the configs and eventually, seemingly spontaneously, again it will start working again. Then the cycle continues where it works for 1 hour - a few months before just breaking again.
Here is the screenshot from my Web Service URL:
The actual error message from the log is:
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: AuthzInitializeContextFromSid: Win32 error: 1355, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
When I google that error message I get a bunch of forum posts about sending emails and email configuration but I'm not trying to send emails nor do I have any email stuff configured.
Here is the configuration I'm using under Reporting Services Configuration Manager:
Service Account:
User Another Account (My Domain Account) I've also tried every combination of built-in account which also seem to work when the server doesn't throw this error..
Web Service URL:
IP Address: All Assigned
TCP Port: 80
HTTPS Cert: N/A
HHTPS Port: {blank}
Database:
My Local SQL Server instance and Report DBs using Windows Account login
Email Settings (all default settings):
Sender Address: {blank}
Current SMTP Delivery Method: Use SMTP Server (drop down is read only cannot be changed)
SMTP Server: {blank}
Authentication: No Authentication
Execution Account:
Specify an existing Account: unchecked
Subscription Settings:
Specify a file share account: unchecked
I've also restored and changed encryption keys numerous times and deleted all Encrypted Content under the Encryption Keys Pane. I always use the same snk file for the key and same password so I know it's correct.
If there's any additional information I can provide to help, please let me know. I know this is a bit of a longshot but it's really annoying and impedes my productivity developing SSRS reports.
Thanks in advance.
Well, after more googling, half way down the first page of results I finally came across this article:
https://support.microsoft.com/en-ca/help/3171505/fix-the-service-is-not-available-error-when-you-use-ssrs-2016-portal-a
I downloaded the suggested Cumulative Update 2 for SQL Server 2016 and low and behold, my local setup is working again. Could this be just a coincidence? Absolutely. I will report back if it dies again with the same error but I'm hopeful for the time being.
I am integrating Quickbooks using SSIS to pull data into our SQL Server Database. The SSIS works fine but the problem is when I run the package from the front-end application. It cannot run it as the credentials to access the Quickbooks API are different than the credentials used to log in on the front end.
I have tried changing the packages and project settings to "DontSaveSensitive" but this causes blank files to be downloaded as it leaves out the credentials for the HTTP Connection.
I tried setting up the proxy tab as well but either get a bad request error, invalid URL error or unable to connect to server error.
Issue was resolved.
The solution was to set the project protection level to "DontSaveSensitive" and then set up a variable for the server password.
In HTTP Connection properties, add an expression (ServerPassword) and set it equal to your new variable.
I'm working on a linux deployment project of an webdev's application.
This application is perfectly working on Windows.
But when I'm deploying it with the pcsoft's deployment tool on a linux server (PCSoft WebApplication Server), the server is looping, and I got a timeout message.
In the application, there is a screen where the user fill a form, to initialize the database's connection. When the user sends this form the server try to call the MySQL server, and it's at this moment, the server is looping.
And I don't have any log.
Can you help me ?
I wish to know if its possible to post process traps and events that zabbix server would have received from zabbix agents . I am hoping there is some configuration which I don't know of .
Since you don't give more details, my assumption will be that you want to do something in case of a certain event. Most probably a trigger. Like a service went down or there are too many open connections. These can be handled by using zabbix's Actions to intercept an event.
The following operation depends on what you have to do, it can be a remote command (executed on remote agent) or a script executed by server.
The remote command is a straight forward concept working OOTB. Just follow the manual and howtos.
Running something on the server isn't there, but you can trick zabbix to do just that by using custom alert scripts, which are just scripts launched by the server process. Then create a send message operation that uses your custom alert script and off you go.