I have a website working. I run it and i see localhost/pagename.aspx up and running. I replace it with my ip address and the port number like this .. ://10.xxx.xxx.xx:12234/pagename.aspx and it does not work. If I use 127.0.0.1,it works.The thing is this web site has an asmx web service. I need access to it. I disabled my firewall.I also added inbound and outbound rule for the port 12234. I allowed on both times. But still cannot see. What am I doing wrong?Is there any other way I can get access? (Some research told me to go to IIS and do some setting changes there. It was not that clear). More questions coming. Thanks.
I want you to follow this tutorial.
I will give you a few steps too.
Go to the iis manager and create a new application pool with the .net framework set to v4.0. Also note that the framework of the application/service that you are going to use is also the same framework.
Publish your web application/ service into a folder in you file system with publishing profile as "File System".
Copy the folder (that you just published) into C:\inetpub\wwwroot (which is the default folder).
Open iis manager and refresh the default site and the new folder that you just copied into the C:\inetpub\wwwroot folder will appear.
Right click that folder and click convert to application.
Right Click again and click -> manage application -> Advanced setting. Find and change the application pool from Default to the new pool that you just created.
Enable directory browsing which is on the middle pane.
On the left pane, click "rowse *:80 (http)"
the browser will open and you can see the application/service running.
http://localhost/something/ will be your default value on the address bar.
changing it to 192.168.1.85/something will also give you the same result. The same can be accessed from any computer in the same network with the ip address your system
192.168.1.85 was my system's ip address. run command prompt and type in ipconfig and you can find your ip address.
I did an installation of sitecore on one of a dev server and copied over the site root folder to a bunch of dev machines. This process worked fine on 6 of the 7 machines and we can see the sitecore login and content editor pages fine and browse to the site through IIS.
On one of the machines on browsing to site / sitecore in the browser we are not seeing any of the styles come through. After logging in same is the case with the content editor.
I did a comparison of the web config on the server and one of the dev machines with the machine which has the issue and cannot spot any differences. Also did a comparison of IIS settings for the site on with the server IIS settings and couldn't find any difference.
Anyone has any suggestions on what could be wrong or what can be done next to troubleshoot the issue?
Using sitecore 6.5 on windows 7 as the dev machine.
FIXED: Went to IIS->sites->SiteName. On the right under IIS, Authentication. Right click Anonymous Authentication, make sure it is enabled and change the anonymous user identity to Application pool identity. Recycle app pool. Should be all set.
Looks like the "Static Content" feature isn't enabled for IIS. You can check it in the "Turn Windows features on or off", "Internet Information Services", "Worlds Wide Web Services", "Common HTTP Features".
If the feature is installed, check the issue with Fiddler - look at the status code and content that all .css requests return.
After a Windows 7 fresh restart, I open the Visual Studio 2010 as administrator, create a new project of Windows Azure Project with ASP.NET Web Role, then at the WebRole1 project I add a WebService1.asmx and press F5 (run).
The Windows Azure services starts OK and the browser open the http:/127.0.0.1:8080/WebService1.asmx perfectly. But when I click at Invoke button to test the webservice method I always receive a Bad Request - Invalid Hostname, with a http:/127.0.0.1:8081/WebService1.asmx/HelloWorld.
The most likely cause is ASMX's WSDL file doesn't stand by load balanced environment such as Windows Azure. The test feature relies on WSDL. You will see similar issues if you add a web/service reference. It is recommended to upgrade to WCF. In WCF, you can use useRequestHeadersForMetadataAddress (http://msdn.microsoft.com/en-us/library/ee816894.aspx) to fix the issue. If you need to use ASMX, please try to manually provide a correct WSDL file.
created and deployed a Web service application in a virtual directory using IIS 6.1. The client application works fine on the same machine. But it is not working in another machine where the client application is copied manually. Can any one help what went wrong?
In Internet explorer, The XML file is displayed in the same machine. But from other machine, 'Un able to open the page' error occurs.
Suggestions please...
Regards,
Baskaran A.
Did you check your firewall settings? Can you open other pages that are served by the same IIS webserver?
My first 2 guesses would be:
1) Firewall settings, as previously mentioned.
2) The client app has a hard coded path in it somewhere that ought to be a relative path or, perhaps a URL. Something along the lines of 127.0.0.1 or localhost or C:\... within the app or in its configuration file(s).
Windows web server 2008 R2 64 bit, CF9 64 bit, IIS7, ISAPI extensions and filters and II6 metabase compatability installed. OS is on C default, and trying to install CF to D:
Testing IIS and it shows index.html correctly from c:\inetpub\wwwroot at http://localhost/index.html
Then I install CF to D:\ , single standard server licence, select run with all IIS sites, select C:\inetpub\wwwroot as the web root for administrator, and when it gets to the bit where it is supposed to open up administrator to complete the installation it opens up the browser with a 500 error.
Now when I go back to http://localhost/index.html I also get a 500 error, if i uninstall CF I can again reach the html page.
CFIDE has been installed in C:\inetpub\wwwroot presumably correctly. Can anyone tell me where I'm going wrong please.
Update
The exact IIS error is
HTTP Error 500.0 - Internal Server Error
The page cannot be displayed because an internal server error has occurred.
Module IsapiModule
Notification ExecuteRequestHandler
Handler AboMapperCustom-28262
Error Code 0x800700c1
Requested URL http://127.0.0.1:80/test.htm
Physical Path C:\inetpub\wwwroot\test.htm
Logon Method Anonymous
Logon User Anonymous
Resolves as below
There is a setting Enable 32-Bit Applications under Application Pool>Advanced settings. Set this to True and you will gain access to your CFIDE>Administrator page.
I would suggest first trying a restart. It is one of those things that after the fact sounds so obvious, but you never think of it. I know I have had problems with installing CF under IIS and had to restart the server to get it running.
I'm humiliated to admit it, but the problem was that what I thought was the cf9 64 bit installer, was the 32 bit one.
# Dave and # CfSimplicity many thanks for your help and in particular the IIS user account stuff was new learning for me.
Try checking the file system permissions for this folder:
D:\ColdFusion9\runtime\lib\wsconfig
The account that IIS uses needs Read, Execute and Modify permissions on this folder and below.
It might be because of two problems.
1) you haven't installed CGI, ISAPI extensions and ISAPI filters aren't installed yet in Web Server (IIS) of Server manager.
Window 2008 R2 with Coldfusion
2) you need to enable 32 bit application at IIS7.
Internal 500 error CF9 on Window 2008
I tried a different approach with my Windows 7 Home Premium - See http://coldfusioner.blogspot.com/2011/12/fix-number-1-installing-64-bit.html
It seems that I was successful by using the IIS Connector batch scripts manually and then to create a second default web site after installing the handlers. My article link above shows the steps I took - a very raw article and will likely be refined as I hear from others how they adapted my approach. The important thing is that this worked ;>) I hope it helps others...
The problem could be that your Application Pool that is part of your default website. It is possible to set it to run 32 bit applications. Try setting the Enable32bit to false in the defaultapppool of your IIS server, restart the app pool and your www service itself. Then try to use the ColdFusion wsconfig tool to add the IIS mapping. It should work even without the cf 9 updater 1 being installed on the server.
To avoid a 500 error when accessing the Administration console for the first time when installaing ColdFusion 9 on a Windows 2008 server with IIS 7.5 installed, include the "IIS_IUSRS" user group with "Full Control" to the \Lib\wsconfig folder in Enterprise server or \runtime\lib\wsconfig folder in Standard server. Before starting the ColdFusion install, make sure the "IIS 6 Management Compatibility" functions are installed, especially the "IIS 6 Metabase Compatibility" function.
Assuming that you use the default installation paths (C:\JRun4 for Enterprise or C:\ColdFusion9 for Standard), here is a step-by-step approach:
Begin the ColdFusion installer as an Administrator. At the completion of the initial installation process, but before accessing the online Administration console, do the following:
1.) At the Start Menu, select "Computer"
2.) In the Enterprise install, go to C:\JRun4\lib. For the Standard install, go to C:\ColdFusion9\runtime\lib.
3.) Right-click "wsconfig" and select "Properties" to open the wsconfig properties dialog box.
4.) Click the "Security" tab.
5.) Click "Edit" to change permissions for that folder.
6.) Click "Add..." to add a new user/group.
7.) Enter "IIS_IUSRS" in the Object name field and click OK to return to the Permissions dialog box.
8.) In the permissions dialog box, ensure that the "IIS_IUSRS" group is highlighted and click "Full Control" in the "Allow" column, then click "OK" to close the dialog box. Ensure that the permissions change will affect all files and folders under wsconfig.
9.) Click "OK" to close the wsconfig properties box.
Return to the ColdFusion installer wizard and continue the installation by clicking the open ColdFusion Administrator link. If the settings are correct, after a minute or two, a web browser with the ColdFusion Administrator Console should appear so you can complete the installation.