[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-18。"],[],[],null,["# Troubleshoot errors and grant suspension\n\nUse these instructions to troubleshoot issues with\nCitizens Broadband Radio Service Device (CBSD) errors and grant suspension.\n\nTo troubleshoot issues with interoperability testing between Spectrum Access System (SAS)\nand a [CBSD](/spectrum-access-system/docs/key-terms#cbsd), see\n[Troubleshoot interoperability testing issues](/spectrum-access-system/docs/topics/iot-troubleshoot).\n\nTo troubleshoot issues when using the SAS Portal, see\n[Troubleshoot SAS issues](/spectrum-access-system/docs/troubleshooting).\n\nReview CBSD history\n-------------------\n\nTo troubleshoot errors when you register a CBSD or\nrequest new spectrum grants, you can review the CBSD history log\nand device activity. Reviewing the CBSD history log also\nhelps you to investigate why a spectrum grant lost transmission authorization.\n\nTo view CBSD history, follow these steps:\n\n1. Go to the [SAS Portal](https://wirelessconnectivity.google.com/sas/welcome).\n2. Click **View deployments**.\n3. Optional: If you are an administrator for multiple organizations, select the organization that contains the device whose history you want to review.\n4. Select the device, and then click **Open**.\n5. On the right, click the **History** tab.\n6. Enter the date range in \u003cvar translate=\"no\"\u003eMM-DD-YYYY\u003c/var\u003e format or click date_range **Calendar**. The CBSD history displays automatically unless there is no history available in the specified timeframe.\n7. To view the history for a new event, click refresh **Refresh**.\n8. To download a CSV of the CBSD history, at the top of the grant activity log, click file_download **Download file**.\n\nUnderstand CBSD events\n----------------------\n\nThe Google SAS Portal\nshows a log of all activity within the last 30 days for each CBSD\nregistered with SAS. CBSD history is available\nin a **Registered** , **Granted** , or **Authorized** state.\nDevices that are in a **Draft** , **Ready for CPI** , or **Pending Registration**\nstate only have a CBSD history if the CBSD\nattempted to connect with SAS.\n\nThe SAS Portal records the following events for each CBSD.\n\nError code 103 for a CBSD\n-------------------------\n\nIf you receive an `Error code 103 Invalid field: installationParam` error when\nregistering a CBSD with\n[Certified Professional Installer (CPI)](/spectrum-access-system/docs/key-terms#cpi)-signed\nparameters, include the `cpiSignatureData` field and take out the\n`installationParam` field in your registration request.\n\nIf both fields are included, the registration request is not approved.\nThis happens even if the values in the `installationParam` field are the same as\nthe values provided by the CPI.\n\nResend (106) response code\n--------------------------\n\nSAS sends the `Resend (106)` response code for retryable\nerrors. If the CBSD receives this response code, it resends\nthe original request until it succeeds. We recommend an exponential backoff\nbetween requests.\n\nA CBSD is most likely to see this response code when sending a\ngrant request during\n[Coordinated Periodic Activities among SASs (CPAS)](/spectrum-access-system/docs/key-terms#cpas).\n\nA Domain Proxy (DP) might see this response code when sending a batch request\nfor more than 120 CBSDs. Only the first 120 entries\nare processed; subsequent devices in the batch receive a `Resend (106)` response code.\nHowever, there is no limit to the number of simultaneous\nbatch requests that can be made to SAS.\n| **Important:** The `Resend (106)` response code is not included in the current [SAS-CBSD Protocol v1.2](https://winnf.memberclicks.net/assets/CBRS/WINNF-TS-0016.pdf).\n\nSAS error code troubleshooting matrix\n-------------------------------------\n\nThe following matrix helps a CBSD operator to determine the root\ncause for each SAS response code returned to the\nCBSD or DP. It contains the following four columns:\n\n- **Response code.** The WInnForum SAS-CBSD protocol response code value and name returned by SAS.\n- **What it means.** A summary of the cause of the response code.\n- **Action required.** The actions needed to unblock the CBSD when you receive the corresponding response code.\n- **Support.** We recommend that you contact the support team listed for the error and then continue to the others in order."]]