appcmd restore backup "bachupname" results in ERROR ( hresult:80070005, message:Command execution failed Access is denied)

[bswhipp]

Running CMD ad an admin so not sure why it is denied.

 

[ChatGPT]

The ERROR (hresult:80070005, message: Command execution failed Access is denied) from the appcmd restore backup command usually indicates permission issues, even though you’re running CMD as an administrator. This could happen due to:

1. Misconfigured Permissions on the backup directory or IIS configuration files.
2. IIS-related services not having sufficient access.
3. A corrupted IIS configuration or locked files preventing restoration.

Let’s fix this step by step.

---

Steps to Resolve Access Denied for appcmd restore backup​

Step 1: Verify Backup Directory Permissions​

The IIS backups are stored in the following location by default:

%windir%\System32\inetsrv\backup

1. Check Permissions on the Backup Folder:
   • Navigate to:
     

          C:\Windows\System32\inetsrv\backup

   • Right-click the folder, select Properties > Security tab.
   • Ensure the following accounts have Read/Write access:
     • Administrators
     • SYSTEM
2. Explicitly Grant Permissions if Needed:
   • Add your user account or Administrators manually:
     • Click Edit > Add... > Enter your admin username or Administrators.
     • Grant Full Control to the folder.

---

Step 2: Ensure Elevated Admin Privileges​

Even when running CMD as Admin, you may need to explicitly elevate permissions for the appcmd command.

1. Force elevated CMD mode:
   • Search for Command Prompt, right-click it, and select Run as Administrator (again).
2. Attempt the Command Again:
   

   bash
      appcmd restore backup "backupname"

---

Step 3: Verify that IIS Services Are Running​

If IIS services are stopped or misconfigured, appcmd might fail.

1. Check IIS service status:
   

   bash
      net start W3SVC
      net start WAS

2. If services are stopped, start them manually using the above commands.

---

Step 4: Bypass UAC (As a Test)​

Windows User Account Control (UAC) could interfere with permissions.

1. Temporarily disable UAC:
   • Open Control Panel > User Accounts > Change User Account Control Settings.
   • Lower the slider to Never notify.
   • Reboot the server (if prompted).
2. Retry the appcmd restore backup command:
   

   bash
      appcmd restore backup "backupname"

3. Re-enable UAC after testing.

---

Step 5: Confirm Integrity of the Backup​

If the backup files themselves are incomplete or corrupted, the restore may fail.

1. Inspect the Backup Folder:
   • Navigate to:
     

          C:\Windows\System32\inetsrv\backup\<backupname>

   • Ensure the backup folder contains the required files, including:
     • applicationHost.config
     • metaBase.xml (if IIS 6 compatibility is enabled).
2. If the Backup is Corrupt:
   • Try another backup file from the directory (test restoring a different backup using the same command).

---

Step 6: Run appcmd Restore via Safe Mode​

If permissions issues or file locking persist, boot into Safe Mode to minimize interference with files or services.

1. Reboot into Safe Mode:
   • On reboot, press F8 repeatedly (or Shift+F8).
   • Choose Safe Mode with Networking.
2. Restore Backup in Safe Mode:
   • Try the command again in Safe Mode:
     

     bash
          appcmd restore backup "backupname"

3. Reboot into normal mode once the restore is complete.

---

Step 7: Check System Logs for IIS Errors​

If the issue persists, error logs might reveal the underlying cause.

1. Open Event Viewer:
   • Check Windows Logs > System or Applications and Service Logs > IIS-Configuration for errors around the time of the failed restore.
2. Look for Specific Errors:
   • File locking, missing privileges, or mismatched metadata errors related to IIS or appcmd.

---

Step 8: Elevated Manual Restore​

If all else fails, you can restore the configuration manually.

1. Navigate to the backup folder:
   

      C:\Windows\System32\inetsrv\backup\<backupname>

2. Replace Current IIS Configuration:
   • Backup the current applicationHost.config:
     

          C:\Windows\System32\inetsrv\config\applicationHost.config

   • Replace it with the backed-up version from <backupname>.
3. Restart IIS:
   

   bash
      iisreset

---

Let Me Know!​

• Share any new output/error messages or results from the above steps, and I’ll assist further!
• We're close to resolving this!

 

[bswhipp]

When attempting to do iisreset I get
Attempting stop...
Restart attempt failed.
Access denied, you must be an administrator of the remote computer to use this
command. Either have your account added to the administrator local group of
the remote computer or to the domain administrator global group.

Ran cmd as administrator. User is and Enterprise Admin and is part of the Local administrators group.

 

[ChatGPT]

The Access Denied error when running iisreset, despite being an Enterprise Admin and part of the local Administrators group, typically occurs due to elevated permission mismatches, misconfigured UAC policies, or service-specific restrictions. Here's how you can resolve this and regain proper control over IIS.

---

Steps to Fix iisreset Access Denied and Permissions Issues​

---

Step 1: Force Elevated CMD​

Even though you ran the Command Prompt as Administrator, it’s possible it wasn’t fully elevated due to UAC or context issues.

1. Explicitly Run CMD as Administrator:
   • Press Win + S, search for Command Prompt, right-click it, and select Run as Administrator.
2. Ensure UAC is Not Blocking Elevated Access:
   • Open Control Panel > User Accounts > Change User Account Control settings.
   • Lower the slider to Never notify (temporarily).
   • Reboot if prompted and test again with:
     

     bash
          iisreset

---

Step 2: Verify Membership in the IIS Admin Group​

Certain IIS commands, such as iisreset, also depend on privileges specific to IIS Admin access.

1. Ensure the user account is added to the following Administrators local group:
   • Open Computer Management:
     

     bash
          compmgmt.msc

   • Navigate to:
     

          Local Users and Groups > Groups > Administrators

   • Confirm your user account is listed.
2. If IIS-specific permissions are needed:
   • Ensure the account has ownership and control over IIS directories:
     

          C:\Windows\System32\inetsrv
          C:\inetpub

---

Step 3: Add User to the IIS Admin Service Group​

The iisreset command interacts directly with the Windows Process Activation Service (WAS) and other IIS services. Permissions to control these services are sometimes bound to the IIS_IUSRS group.

1. Add your account to IIS_IUSRS:
   • Open Command Prompt as Administrator:
     

     bash
          net localgroup IIS_IUSRS <YourUsername> /add

2. Retry iisreset:
   

   bash
      iisreset

---

Step 4: Verify IIS Services Status​

If an IIS-related service (e.g., WAS, W3SVC) isn't starting or is misconfigured, iisreset might fail.

1. List the status of IIS-related services:
   

   bash
      net start

   • Check services like:
     • World Wide Web Publishing Service (W3SVC)
     • Windows Process Activation Service (WAS)
2. Manually start the required services:
   

   bash
      net start W3SVC
      net start WAS

3. Retry iisreset.

---

Step 5: Temporarily Disable Remote Permissions Enforcement​

If the server believes you’re running the command remotely (even on the local machine), there may be a misread context due to a security policy.

1. Temporarily disable remote restrictions:
   • Open Local Security Policy (secpol.msc).
   • Navigate to:
     

          Security Settings > Local Policies > Security Options

   • Locate:
     • User Account Control: Run all administrators in Admin Approval Mode.
     • User Account Control: Admin Approval Mode for the Built-in Administrator Account.
   • Disable both.
2. Reboot the server and retry iisreset.
3. Re-enable UAC after troubleshooting.

---

Step 6: Reset IIS Configuration​

Permissions issues may also arise from corrupt IIS configuration.

1. Backup Existing Configuration:
   • Navigate to:
     

          C:\Windows\System32\inetsrv\config

   • Copy and save the file applicationHost.config to a backup location.
2. Restore IIS Configuration:
   • Restore the IIS backup via:
     

     bash
          compmgmt.msc

     0

---

Step 7: Repair Windows Components​

Corruption in Windows services or components could prevent proper service startup.

1. Run Component Store Cleanup:
   

   bash
        compmgmt.msc

   1
2. Restart the server and retry the commands after completion.

---

Step 8: Check Event Viewer for Further Clues​

Review Windows logs for permission-related issues during iisreset.

1. Open Event Viewer (eventvwr.msc).
   • Navigate to:
     

     bash
          compmgmt.msc

     2
   • Look for errors or warnings related to IIS, WAS, or services.
2. Address any errors or failures logged.

---

If All Else Fails: Rebuild IIS Configuration​

If unresolved, IIS may require a clean slate:

1. Uninstall and Reinstall IIS:
   • Remove IIS:
     

     bash
          compmgmt.msc

     3
   • Reinstall IIS:
     

     bash
          compmgmt.msc

     4
2. Restore configuration from backups.

---

Let Me Know​

Test these steps (starting from UAC and permissions adjustments) and let me know how it goes! If iisreset or appcmd still fails, additional logs or error codes will help refine the solution.

 

[bswhipp]

I found this wiill work iisreset /stop /timeout:60 Issue with IIS 7

 

[ChatGPT]

That’s a great observation! Using the iisreset /stop /timeout:60 command is a workaround for IIS 7's known quirks where the standard iisreset command may hang or fail due to delayed stopping of dependent services such as WAS or W3SVC.
By explicitly adding the /timeout flag, the command waits appropriately for services to stop before reporting success or failure. IIS 7 sometimes times out prematurely, causing issues like errors or Access Denied.

---

Why /timeout:60 Works​

1. Extended Grace Period:
   • The timeout parameter gives additional time for services like Windows Process Activation Service (WAS), W3SVC, or custom app pools to gracefully stop.
   • Without /timeout, these services might still be shutting down when the system assumes failure.
2. Prevents "Access Denied":
   • Delayed services might interfere with stop/start operations when improperly terminated.
   • The added timeout clears processes locked by services.

---

Steps to Fully Resolve IIS Issues​

Now that iisreset /stop /timeout:60 works, here’s what you can do to ensure IIS runs smoothly moving forward:

---

Step 1: Verify IIS Service Behavior​

Check if all IIS services stop/start properly without further intervention.

1. List Running Services:
   

   bash
      net start

   • Look for:
     • W3SVC (World Wide Web Publishing Service)
     • WAS (Windows Process Activation Service)
2. Test Manually Stopping IIS:
   

   bash
      net stop W3SVC
      net stop WAS

3. Restart Services After Testing:
   

   bash
      net start WAS
      net start W3SVC

---

Step 2: Verify iisreset Command Timing​

If /timeout is still needed for iisreset, you can add it to your working process to ensure stability:

1. Stop IIS with Timeout:
   

   bash
      iisreset /stop /timeout:60

2. Start IIS:
   

   bash
      iisreset /start

3. Restart Entirely:
   

   bash
      iisreset /restart /timeout:60

---

Step 3: Check for Underlying Delays​

Long service shutdown/start times could be caused by resource contention or IIS configuration issues (e.g., application pool timeout settings).

1. Check Application Pool Behavior:
   • Open IIS Manager > Application Pools.
   • Look for app pools with Stopped or Error states.
   • Set all app pools to Recycle Automatically:
     • Right-click the application pool > Select Recycling... > Configure settings.
2. Investigate Event Viewer:
   • Open Event Viewer (eventvwr.msc).
   • Check Windows Logs > System or Applications and Service Logs > IIS-Configuration for errors.

---

Step 4: Cleanup Configuration if Needed​

If the above steps indicate lingering issues, clean and refresh IIS:

1. Run DISM to repair system components:
   

   bash
      dism /online /cleanup-image /restorehealth

2. Test configuration restore for IIS backups using:
   

   bash
      appcmd restore backup "backupname"

---

Let me know if the solution fully resolved the issue or if additional help is needed—I’m glad you found that useful workaround!

 

[bswhipp]

I can backup but not restore still get the access denied error

 

[ChatGPT]

If you can backup IIS successfully but still get an "Access Denied" error when attempting appcmd restore backup, this means the read permissions during restoration (which involve overwriting existing IIS configuration files) are limited or blocked. This discrepancy between backing up and restoring usually occurs due to restricted write permissions or locked configuration files.
Let’s resolve this step-by-step to ensure restoration works:

---

Steps to Resolve "Access Denied" for appcmd restore backup​

---

Step 1: Verify Permissions for the Backup Folder​

Restoring a backup involves overwriting key IIS config files like applicationHost.config in its system location. Improper folder or file permissions are a common cause of issues.

1. Navigate to the IIS Config Backup Folder:
   

      C:\Windows\System32\inetsrv\backup

2. Check the Folder and File Permissions:
   • Folder (backup):
     • Right-click and select Properties > Security.
     • Verify the following accounts have Full Control:
     • Administrators
     • SYSTEM
     • If not present, add these accounts and grant Full Control.
   • Files within Backup Folder (applicationHost.config, etc.):
     • Open the backup folder (e.g., C:\Windows\System32\inetsrv\backup\YourBackupName).
     • Repeat the same permission steps for the actual content files.
3. Retry the Restore Command:
   

   bash
      appcmd restore backup "backupname"

---

Step 2: Ensure Elevated Admin Privileges (Re-check Context)​

Even if running Command Prompt as an administrator, appcmd may encounter access issues due to UAC or service-level permissions.

1. Launch Truly Elevated Command Prompt:
   • Search for Command Prompt > Right-click > Run as Administrator (again).
   • Type:
     

     bash
          appcmd restore backup "backupname"

---

Step 3: Stop IIS Services Before Restore​

Active IIS services or locked configuration files may block overwrite attempts during restoration.

1. Stop IIS Services:
   

   bash
      net stop W3SVC
      net stop WAS

2. Retry Restoration:
   

   bash
      appcmd restore backup "backupname"

3. Start IIS Services Again Once Restored:
   

   bash
      net start WAS
      net start W3SVC

---

Step 4: Temporarily Disable UAC​

If User Account Control (UAC) is interfering, temporarily disable it to restore IIS.

1. Adjust UAC Settings:
   • Open Control Panel > User Accounts > Change User Account Control Settings.
   • Move the slider to Never Notify.
2. Retry the Restoration Command:
   

   bash
      appcmd restore backup "backupname"

3. Reboot and Re-enable UAC Afterwards (Important).

---

Step 5: Manually Restore a Backup​

If appcmd restore backup continues to fail, manually override and replace the IIS configuration files from the backup.

1. Navigate to The Backup Location:
   • Example:
     

          C:\Windows\System32\inetsrv\backup\YourBackupName\

2. Backup the Current IIS Configuration:
   • Before overwriting, save the current config:
     

          C:\Windows\System32\inetsrv\Config\applicationHost.config

   • Copy it to a safe location for later recovery purposes.
3. Overwrite IIS Config Files:
   • Copy the following files from your backup folder and overwrite the originals:
     

          applicationHost.config

     Path to overwrite:
     

     bash
        appcmd restore backup "backupname"

     0
4. Restart IIS:
   

   bash
      appcmd restore backup "backupname"

   1

---

Step 6: Investigate Event Viewer for Clues​

If errors continue, Windows logs may provide insights into what's blocking the restoration.

1. Open Event Viewer (eventvwr.msc).
   • Check logs under:
     

     bash
        appcmd restore backup "backupname"

     2
2. Look specifically for:
   • Errors related to file permissions, IIS services, or locked config files.

---

Optional Step 7: Repair IIS​

If none of the above works, reset IIS’s configuration entirely before attempting restoration.

1. Backup the Current Config:
   

   bash
      appcmd restore backup "backupname"

   3
2. Reinstall IIS:
   • Uninstall IIS:
     

     bash
        appcmd restore backup "backupname"

     4
   • Reinstall IIS:
     

     bash
        appcmd restore backup "backupname"

     5
3. Restore the Original Config:
   • Use appcmd:
     

     bash
        appcmd restore backup "backupname"

     6

---

Summary​

The most likely root cause of Access Denied errors during restoration is insufficient permissions or locked files. The advised steps (permissions check, manually restoring config files, and stopping IIS services) should resolve these issues. Let me know how it goes and if additional errors or roadblocks appear—I’ll guide further!

 

[bswhipp]

Trying to restore kills the WWW Publishing Service

 

[ChatGPT]

If attempting to restore the IIS configuration using appcmd restore backup causes the World Wide Web Publishing Service (W3SVC) to stop, it indicates a deeper configuration conflict or corruption during the restoration process. The service abruptly stopping suggests that the restored configuration might have invalid elements or permissions issues, which ISAPI filters, custom modules, or corrupt applicationHost.config files could trigger.
Let’s fix your IIS restore process step-by-step while investigating why W3SVC is being terminated.

---

Steps to Resolve IIS Restoration Killing W3SVC​

Step 1: Verify the Backup Configuration​

There could be corruption or unsupported configuration elements in the backup files you're attempting to restore.

1. Inspect the Backup Files:
   • Navigate to your backup folder:
     

          C:\Windows\System32\inetsrv\backup\<backupname>

   • Open applicationHost.config in a text editor (like Notepad or Notepad++).
   • Look for:
     • Invalid XML structure (e.g., unclosed tags).
     • Unrecognized or custom modules (particularly under <system.webServer> or <modules>).
     • Bad site or application references (e.g., <site> pointing to non-existent directories).
2. Repair or Simplify Config (If Necessary):
   • Temporarily simplify the configuration to contain only basic/default settings:
     • Keep <sites> defined for core IIS sites (if critical to restore).
     • Remove custom <modules> or <isapiFilters> entries that might trigger crashes.
   Example: A minimal applicationHost.config backup might look like:
   

   xml
      <configuration>
          <system.applicationHost>
              <sites>
                  <site name="Default Web Site" id="1">
                      <application path="/" applicationPool="DefaultAppPool">
                          <virtualDirectory path="/" physicalPath="C:\inetpub\wwwroot" />
                      </application>
                  </site>
              </sites>
              <applicationPools>
                  <add name="DefaultAppPool" />
              </applicationPools>
          </system.applicationHost>
      </configuration>

3. Retry the Restore Command After Reviewing:
   

   bash
      appcmd restore backup "backupname"

---

Step 2: Test and Start the IIS Services Directly​

After restoring the configuration, test if services can restart manually to debug errors.

1. Attempt to Start W3SVC:
   

   bash
      net start W3SVC

2. If W3SVC Fails to Start:
   • Check the following logs for error details:
     • Event Viewer > Windows Logs > System or Application.
     • Review failures related to W3SVC, IIS, or WAS (Windows Activation Service).

---

Step 3: Clear Corrupted App Pools and Sites​

Custom sites or application pools can also cause instability during restoration.

1. List Application Pools:
   

   bash
      appcmd list apppool

2. Default Application Pools to Test:
   • Ensure DefaultAppPool exists and is functional (repair if necessary):
     

     bash
          appcmd add apppool /name:"DefaultAppPool"

3. Remove Corrupted Sites or Apps (Manually Identify Issues):
   

   bash
      appcmd list site

4. Restart IIS Services:
   

   bash
      iisreset

---

Step 4: Temporarily Disable Problematic Modules​

Custom IIS modules or ISAPI filters can crash W3SVC when included in a restored configuration.

1. Open your backup applicationHost.config file.
2. Look for <modules>:
   • Temporarily comment or remove any non-standard or custom modules (especially 3rd-party ones).
     Example:
     

     xml
        <modules>
            <!-- Temporarily remove problematic modules -->
            <add name="CustomModule" />
        </modules>

3. Retry Restore and Restart:
   

   bash
      appcmd restore backup "backupname"
      iisreset

---

Step 5: Validate Permissions for IIS Files​

The "Access Denied" errors during previous attempts and stopping of W3SVC may be connected to permissions issues.

1. Check Config Folder Permissions:
   • Navigate to:
     

     xml
        <configuration>
            <system.applicationHost>
                <sites>
                    <site name="Default Web Site" id="1">
                        <application path="/" applicationPool="DefaultAppPool">
                            <virtualDirectory path="/" physicalPath="C:\inetpub\wwwroot" />
                        </application>
                    </site>
                </sites>
                <applicationPools>
                    <add name="DefaultAppPool" />
                </applicationPools>
            </system.applicationHost>
        </configuration>

     0
   • Ensure the following accounts have Full Control:
     • SYSTEM
     • Administrators
2. Apply Permissions Recursively:
   • Right-click the folder > Properties > Security > Advanced.
   • Check the box "Replace all child object permissions with inheritable permissions from this object."
3. Restart IIS Services:
   • If restoring succeeds, attempt to restart W3SVC again:
     

     xml
        <configuration>
            <system.applicationHost>
                <sites>
                    <site name="Default Web Site" id="1">
                        <application path="/" applicationPool="DefaultAppPool">
                            <virtualDirectory path="/" physicalPath="C:\inetpub\wwwroot" />
                        </application>
                    </site>
                </sites>
                <applicationPools>
                    <add name="DefaultAppPool" />
                </applicationPools>
            </system.applicationHost>
        </configuration>

     1

---

Step 6: Rebuild Configuration if Restoration Fails​

If all else fails, manually reconstruct IIS instead of restoring the full backup.

1. Create a New IIS Baseline:
   • Rebuild IIS with default settings:
     

     xml
        <configuration>
            <system.applicationHost>
                <sites>
                    <site name="Default Web Site" id="1">
                        <application path="/" applicationPool="DefaultAppPool">
                            <virtualDirectory path="/" physicalPath="C:\inetpub\wwwroot" />
                        </application>
                    </site>
                </sites>
                <applicationPools>
                    <add name="DefaultAppPool" />
                </applicationPools>
            </system.applicationHost>
        </configuration>

     2
2. Restore Manual Configurations:
   • Manually migrate the backup file settings (e.g., <sites>, <appPools>) into the new applicationHost.config.

---

Logs for Debugging​

If services (like W3SVC) still won't start, check the following logs for granular errors:

1. Event Viewer:
   • Review System Logs for W3SVC errors.
   • Look for terms like:
     • "Invalid configuration."
     • "File not found."
2. HTTP Error Logs:
   • Found at:
     

     xml
        <configuration>
            <system.applicationHost>
                <sites>
                    <site name="Default Web Site" id="1">
                        <application path="/" applicationPool="DefaultAppPool">
                            <virtualDirectory path="/" physicalPath="C:\inetpub\wwwroot" />
                        </application>
                    </site>
                </sites>
                <applicationPools>
                    <add name="DefaultAppPool" />
                </applicationPools>
            </system.applicationHost>
        </configuration>

     3
3. Application Errors:
   • Review logs for .NET Framework, IIS extensions, or app pools.

---

Summary of Steps​

• First, simplify and verify the backup's configuration (applicationHost.config) to ensure it is clean and valid.
• Stop IIS services before restoring and validate whether W3SVC can restart after applying the backup.
• If restoration continuously fails due to config issues or W3SVC crashes, rebuild the server’s IIS configuration manually.

Let me know the outcome, or feel free to share error logs or specific findings, and I’ll assist further!

 

[bswhipp]

Well it is not any of this. I can create a backup of the Default Site and that is fine but can not restore that site. Get the same error

 

[ChatGPT]

Thanks for clarifying! If you’re able to create a backup of the Default Website successfully but cannot restore it, this strongly suggests there’s an underlying permission issue somewhere in the restore process, specifically when appcmd attempts to overwrite files in IIS directories. Since the issue persists even with a new, valid backup of the Default Website, we can eliminate corruption in the backup file itself and focus on permissions, locks, or restrictive policies.
Let’s dig deeper and get this restore working.

---

Updated Steps to Address Failed Restore​

---

Step 1: Test by Restoring While IIS Services Are Stopped​

The Access Denied issue might occur because the restore process tries to overwrite IIS configuration files while services like W3SVC or WAS are actively running, locking key files like applicationHost.config.

1. Stop IIS Services Properly:
   • Run:
     

     bash
          net stop W3SVC
          net stop IISADMIN
          net stop WAS

2. Cleanly Retry the Restore Command:
   

   bash
      appcmd restore backup "backupname"

3. If Successful:
   • Restart the IIS services:
     

     bash
          net start WAS
          net start W3SVC

4. If the Same Error Occurs:
   Proceed to adjust permissions and identify the locking process in Step 2.

---

Step 2: Verify and Fix Permissions on IIS Config Files​

The "Access Denied" error strongly suggests a permission issue preventing appcmd from writing updated configuration files. You may be missing write access to key files/folders like applicationHost.config during the restore.

1. Go to the IIS Configuration Folder:
   

      C:\Windows\System32\inetsrv\config

2. Check File Permissions:
   • Right-click the applicationHost.config file > Properties > Security tab.
   • Verify the following accounts have Full Control:
     • Administrators
     • SYSTEM
   • If any accounts are missing or lack Full Control, add them:
     • Click Edit > Add > Enter the account name and grant permissions.
3. Apply Permissions Recursively:
   • Ensure the same permissions are applied to:
     • The folder containing the config (C:\Windows\System32\inetsrv\config).
     • All child objects/files.
   • To propagate permissions:
     • Open Advanced Security Settings > Enable Replace all child object permissions.
4. Retry the Restore Command:
   

   bash
      appcmd restore backup "backupname"

---

Step 3: Temporarily Disable UAC​

Even as an Administrator, User Account Control (UAC) can impose restrictions on elevated actions, including overwriting system files.

1. Disable UAC Temporarily:
   • Open Control Panel > User Accounts > Change User Account Control Settings.
   • Move the slider to Never Notify.
   • Reboot the server if prompted.
2. Run the Restore Command:
   

   bash
      appcmd restore backup "backupname"

3. Re-enable UAC afterward (set slider back to original level).

---

Step 4: Verify Windows Process Locks​

A background process or open file handle may be preventing successful restoration.

1. Check for Locked Files:
   • Use Process Explorer (Sysinternals) to locate locks:
     • Launch Process Explorer (Admin Mode).
     • Go to Find > Find Handle or DLL.
     • Search for:
       

              applicationHost.config

   • Identify the process holding the file handle (common examples: w3wp.exe or inetinfo.exe).
2. Kill Locking Process:
   • Manually terminate the locking process if identified.

---

Step 5: Use Safe Mode to Bypass Service Interference​

If previous steps fail, rely on Safe Mode to bypass running services that might interfere with the restore process.

1. Start the System in Safe Mode:
   • Reboot and press F8 (or Shift + F8) to access Advanced Boot Options.
   • Select Safe Mode with Networking.
2. Retry the Restore Command:
   

   bash
      appcmd restore backup "backupname"

3. Reboot Into Normal Mode:
   • After restoring, restart the server and verify if the restoration resolves the issue.

---

Step 6: Test Manual File Copy (If Restore Still Fails)​

If appcmd restore backup consistently fails despite correct permissions, manually apply the backup configuration.

1. Go to the Backup Location:
   • Open:
     

          C:\Windows\System32\inetsrv\backup\<backupname>

2. Manually Replace Configuration File:
   • Backup the current config files in C:\Windows\System32\inetsrv\config:
     • Copy the applicationHost.config file to a backup directory.
   • Replace it with the applicationHost.config from <backupname>.
3. Restart IIS Services:
   

   bash
      net start WAS
      net start W3SVC

---

Step 7: Review Relevant Logs​

1. Open Event Viewer:
   • Look for errors in:
     

     bash
        appcmd restore backup "backupname"

     0
2. Check Log Entries:
   • Look for entries associated with IISADMIN, W3SVC, or applicationHost.config.
3. Let me know if specific error codes or new patterns emerge from the logs.

---

Next Steps if Issues Persist​

If none of the above steps resolve the issue:

• Share details about additional error messages or access patterns.
• Let me know if you’ve worked with custom configuration elements or modules that might affect IIS behavior.

We’ll tackle the issue together until resolved!

 

[bswhipp]

Trying to stop WAS, 3 other services are not stopping. They are in the stuck starting status. Net.Pipe Listener Adapter, Net.TCP Lisctneer Adapter, and Net.Tcp Port Sharing Service. So Unable to stop WAS

 

[ChatGPT]

If WAS (Windows Process Activation Service) is stuck because dependent services like Net.Pipe Listener Adapter, Net.TCP Listener Adapter, or Net.Tcp Port Sharing Service are in a "stuck starting" state, this is preventing WAS (and likely W3SVC) from stopping cleanly. These services are interdependent, and a failure in one can cascade to the others.
Let’s resolve these stuck services and regain control of IIS and its dependent components:

---

Steps to Fix Stuck Services and Restore IIS Functionality​

---

Step 1: Forcefully Kill Stuck Services​

If stopping the dependent services with net stop isn’t working, forcefully terminate them.

1. Identify PIDs for Stuck Services:
   • Run the following command to list the status of all services:
     

     bash
          sc queryex type= service state= all

   • Find the following services and note their PID:
     • Net.Pipe Listener Adapter: Service name is NetPipeActivator
     • Net.TCP Listener Adapter: Service name is NetTcpActivator
     • Net.Tcp Port Sharing Service: Service name is NetTcpPortSharing
2. Kill the Processes:
   • Forcefully terminate the services using their PID:
     

     bash
          taskkill /pid <PID> /f

   • Example:
     

     bash
          taskkill /pid 12345 /f

3. Once the dependent services are stopped, stop WAS:
   

   bash
      net stop WAS

---

Step 2: Validate Services and Clear Corruption​

If the services remain stuck, their configurations may be corrupted or improperly registered.

1. Re-Register the Services:
   • Open Command Prompt (Admin) and run:
     

     bash
          sc config NetPipeActivator start= demand
          sc config NetTcpActivator start= demand
          sc config NetTcpPortSharing start= demand
          sc config WAS start= demand

2. Check Service Dependencies:
   • Confirm required dependencies for these services:
     

     bash
          sc qc NetPipeActivator
          sc qc NetTcpActivator
          sc qc NetTcpPortSharing

3. Restart the Services:
   • Start each service sequentially to test dependencies:
     

     bash
          net start NetPipeActivator
          net start NetTcpActivator
          net start NetTcpPortSharing
          net start WAS

---

Step 3: Repair WCF and Net.TCP Features​

These services are tied to Windows Communication Foundation (WCF) and .NET Framework features. If dependencies are missing or damaged, the services won’t behave correctly.

1. Repair .NET Framework Core Features:
   • Fix related features using DISM:
     

     bash
          dism /online /enable-feature /featurename:NetFx4 /all
          dism /online /enable-feature /featurename:NET-WCF-Services45 /all

2. Repair or Reinstall Net.TCP Support:
   • Add missing Net.TCP features using DISM:
     

     bash
          dism /online /enable-feature /featurename:NET-WCF-TCP-Activation45

---

Step 4: Temporarily Disable Services to Restore WAS​

If the above steps don’t resolve the stuck state, disable the related services and start WAS first.

1. Disable Net.TCP and Pipe Services:
   • Temporarily disable the stuck services:
     

     bash
          sc config NetPipeActivator start= disabled
          sc config NetTcpActivator start= disabled
          sc config NetTcpPortSharing start= disabled

2. Stop and Restart WAS:
   • Now stop and restart the Windows Process Activation Service (WAS):
     

     bash
          taskkill /pid <PID> /f

     0
3. Re-enable the Dependent Services:
   • Set the dependent services back to their defaults:
     

     bash
          taskkill /pid <PID> /f

     1

---

Step 5: Check for Locked Files​

Locked resources can cause services to get stuck. Use Process Explorer or Resource Monitor to identify problematic locks.

1. Open Resource Monitor:
   • Open Task Manager > Performance tab > Open Resource Monitor.
   • Check the CPU or Disk tabs.
2. Look for high activity tied to services like:
   • NetPipeActivator
   • NetTcpActivator
3. Kill locking processes manually after identifying them.

---

Step 6: Investigate Logs​

If services still won’t stop or start properly, logs might indicate the reason.

1. Review Windows Logs:
   • Open Event Viewer > Windows Logs > System.
   • Look for errors tied to:
     • NetPipeActivator
     • NetTcpActivator
     • WAS
     • W3SVC
2. Key Errors to Investigate:
   • Errors related to missing dependencies or file paths.
   • Configuration corruption that references files or features no longer present.

---

Step 7: Repair Component Store​

If the services won't stop because of corrupted components, repair the underlying component store.

1. Run DISM to Repair the Component Store:
   

   bash
        taskkill /pid <PID> /f

   2
2. Run System File Checker:
   

   bash
        taskkill /pid <PID> /f

   3
3. Reattempt the service operations after this.

---

Step 8: Manual File Restore​

If locking or corruption persists:

1. Navigate to WAS and dependent service configuration files:
   

   bash
        taskkill /pid <PID> /f

   4
2. Backup both files, then restore from clean defaults or backups.

---

If Services Are Now Stopped​

Once services are stopped:

• Retry the IIS restore:
  

  bash
       taskkill /pid <PID> /f

  5
• Start the services after the restore completes:
  

  bash
       taskkill /pid <PID> /f

  6

---

Let Me Know​

Let me know if services remain stuck or if new error messages/log entries appear. Together, we’ll dig deeper into fixing this issue!

 

[bswhipp]

Sorry not Port Sharing Services Net.msmg Listener Adapter

 

[ChatGPT]

Thanks for clarifying—the Net.Msmq Listener Adapter is another dependent service tied to Windows Process Activation Service (WAS), often used for MSMQ (Microsoft Message Queuing) in WCF (Windows Communication Foundation). If this service is stuck in the "starting" state and preventing WAS from stopping, we need to address it specifically.
The stuck "starting" state usually results from:

1. Corrupted service configuration or bad dependencies.
2. MSMQ components not being properly registered.
3. Permission issues or resource locks.

Here’s how to fix this and regain control of WAS and the dependent services.

---

Steps to Fix Stuck Net.Msmq Listener Adapter​

---

Step 1: Forcefully Stop the Stuck Services​

To regain control over Net.Msmq Listener Adapter and WAS, forcefully terminate the stuck service.

1. Find the PID of the Stuck Service:
   Run:
   

   bash
      sc queryex NetMsmqActivator

   • Look for PID in the output (e.g., PID=XXXX).
2. Kill the Process:
   • Forcefully terminate the service process using its PID:
     

     bash
          taskkill /pid <PID> /f

     Example:
     

     bash
          taskkill /pid 12345 /f

3. Retry Stopping WAS:
   

   bash
      net stop WAS

---

Step 2: Restart MSMQ Components​

Net.Msmq Listener Adapter depends on MSMQ features. Restarting these services often clears the stuck state.

1. Stop the MSMQ Service (if running):
   

   bash
      net stop MSMQ

2. Restart the MSMQ Service:
   

   bash
      net start MSMQ

3. Try Starting the Listener Adapter:
   

   bash
      net start NetMsmqActivator

If MSMQ services are corrupted or missing, use Step 3 to repair them.

---

Step 3: Repair MSMQ and .NET WCF Services​

If there's a deeper issue with MSMQ or its dependent components (e.g., WCF features), repairing these can resolve the listener adapter's stuck state.

1. Re-enable MSMQ Services:
   • Use the DISM command to ensure that MSMQ components are reinstalled:
     

     bash
          dism /online /enable-feature /featurename:MSMQ-Server /all

2. Repair WCF Services:
   • Run:
     

     bash
          dism /online /enable-feature /featurename:NET-WCF-MSMQ-Activation45 /all

3. Test the Listener Adapter:
   

   bash
      net start NetMsmqActivator

4. Restart WAS:
   

   bash
        taskkill /pid <PID> /f

   0

---

Step 4: Temporarily Disable Listener Adapter​

If the listener adapter remains stuck or isn’t critical to current operations, you can disable it temporarily to focus on WAS/IIS.

1. Disable the Listener Adapter:
   

   bash
        taskkill /pid <PID> /f

   1
2. Stop WAS Again:
   

   bash
        taskkill /pid <PID> /f

   2
3. Retry the IIS Restore:
   

   bash
        taskkill /pid <PID> /f

   3
4. Re-enable the Listener Adapter After the Restore:
   

   bash
        taskkill /pid <PID> /f

   4

---

Step 5: Rebuild Listener Adapter Registration​

If the Net.Msmq Listener Adapter service is corrupted, rebuilding or re-registering it will resolve the issue.

1. Re-register the Service:
   Run:
   

   bash
        taskkill /pid <PID> /f

   5
2. Manually Fix Registrations (As Needed):
   • View or repair configuration files such as machine.config or applicationHost.config.

Example path for WCF or MSMQ-related configs:

bash
     taskkill /pid <PID> /f

6

1. Restart and Test:
   

   bash
        taskkill /pid <PID> /f

   7

---

Step 6: Investigate Logs​

Check logs for specific errors if the service remains stuck.

1. Event Viewer:
   • Open eventvwr.msc.
   • Look at:
     • Windows Logs > System (search for NetMsmqActivator).
     • Applications and Services Logs > Microsoft-Windows-WAS > Operational.
2. Common Errors to Investigate:
   • Dependencies failing, like MSMQ or .NET WCF.
   • Access or policy issues blocking service startup.

---

Step 7: Reset Component State​

If none of the above resolve the issue, the system configuration for MSMQ or WCF features may require a full reset.

1. Revert Pending Actions:
   • Clean pending system changes:
     

     bash
          taskkill /pid <PID> /f

     8
2. Repair Component Store:
   • Run:
     

     bash
          taskkill /pid <PID> /f

     9
3. Restart and Re-test Services:
   Retry stopping WAS and running the restore command.

---

Summary​

To resolve the stuck Net.Msmq Listener Adapter state:

1. Force stop the process using taskkill.
2. Repair or reinstall MSMQ services (dism /enable-feature).
3. Rebuild or re-register the NetMsmqActivator service if corruption is causing the issue.

Once the Adapter and WAS are functional, retry restoring your IIS backup (appcmd restore backup). Let me know the outcome or if other new errors appear—we’ll refine from there!