Started receiving the error below and it is not resolving itself even after the REPLICATE ALL. Any ideas what the soution would be for this issue? Thanks in advance.
Error: SF_Refresh failed for table ApexClass [SQLSTATE 01000]
Error 7330, Severity 16, State 2, Line 1 [SQLSTATE 01000]
Cannot fetch a row from OLE DB provider "DBAmp.DBAmp" for linked server "SF_CD_LINK_SERVER". [SQLSTATE 01000]
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.


-
What command are you running that causes the error? What version of DBAmp are you running? Also, can you post the complete message output from the failing command.
-
-
It is failing on both SF_refreshAll (errors attached) and when the weekly run of SF_ReplicateAll. the refresh uses the "Yes" switch. Version 3.1.5.
I am running in our test org with same version and didn't get that specific error but go some other error regarding date conflicts but that's because we don't run jobs in our test org. The SF release (Winter '19) is being pulled from in both sandbox and production orgs.
The job in test just completed and at the end of the log there are no errors. So this issue seems to be in our production DBAmp setup. Both test and prod have the same version 3.1.5.
Hope that helps to help me. -
-
Can you send an email with the exact commands you are running and the complete message output showing the error from those commands to support at forceamp.com?
-
-
What is the complete message output from the following SQL statement:
select * from SF_CD_LINK_SERVER...Organization -
-
-
-
Hi Bill et al, Sorry for jumping in on this thread, but the problem we've encountered produces a similar error message ...
Computer 1:
We have dbamp (3.7.2.0) version running on a windows server 2008 r2 enterprise (SQL Server 12 Dev). It had been working fine until sql server was 'downgraded' from enterprise edition to developer edition ...
Computer 2:
Running dbamp (same version) as above on windows 10/sql server developer edition (SQL Server 2016)
Link servers on both machines pass the basic connectivity test to the same instance of SFDC. (Right click link server/Test Connection).
Computer 2 runs the following correctly:
Select * from OpenQuery(Salesforce_qat_dm,'SELECT count() FROM Account')
Computer 1 returns:
--expr0
--Msg 7399, Level 16, State 1, Line 1
--The OLE DB provider "DBAmp.DBAmp" for linked server "Salesforce_qat_dm" reported an error. The provider did not give any information about the error.
--Msg 7330, Level 16, State 2, Line 1
--Cannot fetch a row from OLE DB provider "DBAmp.DBAmp" for linked server "Salesforce_qat_dm".
So I'm assuming SFDC isn't the issue here.
Both machines have had their initial installations of dbamp uninstalled & reinstalled. Does the error message suggest a next course of action?
Thanks in advance,
Carl -
-
Check and make sure of the following:
1. The DBAmp.DBAmp provider options are set according to chapter 1 of the DBAmp manual. In particular, make sure "Allow in process" is checked.
2. Collation Compatible is set to true on the linked server properties. -
-
Thanks. I've passed that information to the Apps Department, hopefully that will solve it.
Turning off Allow In Process on my developer machine (Computer 2) made a big difference
I'll report back here -
-
"Turning off Allow In Process on my developer machine (Computer 2) made a big difference "
We do not recommend running DBAmp with Allow in process off. What "big difference" did it make ? -
-
Oh, sorry, Computer 2 is the machine where Dbamp *is* working fine. Allow In Process is turned on. Turning Allow In Process OFF results in the query *not* working, which was the big difference !
Sadly, it looks like our apps department may have gone home for the weekend, so I won't be able to confirm the fix until next week. Logically it makes sense running the Change Server Edition wizard may have reset things. -