I am getting the above error message in production when trying to call the AddImageUrl section of ABCPdf (version 10). This started occurring yesterday just after midday my hosting provider assures me nothing has changed I am the only developer on the project as was working on something else entirely.
The URL provided in the stack trace can be accessed in IE on the web server without any error messages (including SSL). There is also a UAT environment on the same web server in which the PDF works, the UAT environment is identical in code and application pool settings, the only difference is the web address and database.
The HTML the PDF is calling can take a little time to come up on first load. Given that data is different I have increased the timeout from 15 seconds to 2 minutes.
I have arranged a reboot to see if that fixes it, but I have run out of things to check.
Edit: I did think of one further check, could I add the image of a page not on the site (https://www.google.co.uk/), doing this resulted in the same error so it appears not to be a blocking issue on the worker process.
—
Edit2: switched to the gecko engine and it is now working.
You can sometimes get this error if the web browser within Abcpdf cant access the URL.
On the webserver add the URLs directly to the local machine hosts file
C:\Windows\System32\drivers\etc\hosts
The entry should look something like this
127.0.0.1 example.com
Related
I have three mvc 3 web applications in a single web role on Azure Cloud Services. All of a sudden this morning both the single instance in production and in staging give "HTTP Error 503. The service is unavailable." when navigated to in a browser.
I rebooted the production instance but nothing changed. Then I deployed a remote desktop enabled version to the staging instance and logged in. However, strangely when I navigate to the web applications in a browser inside the remoted staging instance everything works.
Looking at IIS server logs it seems there are some issues starting the roles (warning level about the appPoolId being incorrect) but obviously the roles are starting as they are accessible from inside the staging server.
The World Wide Web Publishing service is also running and even after restarting this service the web application is not accessible externally.
Does anyone have an explaination for why the sites are accessible locally but not remotely that would help me debug this issue?
I found out where the issue came from, the bindings that were configured in IIS7 did not include bindings for the actual [abc].cloudapp.net host headers.
I assume that for some reason since some time last night or this weekend the requests seem to come with those headers instead of the original headers for the website. This is really strange but adding these bindings fixed both the staging and production instances and they were available again after this change.
I've done this many times in the past, but this is new, and I think CF11 is the problem. Not sure.
Fresh Windows Server 2012.. installed CF11. Selected "Configure All IIS Websites" during install. There's only two sites configured in IIS -- Default, and one other, which has its own name (test.mydomain.com) configured in the hosts file and in DNS. In its webroot is a single index.cfm file, and a subdirectory thereof, is an actual ColdFusion web app.
When I browse to the webroot, I get a standard Microsoft IIS page, rather than the index.cfm file. If I browse to the subdirectory, I get 404.
I've set index.cfm as the default document.
The path specified to the webroot is correct.
If I run the wsproxyconfig.exe file, it shows nothing is configured. I click Add, select IIS. In the drop-down where you configure a specific site, it says None and is not selectable. If I try to add, I get the error, "Unable to configure WebSocket Proxy Enable the required WebSocket Protocol option in IIS." I've looked all over IIS and can't find where this setting might be.
What's interesting is I can get the cfadmin page to load and function just fine (127.0.0.1/cfide/administrator)... there are no port numbers in that URL so it must be passing through IIS. So I'm not really sure what the problem is. Is it the connector? Is it something else? I'm stumped.
I'm currently running MAMP Pro (osX 10.9.4) with several different virtual servers on my local machine, one for each of my client's projects. I've been trying to connect to the Google API use OAuth and have everything working just fine when 'REDIRECT URIS' is set to:
http://localhost:8888
However, as mentioned I've got several of these servers running,
e.g. 'https://clientname1:8890' or 'https://clientname2:8890'
Whenever I enter those into the API console I just get a 'Whoops' message telling me something has gone wrong Google's end:
"Server Error: Whoops! Our bad."
It seems as though only 'localhost' is allowed via the API for local testing, is there anyway I can set it up so I can test off any of my local servers?
I had to add my localhost to the allowed referrers list to test locally. Without that inclusion, I get 403 Forbidden errors. You probably just need to add clientname1 and clientname2 or clientname1:8890 and clientname2:8890 to the allowed referrers list in the Google Developers Console. Mine's set under public api access, so maybe it's going to be another problem for you depending what API you're using and how you're using it. Hope it helps -
I'm currently trying to install web api project directly from vs 2013 to my local dev machine, but when I test one of my http get controllers, I get the following:
My url looks like this:
http://localhost:8081/api/Location/States?queryTerm=Ark
When I test this on my local, this url works and I get my json response.
pay no attention to the web config error in the background. If I enter anything invalid, I get an IIS error, so I know I'm hitting the right URL.
Side note: I'm using IE8 for testing.
I found out the solution, and it may be a config thing, but when I made this as an virtual application to a website, this went away, and it gave me a yellow sign of death (which is a good thing). I was able to deduce this to be an oracle issue, where it couldn't find the database connection, and then found out it couldn't resolve tns names.
So I guess Web API can not be hosted by itself on IIS? I haven't looked into it, but it seems this to be the case, unless there needs to be more tweaking involved.
i know too late for response. But i get same error when I try deploy Odata v4 Application in IIS server.
In server , i hit this error as above, i try everything config but nothing change.
At last, i try connect from client and it work.
I recognize that in Client , it download a json file from Server (in case use Odata , it seem like wsdl file in webservice) and API still work well.
For some reason, it cant download in server, but dont worry, it still work.
Hope this helps!
I am attempting to setup a remote profiling session with a server. I have downloaded the latest version of Zend Debugger, and have installed it on the server with the following setup - http://puu.sh/3ezyh/39247f2f15.png . With my local machine, I have setup a putty session to the remote server, and forwarded port 10137 as per the KB article listed on zend.com.
I am able to debug the remote server without a problem, however when I goto profile the page, the page will process, then a dialog will pop up with a "Waiting for the debugger's response" message. After approximately ~20 seconds, I get the following error: http://puu.sh/3ezDk/57f6dc1bb5.png .
However, there will be profiling information displayed , as well as execution statistics, but no execution flow, almost like it's getting part of the data but not all of it.
The page in question does have anywhere from a 20-30 second page load (which is why I'm tyring to profile to find the problem.)
The only error I can find is in the server's error_log, which just says "[Zend Debugger] Cannot send message"
Is there anyway to diagnose why I'm not getting the complete response?
I wonder if it is getting your IP address and trying to send directly to it instead of over the local forwarded connection. You might need to set your host IP to 127.0.0.1 as the address like in http://screencast.com/t/7lheaOlx. If that doesn't work I would say do a
tcpdump port 10137
And see what you can see. Also, depending on your local OS you may have a firewall blocking access to your instance of Studio.