SSIS Redirect Request Failed Error - redirect

I have an SSIS package that calls an SSRS report hosted on a local server that produces a series of PDFs. It has been working perfectly for months, but all of the sudden I am now getting this error:
Error: 0xC001600B at SSIS_Package, Connection manager "ReportServer": The specified server, URL http://server/report&parameter1=401&parameter2=13&rs:Command=Render&rs:Format=PDF, has a redirect and the redirect request failed.
I have checked all my credentials in the package and on the server and everything is connected properly. I haven't been able to find anything at all about this error and I'm hoping someone out there has come across it!

It turned out to be a permissions error that was resolved by another user running the package.

Related

Powershell error with PnPOnline when trying to use ClientId and ClientSecret to connect to SharePoint Online

I am using PnPOnline to connect to SharePointOnline in order to publish files there from local network. I have installed PnpOnline and set up everything, but I'm getting this error when trying to simply connect (lol, stuck at the first step :( )
This is what I'm running. But when I run it, this is the error I'm getting:
As you can see I'm stuck in the first step. Anyone know what I'm doing wrong? How do I resolve this error?
Thanks!

AWS AmazonS3Client request returns error "The remote certificate is invalid according to the validation procedure"

We have an application using AWS SDK AmazonS3Client to communicate with the S3 service to get files downloaded. With thousands of instances running fine, however, we got a few sites getting the following exception error message:
The remote certificate is invalid according to the validation procedure.
The versions of the AmazonSDK.S3.dll and AmazonS3.Core.dll we're using are 3.3.102.18 and 3.3.103.1 respectively. These had been running for over a year without problems until recently.
Has anyone else experienced the similar issue? What could be the root cause of the problem? How do we resolve it?
Thanks!
This has been determined as an issue with proxy server loaded with incorrect certificate from the service provider. So, not really the application issue.

The remote name could not be resolved: '*****.sharepoint.com' in O365 Online Sharepoint in Powershell

I am uploading files from a specific drive in the host computer to a Sharepoint Site, for this I have used Microsoft.SharePoint.Client.dll & Microsoft.SharePoint.Client.Runtime.dll. Most of the times my script works fine, but at times I get the error:
"Failed to connect to SharePoint Online site: 'https://XXX.sharepoint.com/sites/XXX'"
"Exception Type: System.Management.Automation.MethodInvocationException"
"Exception Message: Exception calling ""ExecuteQuery"" with ""0"" argument(s): ""The remote name could not be resolved: 'XXX.sharepoint.com'"""
Any ideas of what might be causing the error and how I could prevent the script from crashing again?
Thank you!
As most of the times, the script works.
I assuming that it could be some network issue in your side.
Did you use some proxy in you side and can you access the site url in browser directly ?
I suggest you can trace the request using Fiddler to see if there is some detailed error message when executing the script:
Fiddler

NuGet gives me an error when accessing server

We have set up a small NuGet server in our corporate network. It works fine for EVRYONE except me ;-)
When I try to list the available packages in Visual Studio, all I get is this error message:
Unable to load the service index for source (...).
An error occurre while sending the request.
The remote server returned an error: (502) Bad Gateway.
I've been struggeling with this issue for hours without success. Can anyone give me a hint on why this error occurs?

Web Deploy not working. Timeout on client. Schannel 1203 on server

I'm trying to deploy an application via web deploy to a windows 2012 r2 server.
First tried installing iis, web deploy using the msi. After getting an unreachable error I saw somewhere that I needed wmsvc to be installed and installed it via powershell command Install-WindowsFeature Web-Mgmt-Service.
I stopped getting the unreachable error and started getting this error ->
Error: Could not complete the request to remote agent URL 'http://xx.x.xx.xx:8172/MSDEPLOYAGENTSERVICE'.
Error: The operation has timed out
On the server's event viewer under system I get the following error ->
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.
Any idea of what could be going on? Did I miss something on the installation?
After this I also tried installing everything but without iis and I get the same error.
So, this is really not a PoSH issue.
Maybe you should consider movin gthis question to another forum.
Anyway, you have either real server config issues (this can sometimes mean wipe and rebuild - very ugly option - but if it's a virtual machine and you have a snapshot, just roll back), or an app causing this.
Typically for Schannel type of error, it has to do with application or service in machine not able to complete any SSL connection sort of connection.
The error state parameter of 1203 means client error connecting to server, ie invalid ClientHello from the client
See if you can collect more data by...
https://support.microsoft.com/en-us/help/260729/how-to-enable-schannel-event-logging-in-iis
I realized this is an old question, but in case somebody ran into the same issue, here are my solution.
I had to follow this guidelines : https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-web-deploy-handler
Copy the resulting publishsetting file. In the Publish/Profile page import it.
In the Publish/Connection page, change the server to the server address with the 8172 port. Add the password. Change the Destination URL to the site to go to after the publish is completed.
Then after Validate connection was completed, go ahead and publish it!