Ive programmed an Xbap Application and published it to Windows XP computer without any problem. Now I want to publish the Xbap application to a Computer running Windows Server 2003. I do'nt get any failure when I´m publish the application, but when I try to browse the application I got failure and I cant browse the application.
When i try to run http://localhost/MyApp/setup.exe, It says that the file could not be found...
I there someting else I have to do when publish to a Windows Server 2003 Computer compared to Windows XP
Its seems like the problem here was the MIME Types in IIS. By register the followign MIME Types in IIS solved my problem:
.manifest application/manifest
.xaml application/xaml+xml
.application application/x-ms-application
.xbap application/x-ms-xbap
.deploy application/octet-stream
.xps application/vnd.ms-xpsdocument
For more information how to do this, see:
http://msdn.microsoft.com/en-us/library/ms752346.aspx#content_expiration
List item
Related
I have two machines: Windows 10 Pro, and Windows 10 Home. I have enabled IIS on both of them. From both machines, going to IIS -> File -> About shows this dialog:
One might assume that I'm dealing with the full version of IIS simply due to the lack of the word "Express".
Is there any simple way to confirm if a machine has full or express installed?
IIS Express is normally installed into your 32-bit Program Files folder. So, to see if it's there you can try:
C:\>cd "\Program Files (x86)\IIS Express"
C:\Program Files (x86)\IIS Express>iisexpress /?
Full IIS is normally installed as a service called "World Wide Web Publishing Service" or "w3svc" for short. So, to see if it's there you can try:
C:\>net start w3svc
You opened IIS Manager to see such a dialog and IIS Manager is only part of full IIS, while IIS is part of Windows.
If you want to check that in code, then there are other ways such as checking Windows CBS data, or reading registry key.
IIS Express is completely another software, which is an MSI package to be installed either with Visual Studio or individually. To test its installation, you either check the Programs dialogue as the comment said, or query MSI data or registry keys.
If you have IIS manager installed, you have full IIS.
IIS Express is part of Visual Studio and appears in the Windows system tray when you run a web application/web site from within Visual Studio.
I have an IIS installed on my machine. When I try to run my asp file, it gives me Active Server Pages error 'ASP 0221' The specified 'page aspcompat="true" ' option is unknown or invalid.
I run the same app from visual studio 2005 and it works fine. I don't know why it is not running from IIS. I have to deploy this up in a remote server and run it from local.I have allowed active server pages to run on the IIS on web service extensions.
Other ASP websites seems to run fine except this website I am working now. I don't why it is complaining about this directive.
The reason is some old ODBC connection will not work if I remove this asp directive 'page aspcompat="true"
Please Help..
Thanks
I'm using visual studio 2012 and i have a windows form app. the iis express server is configured by default with visual studio 2012.
I have to publish my windows form app. For that, i have create a storege object on azure platform.
But when i try to publish the project using clickonce i have that issue :
Error 83 The Web server does not appear to have FrontPage Server Extensions installed. If FrontPage Server Extensions are installed, this error can occur because the _vti_bin virtual directory is not marked as executable. To correct this problem, run Internet Information Services Manager, select the Web server that has the problem, and then use the Check Server Extensions command.
Screen shot :
https://docs.google.com/file/d/0B-aV0dsLT4CaemZuQV93Ymt4UVE/edit?usp=sharing
I had no issue during the creation of my storage object on azure, and the URL is good !
I have installed de FrontPage Server Extension several times and normally it's good.
i really need to publish my project, if someone can help me ...
Thanks for help.
You are trying to do HTTP publish to a server that doesn't have FPSE installed. FPSE was no longer available after Server 2008 (I'm guessing here, I just know it's not available for newer versions of Windows Server).
Instead of doing HTTP, use FTP. So you FTP the files to the web server, and use an HTTP link for the customer to access them.
For example, your publishing file location might be
ftp://myserver.com/myfolder/
and your installation URL would be something like
http://myserver/thefolder/
We're in the process of moving from 2003 IIS6 Web servers to 2008 R2 with IIS 7.5.
We also have a Windows 2008 server running IIS7 and everything works fine on this server.
On the new servers when we go to our crystal reports viewer page we get prompted for windows authentication, then if you type in valid credentials or not you get the following error in firefox:
XML Parsing Error: no element found
Location: http://192.168.10.112/Reports/ReportViewer.aspx?id=49
Line Number 1, Column 1:
^
In IE you just get a blank screen.
The same code runs fine in debug mode on the server in Visual Studio 2010, and works fine on our other servers
Thanks
I know that the answer is too late, but to be a reference for other users.
I faced this problem too in IIS 7.5, and after 5 days investigation, I found that the problem is because the Crystal Reports Viewer running as 32-bit, to solve this issue:
in IIS, go to Application Pools
Select pool that you are using it for your application, normally its "ASP.Net v4.0".
Click on "Advanced Setting..." in the right panel.
set the value "Enable 32-bit Application" to "True"
Also, note that you have to install the oracle client 32-bit version too.
I'm using IIS 7.5 on Windows Server 2008 R2 x64 Enterprise Edition. In the project we have developed with ASP.NET 4.0 we used WCF Service. But it doesn't run over domain when the software is running from local computer. Otherwise, I am getting the following error:
HTTP Error 404.3-Not Found
The page you are requesting cannot be served because of the extension
configuration. If the page is script, add a handler. If the file should
be downloaded, add a MIME map.
You should install IIS sub components from
Control Panel -> Programs and Features -> Turn Windows features on or off
Internet Information Services has subsection World Wide Web Services / Application Development Features
There you must check ASP.NET (.NET Extensibility, ISAPI Extensions, ISAPI Filters will be selected automatically). Double check that specific versions are checked. Under Windows Server 2012 R2, these options are split into 4 & 4.5.
Run from cmd:
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir
Finally check in IIS manager, that your application uses application pool with .NET framework version v4.0.
Also, look at this answer.
In my case, along with Mekanik's suggestions, I was receiving this error in Windows Server 2012 and I had to tick "HTTP Activation" in "Add Role Services".
In windows server 2012, even after installing asp.net you might run into this issue.
Check for "Http activation" feature. This feature is present under Web services as well.
Make sure you add the above and everything should be awesome for you !!!
I was having trouble accessing wcf service hosted locally in IIS. Running aspnet_regiis.exe -i wasn't working.
However, I fortunately came across the following:
Rahul's blog
which informs that servicemodelreg also needs to be run:
Run Visual Studio 2008 Command Prompt as “Administrator”.
Navigate to C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation.
Run this command servicemodelreg –i.