I am currently working in a Windows Server 2008 R2 enviroment with IIS and sharepoint installed.
I have installed Application Request Routing(ARR) onto the IIS server and it installs some xml files into "%windir%\system32\inetsrv\config\schema"
I have a UAT and DR environment and it seems that in the UAT environment it is working well but once in the DR, every few hours, the files in that folder will reset to its original state before ARR was installed.
Could anyone shed some light as to why such a problem would happen? Or maybe why does IIS reset its state at all?
[RESOLVED]
Seems like there was a scheduled task that deleted all .xml files on "%windir%\system32" but not all were deleted as there was different permission on it in "%windir%\system32\inetsrv\config\schema" and the scheduled task was unable to delete it.
Related
My complete CICD pipeline is fine. But once the release is completed the test website is inaccessible reason why. In IIS under Basic settings the physical path changes automatically. After every release i have to manually set so iis serves where the contents of release are. Am i missing something in IIS configuration.
***The blacked out is the folder path. After every release it resets to C:\inetpub\wwwroot
Help please this is the only thing that frustrating me. Thanks in advance
Azure release set up webpage error IIS Physical path
After every release it resets to C:\inetpub\wwwroot
The root cause of this issue is the settings(Physical path) in the IIS web app manage task.
This task is used to configure the IIS website. If you set its value to %SystemDrive%\inetpub\wwwroot, it will reset the value to C:\inetpub\wwwroot every time you run release.
To solve this issue, you can change the physical path to the value you expect.
For example:
Here is the doc about IIS web app manage task.
I know this is a long shot but I'm going to ask anyway.
I have a project I'm working on for a company that hosts their application from a server running Microsoft Server 2012. I've found the folder where the web app's files are stored and I want to deploy my own version with updated code - would I just replace those files and restart the server to deploy? (after backing that folder up, of course)
This is super out of my wheelhouse as I've only used Github, Heroku, etc for deploying applications. Please let me know if I need to provide any more information to help you help me.
Thanks in advance!
you host multiple websites on the same server. Use IIS to point to another website and start it on a different port number for your web app. Let me know if this isn't clear enough
If you only update HTML, CSS, JS these files, it will be updated after you restart the iis server, but if you change the cs file code you need to rebuild the project and republish it or just copy the bin folder.
I updated a ASP.NET CORE/ASP.NET 5 RC1 controller cs file with a programming change.
The site has previously been deployed on production on IIS7.5 Windows 2012 Server which makes use of HTTPPlatformHandler installed in IIS.
This is a remote server I have to access via VPN.
The site is setup as an application in IIS and the folder points to the wwwroot directory of the deployed site.
I deploy it currently by deploying it first locally by right clicking on my project in Visual Studio 2015 and selecting publish to local folder. I then copy the contents of the local folder to the remote network IIS7.5 web server site folder.
If I copy for example the appsettings.json or a changed .cs file to the server, the change will not reflect.
If I copy the whole site to the production server I get folders and files in use messages. I have to kill the 'dnx' process in order to copy without getting these messages.
From my understanding if I kill the process dnx it will force a recompile. This is currently the only way I know of to restart the site after updating it but I imagine it is not the best way.
What is the standard practice to restart your website after you update your production sites that run ASP.NET5 RC1?
Also changing my app.settings json file aslo doesn't trigger a site reload like changing the web.config did in ASP.NET 4 so being able to restart a site is important.
If I have multiple sites on the same app pool and I only want to update one in production. How can I only restart the one site to reflect the latest changes?
Is it possibly to restart the website to reflect the change as updating it directly doesn't cause a recompile taking into consideration if I only have access to a shared folder and not the web server itself?
With IISPlatformHandler, DNX process is started by IIS (instructions are in wwwroot\web.config).
IIS knows nothing about your source files, all requests are forwarded to DNX.
DNX does NOT watch source files for changes, because there is no dnx-watch there.
IIS only watches for wwwroot\web.config file changes, so you need to change/edit/touch it to force IIS to restart website (and DNX process).
I use msdeploy to deploy, it has commands to stop and start app pools, using these commands has resolved my file in use errors. There are lots of ways to use msdeploy, below is how I happen to be using it.
msdeploy -verb:sync -source:recycleApp -dest:recycleApp="site/pool",recycleMode="StopAppPool",computername=COMPUTERNAME
msdeploy -source:contentPath='SOURCE PATH' -dest:contentPath='\\COMPUTERNAME\wwwroot\' -verb:sync -retryAttempts:2 -disablerule:BackupRule
msdeploy -verb:sync -source:recycleApp -dest:recycleApp="site/pool",recycleMode="StartAppPool",computername=COMPUTERNAME
We have an ASPNet5 site (angular site and webapi service) running under IIS 8.5 successfully. The issue we have now run into is dnx holding locks on files that prevent us from re-deploying the site from our automated deployment server. The task is simply using robocopy to perform the task but I can reproduce with a simple copy as well. Essentially, the error is "process cannot access the file xxxx because it is being used". The files in question are mostly under the approot/packages dir.
The question is how to work around this. The main goal being able to re-deploy without having to bring down the site which seems impractical.
We are running on Win2012R2, IIS8.5 and clr rc1-update1.
Thanks for your help in advance.
I got a backup of a Sharepoint 2010 site that I created from our client's production server so that I can make some new changes to it on my staging server.
I can restore the site collection from the backup without a problem but when I try to create a backup of the same site on my staging server, I always get the error "Operation is not valid due to the current state of the object".
Before the error is given however, a small part of the backup file is created. If I try to run the Backup-SPSite again, it always fails at the same point and the corrupt backup files are always the same size.
Going through the logs it looks like the problem might be related to user permissions. I wonder if it's possible that the user permissions, user data, etc that came over from the client's production server are somehow screwing the backup process now because the same data cannot be found on my staging server.
The same error is mentioned here http://technet.microsoft.com/en-us/library/ee748617.aspx but UseSqlSnapshot parameter doesn't work anyway in my case.
I've been hitting my head against the wall with this problem and would appreciate if anyone has any advice on what might help! :)
The setup:
Windows Server 2008 R2
Sharepoint 2010 Server (no SP1 because it hasn't been installed on the client's production server)
Microsoft SQL Server Express Edition
Cheers!
The backup process started working after I checked in a file that had been checked out by a user on my client's production server.
I found out what file that was by opening the corrupted backup file and looking at the title of the last entry.