I have observed on Windows 2008 the Windows Error Reporting crash dumps get staged in the folder: C:\Users\All Users\Microsoft\Windows\WER\ReportQueue Which, starting with Windows Vista, is an alias for: C:\ProgramData\Microsoft\Windows\WER\ReportQueue
You actually just reminded me that I needed to fix this issue in an enviroment here. If your situation is the same as mine then it’s a simple fix. Just add the following to your web config: <system.webServer> <modules runAllManagedModulesForAllRequests=”true” /> Edit: To provide further explanation on the issue at hand. In my case what … Read more
The quick answer is User = System.Web.HttpContext.Current.User Ensure your web.config has the following authentication element. <configuration> <system.web> <authentication mode=”Windows” /> <authorization> <deny users=”?”/> </authorization> </system.web> </configuration> Further Reading: Recipe: Enabling Windows Authentication within an Intranet ASP.NET Web application
In powershell5 type: Install-Module CredentialManager -force Then New-StoredCredential -Target $url -Username $ENV:Username -Pass …. and later Get-StoredCredential -Target …. Source code for the module is https://github.com/davotronic5000/PowerShell_Credential_Manager == EDIT 2023 == Original is archived, install newer fork with: Install-Module -Name TUN.CredentialManager Check out Github repository for more details.
sc in PowerShell is Set-Content; so if you are running in PowerShell, you likely have a file called ‘delete’ with your service’s name as its content If this is indeed your issue, use sc.exe delete servicename
After some more extensive searching, I found the answer here: http://blogs.msdn.com/webdevelopertips/archive/2009/08/24/tip-93-did-you-know-php-and-custom-error-pages-configuration.aspx The solution is to manually edit your web.config file with this custom “httpErrors” entry: <?xml version=”1.0″ encoding=”UTF-8″?> <configuration> <system.webServer> <httpErrors existingResponse=”PassThrough” /> </system.webServer> </configuration> However, due to IIS 7.0 “lockdown” feature you might get a “This configuration section cannot be used at this path. … Read more
It turns out to get this application working under VBScript, I had to do two things. Run RegAsm.exe to register the DLLs. Run the C:\Windows\SysWOW64\cscript.exe to run my VBScript. If these don’t work, check out the other answer here about enabling 32-bit applications in IIS.
http://www.windowsnetworking.com/articles_tutorials/Configuring-IIS-7-command-line-Appcmdexe-Part1.html Put this into a file with .bat extension. @echo off appcmd start sites “site1” appcmd stop sites “site2” Update Just ensure that appcmd is available anywhere by adding %windir%\system32\inetsrv\ to the PATH environment variable of your system. Alternatively, you can use the full path to appcmd.exe in the batch file.
Create the task Right click on the task and “export” it Edit the task.xml file that you just exported You will find a line similar to <Priority>7</Priority> Change the value to a normal priority (between 4-6). A table of the potential values: TaskSettings.Priority property A value of 4 will have the same I/O and memory … Read more