Unable to Open database file (Salesforce)

[amitloh]

I am getting Unable to Open database file (Salesforce) with sharepoint list to salesforce.com.
I am using layer2 and devart dotnet connector. it works on one dev box without https.
But does not work on one of the servers where site is https

[Shalex]

Have you set the Data Cache and Metadata Cache connection string parameters to the folders, to which your account has the read/write access in the deployment environment?

[amitloh]

Hi Oleksandr,

I am not sure where to put connection string.
I have a sharepoint list, layer2 salesforce connector and your adaptor. Its working fine in my local box but not on our server.
The configuration on local and server is same

[amitloh]

It says connected from my local dev box but on actual demo server(same deployment) it says unable to open database file

Connected to: -https://login.salesforce.com/services/Soap/u/32.0 (Devart.Data.Salesforce). Connection server version: 1.0.0.0

[amitloh]

I have added custom field in salesforce, but it does not show in select statement.

[Shalex]

I have a sharepoint list, layer2 salesforce connector and your adaptor. Its working fine in my local box but not on our server.

You notified us by email that the issue is solved.

I have added custom field in salesforce, but it does not show in select statement.

The reason of the problem with column availability in client application is that your local metadata cache is out-of-date: http://www.devart.com/dotconnect/salesf ... rview.html. In this case, there are alternative ways to solve the issue:
1) execute the code:

Code: Select all

    SalesforceConnection conn = new SalesforceConnection(connString);
    conn.Open();
    conn.Cache.RefreshMetadata();

2) the "Refresh Metadata=true;" connection string parameter causes a refresh of Salesforce metadata each time when the connection is opened. Leads to the performance loses

3) remove the C:\Users\YOUR_OS_USER_NAME\Application Data\*.db files. dotConnect for Salesforce will recreate them on the next connection.Open().

[amitloh]

that fixed it