Tag Info

New answers tagged

-1

Change impersonate to false in web config file. By default it will be true. identity impersonate="false" />


0

By this morning the databases had been deleted by SharePoint. I suppose the databases are in the PowerPivot SSAS tabular instance for the duration that it is configured to be in memory in the PowerPivot settings. Also the DB for a powerpivot that I had not deleted was deleted from the PowerPivot instance, but re-created when I open the PowerPivot from ...


1

You need to check the Uls Logs(may be enable the verbos for BCS) and also check the Application logs on sharepoint server as well as on the SQL server. Most common reason for not being able to get to the database, apart from someone forgetting to plug it into the network or switch it on, is permissions. And usually the database is SQL Server and we don't ...


1

Tinkering around to fix it in the database is not recommended or supported. The old stand by is to navigate to your web part page and add ?contents=1 to the end of the URL. Here you can delete the corrupt web part. Then go back to your web part page and add it back. You can always try exporting the web part from the site it is working in and importing it ...


0

As I understand you want to make use of SQl data in a SharePoint Form without programming. You could possibly populate your external SQL data to any native SharePoint list and make use of default list lookups in your form. Looks mlike the best approach because it does nit require any programming and your users work with list data only. That makes things easy ...


-1

I have faced the same issue regarding handshake with sql server and restarting the WMI service helped me. Follow the steps below. Got to Start --> Run --> Services.msc --> Windows Management Instrumentation --> Restart the service.. It's possible that you may face the same issue after iisrest. Then you may have to restart the WMI service again and it ...



Top 50 recent answers are included