I am currently developing an application that uses the facebook api to get the posts from my feed.
I tested it locally using Visual Studio 2013 and it works just fine !
But when I publish it at IIS 7 it doesnt work.. it throws an exception while invoking the method Get of Facebook Client.
This is the error:
Exception Message: Unable to connect to the remote server
StackTrace of exception:
at Facebook.HttpHelper.OpenRead()
at Facebook.FacebookClient.Api(HttpMethod httpMethod, String path, Object parameters, Type resultType)
at Facebook.FacebookClient.Get(String path, Object parameters, Type resultType)
at FacebookProxy.WebUI.Default.LoadPosts(ControlCollection container, String upperPostId)
Maybe I need some special configuration on the IIS?
Thanks alot in advance
EDIT: I managed to attach the process to debug while launching the website from the IIS, and this was the inner exception message:
Inner Exception: No connection could be made because the target machine actively refused it 31.13.64.113:443
This only occurs while launching from my local IIS why? I already disabled all Firewall
solved, error on proxy. I need to open port at my network
Related
I recently installed IBM MDM 11.5, DB2 and IBM WebSphere on my system. For some reason the Asset in MDM-operational-server is stopped and isn't getting started. I'm new to this and don't know what is causing the problem.
Business-level applications
MDM-operational-server-EBA-E001
If anything is required from my side then please let me know.
I tried restarting the server multiple times, tried running 'Madconfig redeploy_EBA' and even reinstalled the whole thing again but still after completion it's in the same state. If tried to execute any OOTB transactions, it's throwing the following error:
Error: Service bean could not be looked up on server iiop://localhost:2809 and provider url com/dwl/base/requestHandler/beans/DWLServiceController
com.ibm.mdm.tools.metadata.common.exceptions.MetadataException: javax.naming.NameNotFoundException: Context: INLEN8520069636Node01Cell/nodes/INLEN8520069636Node01/servers/server1, name: com/dwl/base/requestHandler/beans/DWLServiceController: First component in name requestHandler/beans/DWLServiceController not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
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
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!
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¶meter1=401¶meter2=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.
When running a webservice, web page that knows how to respond. The service connects to a dbase. During the sqlconnection.open call, ASP .NET code throws the following exception:
sqlConnection.ServerVersion' threw an exception of type 'System.InvalidOperationException'
NOTE: I'm running this on my dev machine. When it runs on live web server, all is well. It is unique to my system.
I'm I missing a configuration setting with Sql Server 2008?
NOTE: recently upgraded from Sql Server 2005 to 2008
This could possibly be caused by a difference in your web.config between the live server and your dev machine. Have you checked that the connection string is properly specified?
Found problem. There was a space in the front of the connection string.