Troubleshooting: SqlProfileProvider Error "The Incoming Tabular Data Stream (TDS) Remote Procedure Call (RPC) Protocol Stream Is Incorrect"

Version Affected: All
 
 

Overview

When using SQL Server to store some of a user's Profile entries, updating that user's profile fails with an error similar to:

SqlProfileProvider.SetPropertyValues: Error received when saving data to user storage, exception: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter 37 ("@DigitalFP"), row 0, column 0: Data type 0xF3 (user-defined table type) has a non-zero length database name specified. Database name is not allowed with a table-valued parameter, only schema name and type name are valid.

Cause

The standard SQL stored procedures expect a value for certain attributes. This isn't a problem when SQL Server is the realm's complete Profile store, but if SQL Server is only being used for a few specific attributes and one of those expected values is missing, this error is thrown.

Resolution

1. Open the Admin Console.
2. On the realm in question, click the Data tab.
3. Make sure all 4 of the following attributes are set to be stored in SQL Server, as Plain Binary: Fingerprints (DigitalFP), Push Notification Tokens (PNToken), OATH Tokens (OATHToken), and Access Histories (AccessHistory).

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.