No Application Named from jadehttp.dll

[ghosttie]

I'm moving an old jadehttp WebServices application to a new server on a customer site and on the new server I'm getting

No Application Named
The URL must include the Application name as a parameter.

even though I'm using a valid URL that does have the application name in it

I think it must be a problem with the configuration somewhere (the only thing that should have changed is the server name) but I can't think what misconfiguration could be causing this or how to get more information from jadehttp about what the problem is.

It's not logging anything in the \appname_jadehttp\logs\ folder or in jommsg, IIS request tracing doesn't tell me anything I don't already know...

[allistar]

Is there a web.config file for the URL? Do you have any rewrite rules set up? We set up rewrite rules so we can hide the application name (and so there isn't a .dll in the URL). Rewrite rules could explain what you're seeing.

[ghosttie]

Thanks - I found the problem - the application pool didn't have permission to the _jadehttp folder so jadehttp.dll couldn't read the ini