Hi @timmydoza , thanks for your reply.
Here’s what happened, based on your suggestion:
$ twilio login
$ twilio plugins:install @twilio-labs/plugin-rtc
$ npm run deploy:twilio-cli
> twilio-video-app-react@0.1.0 deploy:twilio-cli /Users/issactrotts/src/speakeasy/twilio-video-app-react
> cross-env REACT_APP_SET_AUTH=passcode npm run build && twilio rtc:apps:video:deploy --authentication=passcode --app-directory ./build
> twilio-video-app-react@0.1.0 build /Users/issactrotts/src/speakeasy/twilio-video-app-react
> node ./scripts/build.js
Creating an optimized production build...
Compiled successfully.
File sizes after gzip:
262.9 KB build/static/js/2.8fea057f.chunk.js
13 KB build/static/js/main.059b042d.chunk.js
784 B build/static/js/runtime-main.fa60846a.js
» Error code 20003 from Twilio: Authenticate. See https://www.twilio.com/docs/errors/20003 for more info.
npm ERR! code ELIFECYCLE
npm ERR! errno 35
npm ERR! twilio-video-app-react@0.1.0 deploy:twilio-cli: `cross-env REACT_APP_SET_AUTH=passcode npm run build && twilio rtc:apps:video:deploy --authentication=passcode --app-directory ./build`
npm ERR! Exit status 35
npm ERR!
npm ERR! Failed at the twilio-video-app-react@0.1.0 deploy:twilio-cli script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/issactrotts/.npm/_logs/2020-04-20T21_40_32_491Z-debug.log
This is what happened before, and it’s why I was using environment variables instead. The only additional info I found in the log was this stack trace:
12 info lifecycle twilio-video-app-react@0.1.0~deploy:twilio-cli: Failed to exec deploy:twilio-cli script
13 verbose stack Error: twilio-video-app-react@0.1.0 deploy:twilio-cli: `cross-env REACT_APP_SET_AUTH=passcode npm run build
&& twilio rtc:apps:video:deploy --authentication=passcode --app-directory ./build`
13 verbose stack Exit status 35
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1026:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
Error code 20103-13 : Microsoft Office Error code 20103-13 while trying to install or update Microsoft Office 365 or 2016 is due to internal registry conflicts, network connection errors, insufficient space allocations and preset proxy or firewall rules. The basic windows installer files in the computer may not work properly in case of these registry corruptions.
Especially Microsoft Office is a now an inevitable component of our day to day life such as schools, universities, business organisations and researches. So solving Office program error has crucial role in our hassle free computing.
The important factors causing Office Error code 20103-13 are
1. Disk space error.
2. Registry corruptions.
3. System file corruptions.
4. streaming connectivity error.
5. Firewall rules.
5. Multiple copies installed.
Follow the below steps to fix Error code 20103-13
1. SFC scan
System file checker is a pre-installed windows utility service which enables the windows users to scan and fix corruptions in windows system files. The SFC scan will identify the corrupted files and repair or restore the particular file from cached copies of system files located in a compressed folder at %WinDir%\System32\dllcache.
Reference Microsoft knowledge base : Article number 929833
Steps to perform SFC scan to fix Error code 20103-13:
1. First of all, make sure that the computer date and time is correct.
2. Open command promt with administratior previlages.
3. Type “SFC /SCANNOW” and click enter.
4. Do not close the Scan window untill it is 100% complete.
5. Once the scan is complete, start installation/update to check whether Error code 20103-13 is fixed.
2. Disable firewall to fix Office Error code 20103-13:
You might face Error code 20103-13 if the firewall on the computer block the Office installation or update due to security reasons. In order to bypass the Microsoft Office Error code 20103-13 we need to disable the firewall temporarily to install/update Office product.
Reference Microsoft Knowledge base : Article number 4028544
Steps to disable windows firewall:
1. Open control panel
2. Click on system and security
3. Open Windows Firewall
4. Click on “turn windows firewall ON or OFF”
5. Select “Turn OFF windows firewall” and click OK
6. Finally start installation/update to check whether Error code 20103-13 is fixed.
3. Perform disk clean up to fix Error code 20103-13:
Disk space error or low disk space on your computer may also case Error code 20103-13 while updating/installing Microsoft Office 365 or 2016. In order to fix the Error code 20103-13 due to disk space error, it is recommended to perform disk clean up on your computer.
Reference Microsoft Knowledge base : Article Number 17421
Follow the steps to perform disk clean up:
1. Open control panel
2. Click on system and security
3. Select Administrative tools
4. Open Disk clean up
5. Once disk clean up box is opened, select C Drive and click OK.
6. Check the folders to be cleaned and click OK.
7. Once Disk clean up finished cleaning, start installation/update to check whether Error code 20103-13 is fixed.
4. Registry repair to fix Error code 20103-13
You might also face Error code 20103-13 due to registry corruptions or binary data error. These registry errors needs repair for a proper installation of Microsoft Office 365 or Office 2016 on your computer.
Note: It is mandatory to backup the registry before modification. A single mistake in registry modification may cause severe damages on your windows operating system.
Reference Microsoft Knowledge base : Article Number 4027573 and 136393
Following given are the steps to fix registry errors:
1. Open Registry editor with administrator privilege
2. Navigate to Office registry folder in the given order
Computer Computer\HKEY_LOCAL_MACHINE
Computer\HKEY_LOCAL_MACHINE\SOFTWARE
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\OFFICE\
3. Delete the following subsidiary keys in Office folders HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\OFFICE\10.0 HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\OFFICE\11.0 HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\OFFICE\12.0 HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\OFFICE\14.0 HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\OFFICE\15.0 HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\OFFICE\16.0 HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\OFFICE\COMMON HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\OFFICE\SOFTWARE
4. Also delete sub folders such as WORD, EXCEL, OUTLOOK, POWER POINT in HKEY_LOCAL_CURRENT_USER\SOFTWARE\MICROSOFT\OFFICE\ folder
5. Delete Licenceservers key and LicenceServerRedirection key.
6. Once the corrupted keys are deleted, start installation/update to check whether Error code 20103-13 is fixed.
5. Complete removal and reinstall of Microsoft Office 365 or Office 2016 to fix Error code 20103-13:
The pre-installed or multiple copies of Office program on computer may block the installation of Microsoft Office program with Error code 20103-13. In this case of existing duplicate copies of office program it is recommended to remove the Office program on your computer completely to install Microsoft Office 365 or Office 2016.
Reference : Office article and Microsoft article number 4028054
Follow the steps to remove older version of office:
1. Open control panel
2. Navigate to programs and to Programs and features
3. Check for Microsoft Office in the installed list.
4. Click and uninstall Microsoft Office from the listed applications.
5. Once the program is removed completely, start installation/update to check whether Error code 20103-13 is fixed.
How to install Microsoft Office 365 or 2016?
Office 365 or Office 2016 installation is simple procedure using the Microsoft Office account. Customers can buy the product from office store. Once you purchase office 365 or Office 2016 your product will be added to your Microsoft Office personal account. And the Office product provided by your university or work will be added to your education, university or work account.
You can customise your installation from Office my account after logging in to the Office account.
Steps to install Microsoft Office :
1. Open Microsoft office my account login page
2. Log in to your Office account using registered Office email ID and password.
3. Click on install option below the Office product in your account
4. Save and run the downloaded setup file
(Note: do not go offline once the installation is initiated)
5. Click on close button once the installation is finished.
For more information please see our home page.
Disclaimer: We are independent support providers of Microsoft Products.
Error code 20103-13 : Microsoft office application is now an important element of our day to day life as it deals about our studies, work, business etc. And as it is a development era Microsoft has launched the well developed and secured products such as Office 365 and Office 2016 and also Office 2013 which was precede of Office 365 and Office 2016. You could buy the Office product from Microsoft product list or store .And in some cases the installation or update of Office may end up with Error code 20103-13
Step 1. Temporarily disable Firewall and Antivirus
Error code 20103-13 while installing or updating the Microsoft Office may occur in case of Network or firewall restriction. The network rules or firewall rules in the network/computer may block the installation of Office program or its updating as a part of their security measurements. These firewall rules and Antivirus are implemented on the computer by the network provider or the computer user on its core system or registry.
You could fix the Error code 20103-13 by disabling the firewall or antivirus temporarily or you could fix the Error code 20103-13 by making creating an exceptional rule for Microsoft Office installation or update.
Follow the steps to disable Firewall:
Step 1. Open “control panel”
Step 2. Navigate to “system and security” and then to “Windows Firewall”
Step 3. Click on “turn windows firewall On or Off”
Step 4. Select Turn Off firewall for both private and public network.
Step 5. Try installing or updating Microsoft Office and check whether the Error code 20103-13 is fixed.
For more information: click here to view Microsoft Reference article to disable windows firewall.
Follow the steps to disable Antivirus:
Step 1. Open Antivirus application installed on the computer.
Step 2. Click on settings and navigate to real time protection.
Step 3. Turn Off real time protection.
Step 4. Navigate to Antivirus firewall.
Step 5. Turn off Antivirus firewall.
Step 6. Click on YES or OK confirmation prompt if prompted.
Step 7. Try installing or updating Microsoft Office and check whether the Error code 20103-13 is fixed.
Step 2. SFC Scan to fix Error code 20103-13
Error code 20103-13 also occurs in case of system file errors or corruption. If the Error code 20103-13 is occurred due to the system file corruption, it could be fixed easily by the SFC scan. The SFC scan or system file checking scan is the process of replacing or repairing the corrupted copy of system files using the cached copy of the file from the directory.
Follow the steps to initiate SFC scan:
Step 1. Open command prompt in administrative privileges.
Step 2. Type “ sfc /scannow “ and click enter.
Step 3. The scan will begin automatically .
Step 4. Do not close the command prompt until the scan get completed.
Step 5. Try installing or updating Microsoft Office and check whether the Error code 20103-13 is fixed.
For more information: Click here to view Microsoft reference kb article 929833 for sfc scan
Step 3. Registry repair to fix Error code 20103-13
Error code 20103-13 also occurs due to registry corruption or key value errors. A single key value corruption or change may lead to malfunctioning of the entire Microsoft Office program.
In order to fix Error code 20103-13 it is required to repair the registry keys and rebuilt the string values. And we request you to back up the registry before initiating the registry repair as registry is a highly sensitive element of a computer system and it is recommended to be done in the presence of Online or offline technician.
For more information on back up of registry follow the Microsoft kb article 322756
Follow the steps to repair registry:
Step 1. Open registry editor
Step 2. Delete the preinstalled or older registry key which block the installation of latest version or update.
Step 3. Navigate the below keys and delete it.
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0
HKEY_CURRENT_USER\Software\Microsoft\Office\14.0
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0
HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Office\11.0
HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Office\12.0
HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Office\14.0
HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Office\15.0
Step 5. Also change the DWORD values in below keys from 0 to 1 in Office common registry folder.
LicenseServers
LicenseServerRedirection
AutoExpandDLsEnable
PassportAuthProvider
Solution 4. Remove and reinstallation.
If Error code 20103-13 is not fixed in registry repair, SFC scan and firewall/antivirus exception, it is required to remove the Office suite completely from the programs and features, and then to reinstall the product for a proper use.
Follow the steps given below to fix Error code 20103-13 completely.
Step 1. Open control panel
Step 2. Click on uninstall programs and features
Step 3. Search for Microsoft Office in the list.
Step 4. Select Microsoft Office and click on uninstall.
Step 5. Once uninstall is finished, try running Office setup to install Microsoft Office.
For more information: Click here to view Microsoft reference kb article to uninstall a program.
How to install Microsoft Office
Step 1. Open Office My Account
Step 2. Login to Office account using your registered email ID and password.
Step 3. Click on install Option under the Office product in your account.
Step 4. Save the installer setup if prompted and run it once download is completed.
Step 5. Do not go offline or reboot the computer once installation is initiated.
Step 6. Click on finish button once the program is installed completely.
Please note: If you are trying to install School or college or company version of Office suite click here to login to your office account and then follow from step 2.
Microsoft Office error code 20103-13: When your attempt to install Office fails, an error message typically tries to explain the cause. There are many reasons that could cause the error code 20103-13. Usually, error occurs due to the system files corruption or previous installation files not removed properly. Here is the list of troubleshooting steps to resolve the error. Follow the steps mentioned in this article in the exact order to fix the error code 20103-13. Check to see if the error fixed after finishing each troubleshooting step. Performing the troubleshooting steps mentioned in this article will resolve the error code 20103-13.
Troubleshooting steps to fix Microsoft Office error code 20103-13
When you install Office, you may see error code 20103-13 if a previous installation of Office is failed. Here are some things you can try to resolve error code 20103-13. We’ve listed the most common solutions first, so try them in order.
Common causes for error code 20103-13
- Antivirus software or firewall might be blocking the Office installation.
- Internet connection or proxy settings are preventing from installing Office.
- Pre-existing version of an Office suite is blocking the installation.
- Incomplete\partial\failed repair\installation\change\removal of a previous Office suite can prevent from installing a newer version.
Follow the below steps to troubleshoot the error code 20103-13
1 – Repair your Office app
error code 20103-13 will be fixed when Office repair tool replaces all the corrupted system files. Follow the steps below to run repair tool to fix the error.
- Open Control Panel using Start.
- Click on Programs and select Programs and Features.
- Click on the Office product that you want to repair.
- Click Change.
- Select Quick Repair and click on Repair. If Quick Repair didn’t fix the error code 20103-13, select Online Repair and click on Repair.
Note: If Office Repair did not fix the error, remove and reinstall the Office Suite to fix the error code 20103-13.
2 – Steps to remove Office
In case if the error persists even after running Office repair tool, uninstall Office from your computer.
- Open Control Panel using Start
- Click on Programs and select Programs and Features.
- Select Office Suite and click on Remove.
Note: If Office uninstallation failed or it didn’t fix the error, a manual uninstallation is required to completely remove the Office Suite.
3 – Steps to remove Office manually to fix the error code 20103-13
If the error code 20103-13 is re-occurring, proceed with the following steps to manually remove Office program from your computer.
Step 1: Remove the Windows Installer packages
- Find the Office 16 installation folder, typically located in C:\Program Files\.
- Right-click the Microsoft Office 16folder and select Delete.
Step 2: Remove the Office scheduled tasks
- Open a Command Prompt window as an administrator.
- At the command prompt, type the following commands and press Enter after each one:
schtasks.exe /delete /tn “\Microsoft\Office\Office Automatic Updates”
schtasks.exe /delete /tn “\Microsoft\Office\Office Subscription Maintenance”
schtasks.exe /delete /tn “\Microsoft\Office\Office ClickToRun Service Monitor”
Step 3: Use Task Manager to end the Click-to-Run tasks
- Open Task Manager.
- Click the Processtab
- If the following processes are running, right-click each one, and then click End taskafter you select each process.
- .exe
- setup*.exe
Step 4: Delete the Office files
- Press Windows logo key + R to open the Rundialog box.
- In the Openbox, type %ProgramFiles%, and then click OK.
- Delete the “Microsoft Office 16” folder.
- Delete the “Microsoft Office” folder.
- Open the Rundialog box, type %ProgramFiles(x86)%, and then click OK.
- Delete the “Microsoft Office” folder.
Step 5: Delete the Office registry sub keys
- Open Registry Editor.
- Delete the following registry subkeys:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppVISV
- HKEY_CURRENT_USER\Software\Microsoft\Office
- Then Deletethe Office key.
Step 6: Delete the Start menu shortcuts
- Open a Command Prompt window as an administrator.
- Type %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs, and then press Enter.
- Delete the “Microsoft Office 2016 Tools” folder.
4 – Download and install Office
1. Sign in to your My Account page using the link https://go.microsoft.com/fwlink/p/?LinkId=613327
2. Choose Install.
3. Click Run or the equivalent depending on the browser you’re using.
4. When you see “You’re good to go”, click All done.
Error code 20103-13: This article contains the troubleshooting steps to fix the error code 20103-13. If you have reached here after following all the above mentioned troubleshooting steps. If error still unresolved, you may contact Help desk for further assistance in troubleshooting error code 20103-13.
| error code 30033-77 | error code 1392-2 | error code 30015-11-1073741502 | error code 30058-26 | error code 30125-1011-500 | error code 30183-1011 | error code 0-1037 (0) |
| error code 3008-27 | error code 1392-26 | error code 30015-11-1073741790 | error code 30066 | error code 30125-1011-503 | error code 30183-1011-1 | error code 0-1005 (0) |
| error code 30103-13 | error code 1392-28 | error code 30015-11-2 | error code 30068-13 | error code 30125-28-12007 | error code 30183-1011-2147952507 | error code 0-1011 (0) |
| error code 30174-11 | error code 1392-4 | error code 30015-11-2147023843 | error code 30068-13-1058 | error code 30125-39-12007 | error code 30183-1011-2147954429 | error code 0-1012 (0) |
| error code 0-02 | error code 1392-6 | error code 30015-11-2147024319 | error code 30068-13-1715 | error code 30125-4 | error code 30183-1011-2147954552 | error code 0-1018 (0) |
| error code 0088-4 | error code 1406 | error code 30015-11-255 | error code 30068-39-1715 | error code 30125-4-12007 | error code 30183-1015 | error code 0-1028 (0) |
| error code 0-1 | error code 141078 | error code 30015-11-5 | error code 30068-4 | error code 30126-1011 | error code 30183-1015-1 | error code 0-1036 (0) |
| error code 0-1009 | error code 1466-3 | error code 30015-26-3 | error code 30068-4-1053 | error code 30126-1011-12030 | error code 30183-1-11-2147954429 | error code 1084-13 |
| error code 0-1009-0 | error code 15-14 | error code 30015-40-2147023834 | error code 30068-4-1058 | error code 30126-1011-12152 | error code 30183-28 | error code 1-1012 |
| error code 0-1011 | error code 1603 | error code 30015-4-1006 | error code 30068-4-1084 | error code 30126-4 | error code 30183-28-404 | error code 20175-4 (19) |
| error code 0-1011-0 | error code 1610612703-4 | error code 30015-4-1610612703 | error code 30068-4-1715 | error code 30138-6 | error code 30183-39 | error code 216-13 |
| error code 0-1012-0 | error code 1610612703-8 | error code 30015-4-183 | error code 30068-4-2 | error code 3014-13 | error code 30183-39-214701 | error code 30015-1011 (2) |
| error code 0-1018 | error code 1610612708-8 | error code 30015-4-3 | error code 30068-4-3 | error code 3014-27 | error code 30183-39-2147014790 | error code 30015-1011 (3) |
| error code 0-1036-0 | error code 1610622703-4 | error code 30015-4-5 | error code 3008-26 | error code 30143-37 | error code 30183-4 | error code 30015-1011 (5) |
| error code 0-2 | error code 17002 | error code 30015-6 | error code 30088-04 | error code 3014-4 | error code 30183-4-1 | error code 30015-1025 (5) |
| error code 0-22 | error code 1715-18 | error code 30015-6-1 | error code 30088-1015 | error code 30145-13 | error code 30183-4-2147012889 | error code 30015-11 (-1073610725) |
| error code 0-3 | error code 1715-4 | error code 30015-6-30 | error code 30088-1015-0 | error code 30145-16 | error code 30203-11 | error code 30015-11 (-1073741701) |
| error code 0-4 | error code 1715-5 | error code 30016-2 | error code 30088-1021 | error code 30145-18 | error code 3029-4 | error code 30015-11 (-1073741790-11) |
| error code 0-9 | error code 183-4 | error code 30016-22 | error code 30088-1021-0 | error code 30145-27 | error code 3033-27 | error code 30015-11 (-2147023834) |
| error code 0x404 | error code 1920 | error code 30016-39 | error code 30088-1028-0 | error code 30145-4 | error code 30765-11 | error code 30015-11 (-2147024319) |
| error code 1006-4 | error code 20103-13 | error code 30016-4 | error code 30088-11 | error code 30169-22 | error code 30812-4-2 | error code 30015-11-1073610672 |
| error code 10106-1 | error code 20175-4-19 | error code 300184-4 | error code 30088-13 | error code 30169-26 | error code 3088-13 | error code 30015-11(9) |
| error code 10106-4 | error code 2-13 | error code 30027-4 | error code 30088-15 | error code 30170-28 | error code 3088-26 | error code 30015-13 |
| error code 10107-0 | error code 2147023834-11 | error code 30029-04 | error code 30088-22 | error code 30170-4 | error code 3088-4 | error code 30015-39 (5) |
| error code 10107-1 | error code 2147023836-11 | error code 30029-1007 | error code 30088-26 | error code 30174-11-1392 | error code 3-1 | error code 30015-4 (193) |
| error code 1018-13 | error code 2147024784-4 | error code 30029-1007-0 | error code 30088-28 | error code 30174-22 | error code 31075-4 | error code 30015-40 |
| error code 1052-4 | error code 2147024891-11 | error code 30029-1007-123 | error code 30088-4 | error code 30174-4 | error code 31075-4-8 | error code 30015-40 (-1073741790) |
| error code 1056-16 | error code 2147217387 | error code 30029-24 | error code 30088-8 | error code 30174-4-1 | error code 32-4 | error code 30015-6 (-1) |
| error code 1056-4 | error code 2147483634-8 | error code 30029-28 | error code 30088-88 | error code 30174-4-1392 | error code 3-28 | error code 30016-23 |
| error code 1058-16 | error code 214748363-8 | error code 30029-4 | error code 30089-13 | error code 30174-4-1920 | error code 3-4 | error code 30016-26 |
| error code 1058-4 | error code 2-16 | error code 30033-1011 | error code 30089-14 | error code 30174-4-247012889 | error code 39-30053 | error code 30053-39 |
| error code 1072-3 | error code 25004 | error code 30033-1011-0 | error code 30089-4 | error code 30174-45 | error code 403-4 | error code 30068-15 (1715) |
| error code 1073422314 | error code 255-11 | error code 30033-27 | error code 30094-1 | error code 30174-8 | error code 404-4 | error code 30068-26 |
| error code 1084-16 | error code 255-6 | error code 30033-4 | error code 30094-1011 | error code 30175-11 | error code 408-4 | error code 30088-1007 |
| error code 1084-4 | error code 300102-13 | error code 30034-4 | error code 30094-1011-0 | error code 30175-12 | error code 5-11 | error code 30088-1007 (0) |
| error code 12002-1 | error code 30013-39 | error code 30038-26 | error code 30094-4 | error code 30175-12-30 | error code 5-13 | error code 30088-13 (1715) |
| error code 12002-28 | error code 30015 | error code 30058-28 | error code 30101-11 | error code 30175-13 | error code 5-14 | error code 30125-1011 (400) |
| error code 12002-4 | error code 30015-1 | error code 30038-28 | error code 30102-1 | error code 30175-13-30 | error code 5-26 | error code 30147-13 |
| error code 1200-4 | error code 30015-1007-123 | error code 300384 | error code 30102-11 | error code 30175-19 | error code 5-4 | error code 30147-37 |
| error code 12007-04 | error code 30015-1011-2 | error code 30038-4 | error code 30102-11-1601 | error code 30175-26 | error code 5-6 | error code 30153-4 |
| error code 12007-1 | error code 30015-1011-5 | error code 30043-11 | error code 30102-11-1603 | error code 30175-4 | error code 641-80070641 | error code 30175-4 (19) |
| error code 12007-28 | error code 30015-1015-183 | error code 30045-11 | error code 30102-13 | error code 30175-7 | error code 75550 | error code 30182-1015 (2) |
| error code 12007-4 | error code 30015-1015-32 | error code 30045-13 | error code 30102-4 | error code 30179-4 | error code 772 | error code 30183-1 (1) |
| error code 12029-4 | error code 30015-1015-5 | error code 30045-26 | error code 30103-11 | error code 30180-4 | error code 30088-27 | error code 30183-1011 (2147954407) |
| error code 12030-4 | error code 30015-1025-1392 | error code 30045-27 | error code 30125-1011 | error code 30182-1015 | error code 30184-4 | error code 30183-1011 (403) |
| error code 12152-4 | error code 30015-1025-14001 | error code 30045-39-1 | error code 30125-1011-10106 | error code 30182-1015-3 | error code 3045-26 | error code 30183-1015 (2147954402) |
| error code 1224-28 | error code 30015-1025-193 | error code 30045-4 | error code 30125-1011-10107 | error code 30182-1015-4 | error code 30813-4 | error code 30183-28 (404) |
| error code 1224-4 | error code 30015-1025-216 | error code 30045-4-1 | error code 30125-1011-12029 | error code 30182-1022-2147954430 | error code 30068-4 (1975) | error code 30183-28 (512) |
| error code 1310 | error code 30015-1025-5 | error code 30045-6 | error code 30125-1011-1207 | error code 30182-4-2 | error code 30125-1011 (12002) | error code 30183-39 (-214701) |
| error code 1325 | error code 30015-11 | error code 30053-4 | error code 30125-1011-404 | error code 30183-1 | error code 30125-1011 (12007) | error code 30183-39 (-2147014790) |
| error code 3088-1015 (0) | error code 3088-1007 (0) | error code 3088-1008 (0) | error code 0-1056 (0) | error code 1056-4 (0) | error code 30125-1011 (403) | error code 30015-8 |
This really is not a question but how I was able to resolve my problem with RRAS not being able to start.
I had RRAS (using NAT only) running just fine. Then it just stopped working. I had no idea as to what had happened. My event log showed an event id 20103 — Unable to load C:\windows\system32\iprtrmgr.dll. I tried all of the following
solutions to no avail.
http://support.microsoft.com/kb/299013/en-us
Resetting TCP IP by using netsh:
http://support.microsoft.com/kb/299357
I also tried to removing the IPv6 from the registry: HKEY_LOCAL_MACHINE\System\currentcontrolset\services\remoteaccess\routermanagers\IPV6
But nothing would work. So I broke out the Process Monitor and checked to see what registry calls were being made and which ones were unsuccessfull. I found the PID of the svchost which loads the iprtrmgr.dll. Working my way from bottom up,
I traced all of the entries with that PID. At one point I found where a SUCCESS call was made to the registry entry of
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RemoteAccess\RoutingTableManager\Instance 00000\AddressFamily 00002, but then a NAME_NOT_FOUND for the registry entry of
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RemoteAccess\RoutingTableManager\Instance 00000\AddressFamily 00023.
I checked my registry and noticed that I was missing the AddressFamily 00023 entry. I created a virtual machine of Windows 2008 R2, loaded RRAS and then compared the two registries. The
AddressFamily 00023 entry was in my VM guest. So copied that registry key over to my machine and was able to get RRAS started.
Hopefully this will help others who having the same problem.
-ryan