I have a windows application that acts as a WCF Service that I developed on a 32bit Windows Server 2008 box. I have tested the application and everything works fine when running it from my development machine, as well as from my 32bit workstation. However, when attempting to run the application on a 64bit Windows 2008 Server, the application does not run, and a Windows Error Report is generated stating that the application stopped working. I have attempted to build the application on my 32bit Development Workstation, targeting both x86 and x64, to no avail. The only time I can get the application to run is if I comment out the code that starts the WCF Service. So my question is, do I need to dev and/or build this application on a 64bit workstation to allow the application to run on a 64bit machine?
Ok, I figured it out, nevermind...needed to run the app as admin on that server...
You need to configure http.sys to accept your urls using the httpcfg utility. There is a similar thing for Windows Server 2003.
How to add a URL ACL and avoid AddressAccessDeniedException in Windows Vista
Httpcfg Examples: Internet Information Services (IIS)
Related
I have created program using MSVC++ that besides it's main task calls WCF server functions. Under Windows 7 and Windows 8 everything works fine and I got several problems with Windows XP:
On some machines I have error that webservice.dll is missing and program doesn't starts. Why some Windows XP installations contain webservice.dll while others - not? How to install required dll?
On Win XP computers that has webservice.dll sometimes programm just crashes without any reporting. After recompiling program without WCF client code program runs fine. What might be starting point to look for the problem?
Windows Web Services API (WWSAPI) is an operating-system component of Windows 7 and Windows Server 2008 R2 or later versions of Microsoft Windows.
On Windows XP you need to package it with your app. The reason it works on some boxes is probably caused by one other installed application that uses that the WWSAPI as well.
The final version of the Windows Web Services API for Windows XP, Windows Vista, Windows Server 2003 and Windows Server 2008 is now available
In contrast to the past pre-released version of this API, this final version release can be used in production code and redistributed with the final versions of the product. Because of this, the final version is only available to companies who agree to terms of Windows Master Redistribution License Agreement (MRLA). To acquire the redistributable installers for this release and a copy of the Windows MRLA for review, please email a formal request.
Partially copied and adapted from Windows Core Networking blog, from Ari Pernick, dated Oct 9th, 2009.
I have two web based application. One of them is a WCF server application and the other is a client application and consume first application services.
When they are hosted in a Windows 8 machine's IIS they work good. But when they are hosted in Windows 8.1 they do not work. Client application shows a timeout error message.
Strange point is when client application in Windows 8 connects to server application in Windows 8.1 it works with no problem. If I connect Windows 8.1 client application of Windows 8 server application it works too.
Initially I guessed it may be related to IPv6 so tried to test several IP addresses like localhost, [::1] and many others. But nothing changed.
Now I guess Windows 8.1 has forbidden self WCF hosting (Client and Server in same machine). But have now idea how can I solve problem.
If I use WCFTesetClient in Windows 8 machine to test Windows 8 itself or Windows 8.1, both of them works.
I'm using WSHttpBinding. Both applications are ASP.NET MVC web applications hosted in IIS.
UPDATE:
Why both server and client are on same machine? Because this is a dev machine. In operational environment server and client are on separate machines.
I have a weird situation with WCF web service running on Win7 64 bit.
First the configuration:
.NET 3.5, WCF, web service compiled for x86, running as a console app (or Windows service, doesn't make any difference in this case).
I am using basicHttpBinding. I also have aspNetCompatibilityEnabled set to "true".
I have test clients written in C#, Java, PHP, and Ruby.
Now the issue:
Everything works just fine on XP Pro, Win7 32bit, Win server 2003, Win server 2008 R2 64 bit.
When I run on Win7 64 bit, everything installs fine and the web service starts up just fine. I can run the C# client against this service and it works. When I run Java, it errors out with "Can't connect".
Also, when I type in "http://localhost:55555/RmJobService.svc" in IE 8, it comes back with a blank page right away, suggesting a connection issue. Interestingly, when the web service isn't running, IE 8 takes a lot longer to come back with an error.
Since it works on Win server 2008 R2 64 bit, this doesn't seem to be a 32/64 bit issue.
It is strange that a C# sample can consume the service...
Any help would be greatly appreciated!
thanks!
daver
There is an option in IIS 7 app pool settings to "Enable 32-bit applications." This may help since you are compiling in x86 mode.
Have you enabled the metadata exchange endpoint?
I have installed IIS6 in my pc that have the OS in XP.
I have installed
- IIS6 Manager,
- IIS6 Resource Kit Tools
I can open:
Start>Control Panel>Administrative Tools>Internet Information Services (IIS6) Manager ,
But I cant add new site in IIS, I can't see the wwwroots site.
In the right click in Internet Information Services I can do only connect to one other pc.
Any ideas???
Thnax.
I have installed IIS6 in my pc that have the OS in XP.
I doubt it. IIS6 is part of Windows Server 2003. It doesn't run on vanilla XP, which uses IIS5.1.
I have installed - IIS6 Manager, - IIS6 Resource Kit Tools
That's not IIS6, that's only an interface to configure IIS6 installations on this or other machines. It is of no use to you. If you want to install IIS on an XP machine, as previously mentioned in your other question, you must have a copy of the XP Pro install CD.
But I cant add new site in IIS
You won't be able to add a new site even in a working IIS on XP. As XP is not a server OS, you will be limited to running a single web site, the ‘Default Web Site’ IIS comes configured with.
(There are script hacks you can run to add more sites if you must, but you can only actually serve one site at once.)
The Resource Kit Tools only include the manager that allows you to connect to OTHER computers running IIS. You will need to install IIS directly on the machine (it needs to be XP Pro as well - not home edition). See this link - it is fairly straighforward add/remove windows components.
http://www.learnthat.com/courses/computer/windowsxp/iis/
I'm trying to get EasyPrint to work from workstations running Windows Server
2003, connecting to a Server 2008 TS pool.
I noticed that there is a RDP 6.1 client for XP clients. I couldn't get that
to install on the Server 2003 box.
I was able to install RDP 6.0 client for Server 2003. However it appears
EasyPrint isn't actually working in this case, as we are seeing that printers
without local drivers are not being redirected to the remote desktop.
Information on the web on this topic is somewhat conflicting. Is what we
are trying possible? If yes. Any suggestions on how to get it to work
from a client on a Server 2003 workstation?
http://www.pubforum.info/welcome/BLOG/tabid/78/EntryID/6/Default.aspx
This will do is for you :-)
Kim
Terminal Server Easy Print Overview:
http://winplat.net/post/Terminal-Server-Easy-Print-Overview.aspx
Installing the XP version of 6.1 will work for 32-bit Server 2003, but it doesn't work for 64-bit versions of Windows 2003.