Skip to content

Commit 99e13da

Browse files
committed
edit
1 parent 8c5a39c commit 99e13da

1 file changed

Lines changed: 16 additions & 14 deletions

File tree

articles/service-connector/how-to-troubleshoot-front-end-error.md

Lines changed: 16 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -16,48 +16,50 @@ This article lists Service Connector error messages you might encounter in the A
1616

1717
## Azure portal
1818

19-
The following errors and troubleshooting actions can occur in the Azure portal.
19+
The following Service Connector errors can occur in the Azure portal.
2020

2121
### Unknown resource type
2222

23-
- Check whether Service Connector supports the source and target resource service types.
24-
- Check whether Service Connector supports the specified source-target connection combination.
25-
- Check whether the target resource exists.
26-
- Check whether the target resource ID is correct.
23+
To troubleshoot, make sure that:
24+
25+
- Service Connector supports the source and target resource service types.
26+
- Service Connector supports the specified source-target connection combination.
27+
- The target resource exists.
28+
- The target resource ID is correct.
2729

2830
### Unsupported resource
2931

30-
- Check whether the selected authentication type supports the specified source-target connection combination.
32+
To troubleshoot, make sure that the selected authentication type supports the specified source-target connection combination.
3133

3234
## Azure CLI
3335

34-
The following errors and troubleshooting actions can occur in Azure CLI.
36+
The following Service Connector errors can occur in Azure CLI.
3537

3638
### InvalidArgumentValue errors
3739

3840
| Error message | Suggested action |
3941
|--------------------|-----------------------------|
40-
| `The source resource ID is invalid: {SourceId}` | - Check whether Service Connector supports the source resource ID.<br> - Check whether the source resouce ID is correct. |
41-
| `Target resource ID is invalid: {TargetId}` | - Check whether Service Connector supports the target service type.<br> - Check whether the target resouce ID is correct. |
42-
| `Connection ID is invalid: {ConnectionId}` | Check whether the connection ID is correct. |
42+
| `The source resource ID is invalid: {SourceId}` | - Make sure Service Connector supports the source resource ID.<br> - Make sure the source resource ID is correct. |
43+
| `Target resource ID is invalid: {TargetId}` | - Make sure Service Connector supports the target service type.<br> - Make sure the target resource ID is correct. |
44+
| `Connection ID is invalid: {ConnectionId}` | - Make sure the connection ID is correct. |
4345

4446
#### RequiredArgumentMissing errors
4547

4648
| Error message | Suggested action |
4749
|--------------------|-----------------------------|
4850
| `{Argument} shouldn't be blank` | Provide an argument value for interactive input. |
49-
| `Required keys missing for parameter {Parameter}. All possible keys are: {Keys}` | Provide a value for the authentication information parameter, usually in the form of `--param key1=val1 key2=val2`. |
51+
| `Required keys missing for parameter {Parameter}. All possible keys are: {Keys}` | Provide a value for the authentication information parameter, usually in the form `--param key1=val1 key2=val2`. |
5052
| `Required argument is missing, please provide the arguments: {Arguments}` | Provide the required argument. |
5153

5254
#### Validation errors
5355

5456
| Error message | Suggested action |
5557
|--------------------|-----------------------------|
56-
| `Only one auth info is needed` | Provide one and only one authentication information parameter. Check whether there are none, or more than one. |
58+
| `Only one auth info is needed` | Provide one and only one authentication information parameter. Make sure there is one, but not more than one. |
5759
| `Auth info argument should be provided when updating the connection: {ConnectionName}` | Provide the authentication information when you update a secret connection type. The Azure Resource Manager API can't access a user's secret. |
5860
| `Either client type or auth info should be specified to update` | Provide either client type or authentication information when you update a connection. |
59-
| `Usage error: {} [KEY=VALUE ...]` | Check the available keys and provide values for the authentication information parameter, usually in the form of `--param key1=val1 key2=val2`. |
60-
| `Unsupported Key {Key} is provided for parameter {Parameter}. All possible keys are: {Keys}` | Check the available keys and provide values for the authentication information parameter, usually in the form of `--param key1=val1 key2=val2`. |
61+
| `Usage error: {} [KEY=VALUE ...]` | Check the available keys and provide values for the authentication information parameter, usually in the form `--param key1=val1 key2=val2`. |
62+
| `Unsupported Key {Key} is provided for parameter {Parameter}. All possible keys are: {Keys}` | Check the available keys and provide values for the authentication information parameter, usually in the form `--param key1=val1 key2=val2`. |
6163
| `Provision failed, please create the target resource manually and then create the connection. Error details: {ErrorTrace}` | Retry. If necessary, create the target resource manually and then create the connection. |
6264

6365
## Related content

0 commit comments

Comments
 (0)