Hi Rick,

I am attempting to run my web service on a new cloud server. I have the web service up and running but when I use the interface to pass the parameters and click the invoke button I get an error:

System.IO.FileNotFoundException: Retrieving the COM class factory for component with CLSID {70F9B99C-BD3E-4A75-8A67-C1D4FAE53161} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).
   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at System.Activator.CreateInstance(Type type)
   at Westwind.Utilities.ReflectionUtils.CreateComInstance(String progId)
   at ITFWebService.ITFWebService.CreateObject(String progId) in c:\vfe2005\DEV\ITFWebService\ITFWebService\ITFWebService.asmx.cs:line 75
   at ITFWebService.ITFWebService.GetAccountBalance(String username, String password, String inmateId) in c:\vfe2005\DEV\ITFWebService\ITFWebService\ITFWebService.asmx.cs:line 30

Having a hard time figuring out where to start to resolve this issue. John Cook Bulletproof Software

The FoxPro COM Object is not properly registered on the server...

You need to register the component...

regsvr32 foxCom.dll 

+++ Rick ---

You are correct. I had modified the VFP app but had not put the latest version in place and then re-registered it.

Thank You Sir

Rick, I am trying to get the web service up and running on another server but this time I am getting an http error when I go to http://localhost/itfwebservice.asmx

Thank You, John

Make sure you have all the required ASP.NET components installed.

I have been checking the IIS installation for days. I have checked, double checked and triple checked. Finally this morning I removed IIS and re-added it to the server. Then I went thru the setting up of the web service and again thoroughly checking everything. No luck. Exactly the same error: HTTP Error 500.21 - Internal Server Error Handler "ASMX STA HANDLER" has a bad module "ManagedPipelineHandler" in its module list

I would be happy to hire you to connect to my machine. I will connect to the server and see if you can find the problem, if you are available. John

Please contact me privately if you want me to take a look at your server...

+++ Rick ---

Rick, When I go to my web service from the browser on the server (http://localhost/ITFWebService.asmx) that you and I worked on 2 days ago, it runs just like it should.

From my pc here in NC, when I go to my web service running on the server in Oklahoma (the very first installation of my web service) at http://173.195.29.14/ITFWebService.asmx it runs just like it should. Been running for several years.

From my pc here in NC, when I go to my web service running on the server that you and I worked on 2 days ago at http://63.142.89.84/ITFWebService.asmx I get the error This page can not be displayed so the web service in not being exposed to the internet or something like that. I looked at the windows firewall and it appears that is ok:

I am hoping this is something you are familiar with. If not, do I need to access the router that provides internet access? Not sure what to look for.

Thanks, john

Looks like the service is working now - I can reach it.

Generally IIS on port 80 doesn't need firewall rules set as it's automatically enabled, unless an admin has explicitly set to prevent those ports from being available.

If you can get to it locally but not externally then most likely the machine is not properly connected to the Internet or the routing in the network prohibits access. IOW, it's not a Web Server issue but a network config issue.

It's not working anymore and it looks like the server is not reachable even with a Ping operation.

+++ Rick ---

Are you trying to access http://63.142.89.84/ITFWebService.asmx

I can't reach it

Thanks

I could earlier but I can't anymore.

+++ Rick ---

Rick, I just wanted to let you know that you were correct in assuming there was another firewall blocking http traffic to the server. It was a hardware firewall that I was totally unaware had been installed. I contacted the provider and they setup a rule on the firewall to allow http traffic to be routed to the server.

Thanks, John