Applicationhost.config not showing changes - iis

We have a webserver hosted in Microsoft Azure. It's a Windows Server 2008 R2 Datacenter edition, 64 bit.
For a website hosted on this machine, I need to make changes to the applicationhost.config file. However, changes I made to IIS recently are not shown in the config. I've added a new application pool and added this specific website to that application pool. I restarted the website, the 'Date Modified' of the file is updated, but the application pool is not present.
Right now I'm editing the file in C:\Windows\System32\inetsrv\config, but there's also one in C:\Windows\SysWOW64\inetsrv\Config, but the latter hasn't updated for months.
Am I looking at the wrong file? Are changes not saved right away? Do I need to restart IIS completely and not just the relevant website?

The real issue is that there are two inetsvr directories, one for 32 bits and another for 64 bits. The 32 bits 'version', probably dormant and not updated, is under SysWOW64 !!!
When you open a file on %SystemDrive%\Windows\System32\inetsrv using a 32bits application, Windows will redirect you, with no warning, to %SystemDrive%\Windows\SysWOW64\inetsrv possible a very obsolete file. Interesting no?
Using a 64bits editor like Notepad++ will open the 'right' active configuration file.
The following hack will make the (active) 64 bits location, accessible from 32 bits apps (for example, some Visual Studio versions).
cd /d "%SystemDrive%\Windows\SysWOW64\inetsrv"
move Config Config.OLD
mklink /d Config "%SystemDrive%\Windows\System32\inetsrv\Config"

The solution was to restart IIS as #RickStrahl mentioned, but even though it seems you can properly open and edit the applicationHost.config with Notepad++ or the Visual Studio installed on the server and configured to open .config files, it's not actually showing you the correct content!.
I installed Notepad2 x64 and then I could see the application pool I was looking for.
Bloody brilliant Microsoft... :[

Related

cannot read configuration file - updated

I am having the same issue as I've seen elsewhere but can no longer comment or reply - must be too old a post.
This happens only on my remote server running WIN2012, IIS 8.5 and on my brand new laptop, IIS 10.
I have been successful in running site on desktop WIN7, IIS 7.5 system only.
Seems it comes down to the computer's configuration. I needed to manually install IIS and other stuff on the WIN7 machine since none of it was there.
I don't believe the web.config file is the issue as you've stated, but something in the software installed is the problem.
Why can't this work cross platform? I am using the same folder paths. the "Test Settings" buttons may show errors, but sites other test sites still open (sites with an index file).
I have not found an answer and it's been weeks. If someone else can help it would be appreciated.

Attempting to install NuGet server on iis 10 on w2016 yields 404 not found error

My environment:
Windows 10 Creator (1703 with current updates to this date)
Visual Studio 2017, Enterprise, 15.3 with most of the goodies turned on.
Windows 2016, again with all current updates.
iis 10 with WebDeploy installed (that's a whole other installation nightmare, suffice it to say that SO helped there and the answers are already out there so I won't go into it here). Turned on ASP.NET 4.6, otherwise mainly accepted the defaults.
My process:
As per the NuGet.Server documentation, create a new ASP.NET MVC project using the "Empty" template and download and install NuGet.Server as specified. I'm using .NET 4.7 as my framework.
Compile and configure as desired (at least ensure you have an api key in place).
Deploy to iis using the "Publish" | Web Deploy option
Try to get in touch with the NuGet.Server on the website and fail miserably!
My bindings are 192.168.1.25 (yes, the server has a fixed IP address), port 80. The name of the site is AWENuGet and the desired url is www.awenuget.com.
To be sure, all of this works just fine if you take the same project as described above, assign a local port number (creating the project will do that anyway) and then simply running the application in Visual Studio works just fine.
But, when I took that self-same project and simply deployed it to iis, miserable failure.
I tried to open the host file (Windows\System 32\drivers\etc) and added the following:
192.168.1.25 www.awenuget.com
to said file and it still failed.
...and the answer, for me, was to take that same hosts file entry that I made on the server so that the server could see it and install it in my dev machine's hosts file and voila! NOW it works just fine.

How can I tell if I have IIS Express or Full version installed?

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.

(IIS8.5)Microsoft Excel cannot open or save any more documents

Microsoft Excel cannot open or save any more documents because there is not enough available memory or disk space. • To make more memory available, close workbooks or programs you no longer need. • To free disk space, delete files you no longer need from the disk you are saving to.
I am getting this error while opening an excel sheet in my application
Application is running fine on IIS5 and IIS7 but when I shifted it to Windows server 2012 R2 with IIS8.5 it didn't worked
I googled and found some solution but they also didn't worked.
Here is what I have tried
For both 32-bit and 64-bit versions of Windows, the folder “C:\Windows\System32\config
\systemprofile\desktop” must exist and you need Full Control permissions to the
“systemprofile” and “desktop” directories.
For 64-bit versions of Windows 7 or Server 2008 and higher, the “C:\Windows\SysWOW64
\config\systemprofile\desktop” folder must also exist and you need Full Control
permissions to the “systemprofile” and “desktop” directories.
For 64-bit versions of Windows Vista, the “C:\Windows\SysWOW \config\systemprofile
\desktop” folder must also exist and you need Full Control permissions to the
“systemprofile” and “desktop” directories.
For Windows 8.1, in addition to the above, the Windows Registry Key
[HKEY_Current_User\Softwware\Microsoft\Windows\CurrentVersion\Explorer\User Shell
Folders\Cache] must be set to C:\Windows\Temp
Finally found answer
On 64 bit system with 32 bit Office try this:
Start
Run
mmc -32
File
Add Remove Snap-in
Component Services
Add
OK
Console Root
Component Services
Computers
My Computer
DCOM Config
Microsoft Excel Application
after finding excel application give it appropriate security clearance and you are good to go

Conversion to x64 platform in visual studio failing

So I built a huge website for my company using the AnyCpu option. I didn't think it would matter - I have a 64bit machine with x64 windows, it's getting deployed to a x64 server, and there's no attached dll's, so it should just all be in 64, right?
Well, in the process of trying to implement some security, the company's support told us the application MUST be strictly x64. I figured it was, but to humor them, I went into the configuration manager, and changed all the target cpu, platform etc settings to x64.
Unfortunately now, it breaks when I hit f5 to run it. I've run into this before, I think, and I vaguely remember needing to delete some temp internet files somewhere, but I tried closing VS, deleting the bin folder, deleting the root folder from /framework/tempASPfiles... but I still get the BadImageFormatException - "an attempt was made to load the program with an incorrect format."
What's the best and fastest way to convert an app to x64? and am I right in thinking I need to delete some files somewhere?

Resources