I have a Windows XP running under Virtual PC, but I think that this doesn't matter since IIS6 theoretically should behave the same as on usual Windows XP.
The problem is that Metabase.xml doesn't exist. Why? :(
I've mixed that up: WinXP has IIS6, not IIS5.1.
Related
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.
well, according to what I've found googling around, it's imposible... (maybe with with windows xp 64...)
but I thought that maybe someone could find a way to achieve it, or at least some workaround...
http://www.iisanswers.com/IISFAQ.htm
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.inetserver.iis&tid=14654991-875f-4cc6-a853-7e9f3bb96bc3&cat=en&lang=en&cr=&sloc=en-us&m=1&p=1
--
ps: I need to debug classic asp code, and my production environment is windows 2003, while my development machine is windows xp...
--
edit:
just to clarify, I can already debug classic asp code in iis 5 with vs 2003 and 2008, it's just that I stumbled upon a (very silly) bug that only appeared on iis 6 (when IIS 5 received and empty http status, it just assumed 200, while iis 6 kept asking for my credentials in an infinite loop, it was very silly in deed, but took me a lot of time -and cursing- to discover it)
IIS 6 cannot be installed on Win XP. However, debugging classic ASP code is possible on Windows XP / IIS 5.1 using Visual Studio 2003 and up. You will need to configure IIS 5.1 to "enable ASP server-side debugging" (disabled by default):
IIS settings http://www.freeimagehosting.net/uploads/f1a6f781b9.png
Here is a more detailed article on how to debug classic ASP pages in Visual Studio - link
(NOTE: When running on XP Pro/IIS 5, you need to attach to dllhost.exe instead of w3wp.exe)
You posting in your 2nd link is correct. And read the faq. That spells out why it can't be done.
One option you can do is have a virtual machine of Server 2003 running on your laptop.
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)