You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To access the OLE DB Driver for SQL Server, the consumer must first create an instance of a data source object by calling the `CoCreateInstance` method. A unique class identifier (CLSID) identifies each OLE DB provider. For the OLE DB Driver for SQL Server, the class identifier is CLSID_MSOLEDBSQL. You can also use the symbol, MSOLEDBSQL_CLSID, that resolves to the OLE DB Driver for SQL Server used in the referenced`msoledbsql.h` file.
23
+
To access the OLE DB Driver for SQL Server, the consumer must first create an instance of a data source object by calling the `CoCreateInstance` method. A unique class identifier (CLSID) identifies each OLE DB provider. For the OLE DB Driver for SQL Server, you can use the MSOLEDBSQL_CLSID symbol defined in the `msoledbsql.h` file.
24
24
25
25
The data source object exposes the `IDBProperties` interface, which the consumer uses to provide basic authentication information such as server name, database name, user ID, and password. The `IDBProperties::SetProperties` method is called to set these properties.
26
26
@@ -29,14 +29,14 @@ If there are multiple instances of [!INCLUDE[ssNoVersion](../../../includes/ssno
29
29
The data source object also exposes the `IDBInitialize` interface. After the properties are set, connection to the data source is established by calling the `IDBInitialize::Initialize` method. For example:
30
30
31
31
```cpp
32
-
CoCreateInstance(CLSID_MSOLEDBSQL,
32
+
CoCreateInstance(MSOLEDBSQL_CLSID,
33
33
NULL,
34
34
CLSCTX_INPROC_SERVER,
35
35
IID_IDBInitialize,
36
36
(void **) &pIDBInitialize)
37
37
```
38
38
39
-
This call to `CoCreateInstance` creates a single object of the class associated with CLSID_MSOLEDBSQL (CSLID associated with the data and code that will be used to create the object). IID_IDBInitialize is a reference to the identifier of the interface (`IDBInitialize`) to be used to communicate with the object.
39
+
This call to `CoCreateInstance` creates a single object of the class associated with MSOLEDBSQL_CLSID (CSLID associated with the data and code that will be used to create the object). IID_IDBInitialize is a reference to the identifier of the interface (`IDBInitialize`) to be used to communicate with the object.
40
40
41
41
The following sample shows how to initialize and establish a connection to the data source.
This article lists files and registry keys to monitor for product deployment integrity when you install extensions to enable servers or SQL Server instances for Azure Arc.
16
+
17
+
## Windows server files
18
+
19
+
| Path | Description |
20
+
| :----- | :----- |
21
+
|`%ProgramFiles%\AzureConnectedMachineAgent\*`|`azcmagent` CLI and instance metadata service executables |
22
+
|`%ProgramFiles%\AzureConnectedMachineAgent\GCArcService\GC\*`| Extension service executables |
23
+
|`%ProgramData%\AzureConnectedMachineAgent\*`| Configuration, log and identity token files for azcmagent CLI and instance metadata service |
24
+
|`%ProgramData%\Application Data\Microsoft\Crypto\RSA\MachineKeys`| Windows certificate private keys |
25
+
26
+
## SQL Server files
27
+
28
+
| Path | Description & notes |
29
+
| :----- | :----- |
30
+
|`%ProgramFiles%\Sql Server Extension\*`| Extension program files |
|`C:\Windows\System32\Tasks\Microsoft\SqlServerExtension`| XML for scheduled task for providing privileges |
34
+
|`C:\Windows\ServiceProfiles\SqlServerExtension\AppData\Local\Microsoft SQL Server Extension Agent\*`| When configured for [least privilege](configure-least-privilege.md) <br/><br/> Feature application |
35
+
|`C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft SQL Server Extension Agent\*`| When not configured for [least privilege](configure-least-privilege.md) <br/></br> Feature application |
36
+
37
+
## Registry keys
38
+
39
+
Base key: `HKEY_LOCAL_MACHINE`
40
+
41
+
| Key | Description & notes |
42
+
| :----- | :----- |
43
+
|`SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceRegistryName>\MSSQLSERVER`| Microsoft Entra ID registry key |
Copy file name to clipboardExpand all lines: docs/sql-server/azure-arc/troubleshoot-telemetry-endpoint.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -128,10 +128,11 @@ The following table shows some of the common DPS upload status values and what y
128
128
| --- | --- | --- |
129
129
|`0`|| Likely cause: a firewall is blocking the transmission of the data to the DPS. Open the firewall to the DNS endpoint for the DPS (TCP, port: 443).|
130
130
|`OK`| 200 | The connection is working as expected. |
131
+
|`Bad request`|400|Possible cause: The resource name (SQL Server instance or database name) doesn't conform to Azure resource naming conventions. For example, if the database name is a [reserved word](/azure/azure-resource-manager/troubleshooting/error-reserved-resource-name).|
131
132
|`Unauthorized`| 401 | Likely cause: the extension is configured to send data through an HTTP proxy that requires authentication. Using an HTTP proxy that requires authentication is not currently supported. Use an unauthenticated HTTP proxy or no proxy.|
132
133
|`Forbidden`| 403 | If the Azure Connected Machine agent is otherwise working as expected and this error doesn't resolve itself after a reboot, create a support case with Microsoft Support through the Azure portal.|
133
134
|`NotFound`| 404 | The endpoint that the extension is trying to connect to doesn't exist. You can check which endpoint it is trying to connect to by searching in the logs for `dataprocessingservice` (or before March, 2024 `san-af`). This condition can happen if the Azure Connected Machine agent was deployed and connected to an Azure region in which the `Microsoft.AzureArcData` resource provider is not yet available. [Redeploy the Azure Connected Machine agent](/azure/azure-arc/servers/manage-agent?tabs=windows#uninstall-the-agent) in a region that the `Microsoft.AzureArcData` resource provider for SQL Server enabled by Azure Arc is available. [Region availability](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-arc)|
134
-
| `Conflict` | 409 | Likely cause: temporary error happening inside of the DPS. If this does not resolve itself, create a support case with Microsoft Support through the Azure portal.
135
+
|`Conflict`| 409 | Likely cause: temporary error happening inside of the DPS. If this does not resolve itself, create a support case with Microsoft Support through the Azure portal.|
135
136
|`InternalServerError`| 500 | This is an error that is happening inside of the DPS. Create a support case with Microsoft Support through the Azure portal. |
0 commit comments