Why This Error Happens
Error 1743 (RPCSSTRINGTOOLONG) occurs when a Remote Procedure Call (RPC) operation attempts to process a string binding, name, or annotation that exceeds the maximum character limit defined by the RPC runtime. This is commonly triggered by corrupted registry entries, an oversized computer/domain name, or malformed configuration strings in services like Print Spooler, DCOM, or Group Policy that rely on RPC communication. In many cases, third-party software or a botched update leaves behind an invalid string value in the registry that RPC repeatedly tries and fails to parse.
Step-by-Step Resolution Guide
Step 1: Verify Computer and Domain Name Length
- Open Settings > System > About and check the Device name field.
- Ensure the name does not exceed 15 characters, as NetBIOS and RPC have strict length limitations.
- If the name is too long, click Rename this PC, enter a shorter name, and restart.
Step 2: Restart and Reset the RPC-Dependent Services
- Press
Win + R, typeservices.msc, and hit Enter. - Locate Remote Procedure Call (RPC) and DCOM Server Process Launcher, right-click each, and select Restart.
- Open Command Prompt as Administrator and run:
net stop spooler
net start spooler
- This clears any stuck string bindings related to print or network services.
Step 3: Scan for Corrupted System Files
- Open Command Prompt (Admin) and run:
sfc /scannow
- Follow this with a DISM health check to repair the underlying Windows image:
DISM /Online /Cleanup-Image /RestoreHealth
- Restart the PC once both scans complete successfully.
Step 4: Inspect and Clean the Registry String Values
- Press
Win + R, typeregedit, and press Enter. - Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcSs
- Look for any string values (REG_SZ) with unusually long or garbled character data and revert them to default (back up the key first via File > Export).
Step 5: Update Network and Print Drivers
- Go to Device Manager > Network adapters and Print queues.
- Right-click each device and select Update driver > Search automatically for drivers.
- Outdated or mismatched drivers often send malformed RPC strings, triggering Error 1743.
Alternative or Verification Steps
- After completing the steps, open Event Viewer (
eventvwr.msc) and check the System log for recurrence of Event ID 1743 to confirm the fix. - If the error persists, perform a System Restore to a point before the issue began, or use Reset this PC (Keep my files) via Settings > System > Recovery as a last resort.