Skip to main content
A
Anonymous
March 27, 2013
Question

ColdFusion 10 web services fail in IIS virtual folders

  • March 27, 2013
  • 4 replies
  • 6256 views

We started testing the migration of one of our main websites from CF9 to CF10 and everything seemed to be going well.  When we started testing our web services though things got a little weird.  All of our web services were throwing error messages.  Both installations co-exist on the same Windows 2008 R2 server running inside of the same instance of IIS.

wsVersion = 1

AXIS error
Sorry, something seems to have gone wrong... here are the details:
Fault - Error attempting to create Java skeleton for CFC web service.; nested exception is: coldfusion.xml.rpc.CFCInvocationException: [java.lang.NullPointerException : null]
 AxisFault 
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException 
faultSubcode: 
faultString: Error attempting to create Java skeleton for CFC web service.; nested exception is: coldfusion.xml.rpc.CFCInvocationException: [java.lang.NullPointerException : null] 
faultActor: 
faultNode: 
faultDetail: {http://xml.apache.org/axis/}hostname:Dev

wsVersion = 2

HTTP Status 500 - The web service operation caused an invocation exception.
type Status report
message The web service operation caused an invocation exception.
description The server encountered an internal error (The web service operation caused an invocation exception.) that prevented it from fulfilling this request.
Apache Tomcat/7.0.23

Long story short of the hours I spent debugging I discovered that if the web service files were located within an IIS virtual folder this happens.  If I move them to the root of the website or a folder inside of the website they begin to work again.  This behavior is inconsistent with CF8 & CF9 as our websites in development and production under those are running their web services from an IIS virtual folder.

Anyone have an explanation, fix, or work around relating to this?

This topic has been closed for replies.

4 replies

A
Anonymous
May 17, 2013

Adobe has verified the bug and marked it as ToFix so we should hopefully see a fix coming.

A
Anonymous
April 18, 2013

For those who have replicated the issue can you please go to my bug I've posted regarding this and Vote it up?  Without votes the bug will go unnoticed by Adobe staff.  The vote option is in the bottom right hand of the bug page.

https://bugbase.adobe.com/index.cfm?event=bug&id=3531653

S
shige.
Participating Frequently
April 9, 2013

I also have the same problem, I got workaround the problem by setting a ColdFusion mapping as same as IIS virtual Directory (and Restart ColdFusion service).

A
Anonymous
April 10, 2013

I'll give that a try and see if it works for our system too.

A
Anonymous
March 28, 2013

I've filed a bug relating to this as I've now reproduced this on 3 systems.

https://bugbase.adobe.com/index.cfm?event=bug&id=3531653

Charlie Arehart
Community Expert
Charlie ArehartCommunity Expert
Community Expert
April 3, 2013

Leith, while you say in the bug report that these 3 servers are “fully patched”, it’s important to confirm something that many overlook: can you confirm that you have rerun the CF web server configuration tool, to remove and re-add your IIS sites (whether “all sites” or some individual ones)? If you don’t, that can be the root cause for all kinds of problems.

To confirm it, look at the C:\ColdFusion10\config\wsconfig\1\ isapi_redirect.dll file to confirm that it’s dated Nov 8 2012. If it’s earlier, then you have not rerun the tool as needed. Note also that if you have created more than one connector, then you will have more than just a \1\ folder in that wsconfig folder, and you need to check each of those.

Let us know whether this is helpful or not.

/charlie

/Charlie (troubleshooter, carehart. org)
A
Anonymous
April 3, 2013

I have 2 connectors and both show as 11/8/2012 1:18 PM as their modified date.  I did not rebuild the connectors after CF10 P8 because it said if you had done it back during patch 6 there was no reason to do it again.  However connector #2 was built after P8 anyways and it's the same date as connector #1.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices