Credential Manager Unavailable
One of these messages, followed by notes that name Credential Manager:
Windows would not store the Salesforce connection in Credential Manager (Windows error 1312).
Windows would not read the stored Salesforce connections from Credential Manager (Windows error 1312).
Windows would not remove the Salesforce connection from Credential Manager (Windows error 1312).
The Windows error number can differ.
Speediful keeps each Salesforce connection in Windows Credential Manager, under the Windows
account that runs Speediful. SLAM_add_connection writes the connection there, and every
other procedure reads it back. This error means Windows refused to let that account use
Credential Manager. Nothing is wrong with the connection details.
SLAM_add_connection signs in to Salesforce to test the connection before it stores
anything. When the store fails, the procedure fails with this error and does not report that
the connection test succeeded. The connection was not saved, so run it again after fixing the
cause below.
Which account runs Speediful
Speediful's procedures must be run from a login that is a member of the sysadmin server
role. Procedures run Speediful through xp_cmdshell. For a sysadmin login, that runs as
the SQL Server service account. For any other login, it runs as the xp_cmdshell proxy
account set with sp_xp_cmdshell_proxy_account, which Speediful does not support.
The usual cause of this error is a proxy account: it cannot use Credential Manager, so it cannot store a connection or read one stored by another account. Storing the connection while signed in to Windows as the proxy account does not help.
What to do
- Run the procedures from a login that is a member of the
sysadminrole, so that Speediful runs as the SQL Server service account. - If the connection was never stored for the SQL Server service account, run
SLAM_add_connectionfrom that login. See Salesforce Connection Management. - If the error appears for a
sysadminlogin, contact Speediful support with theSupport reference #from the output and the Windows error number.
A stored connection cannot be read
The stored Salesforce connection for username <username> cannot be read.
Credential Manager is available, and it holds an entry for that username, but the entry is
not a Salesforce connection that Speediful can read. This can happen when the entry was
edited or replaced outside Speediful. SLAM_list_connections leaves the entry out of its
list and prints the same warning for it.
To fix it, remove the connection and add it again:
EXEC SLAM_remove_connection @username = 'user@example.com'
EXEC SLAM_add_connection @username = 'user@example.com', ...
See Salesforce Connection Management for the
SLAM_add_connection parameters.
Related error number
Each of these errors is raised as error 88300 (exit code 1). The message appears in the Results pane.