Sharepoint Foundation 2010 compatibility with SQL Server 2014

Due to a requirement to use Sharepoint without Active Directory access. I am trying to find explicit confirmation whether Sharepoint Foundation 2010 is compatible with SQL Server 2014. I have seen that Sharepoint Server 2010 and 2013 are compatible
with SQL Server 2014 as of CU 1 (released in April). But there is no mention of Sharepoint Foundation.
This chart is great except it doesn't mention whether the Foundation versions are supported.
http://msdn.microsoft.com/en-us/library/gg492257.aspx
Thanks.

Note that that is for the Reporting Services component, but not necessarily for the SQL Database Engine component (which comes from the SharePoint Product Group, rather than the SQL Product Group). I haven't seen any confirmation that SharePoint 2010 is
supported at all with SQL 2014 as a Database Engine.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Similar Messages

DB-Library BCP issue with SQL Server 2014

Hello,
My application uses DB-Library (ntwdblib.dll) to communicate with SQL Server 2014. We are having issues calling bcp related functions like bcp_init which always returns FAIL status. Our application was working fine with SQL Server 2012 and all other previous
SQL releases. But we are getting below error in SQL 2014,
msg 4801, state 1, severity 16 : Insert bulk is not supported over this access protocol.
Can anyone please help ?
Thanks,
Himanshu

Hi Himanshu_kus,
Is this still an issue, or can we close the thread?
[Personal Site] [Blog] [Facebook]

Error in VS2010 when connecting with SQL Server 2014

I have SQL2014 Express installed locally but it is not detected by VS2010. Why would I need to have the 2008 version?

http://blogs.msdn.com/b/webdev/archive/2010/05/03/visual-studio-2010-support-with-sql-server.aspx
It proably only goes to SQL 2008. I don't recall pointing VS2010 to SQL Server 2012 either.
Maybe, you should post to the below fourm.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=visualstudio

RDS 2012: Compatible with SQL Server 2014 AlwaysOn?

Is Remote Desktop Services 2012 R2 compatible with SQL Server 2014 AlwaysOn Availability Groups? Are there any procedural documents available for RDS requirements on how it expects AlwaysOn to be configured?
Thanks

Hi,
Thank you for posting in Windows Server Forum.
As per my research, we can install SQL server 2014 on RDS Server 2012\R2, you can check below article with step by step guide.
How to install SQL Server 2014
In addition for SQL AlwaysOn Consideration there is useful blog (RDS 2012 SQL AlwaysOn Considerations) you can go through for details.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Sql server 2005 reports with sql server 2014

Can i upload SSRS 2005 reports as it is on SSRS 2014 and use it without doing anything extra or without changing anything ??
I can use SSRS 2005 reports as it is with SSRS 2012. But for SSRS 2014 not sure.
h2007

You can upgrade the the RDL schema will be upgraded.
Report definition (.rdl) files are automatically upgraded in the following ways:
When you open a report in Report Designer in SQL Server Data Tools (SSDT), the report definition is upgraded to the currently supported RDL schema. When you specify a SQL Server 2008 or SQL Server 2008 R2 report server in the project properties, the report
definition is saved in a schema that is compatible with the target server.
When you upgrade a Reporting Services installation to a SQL Server 2014 Reporting Services (SSRS) installation, existing reports and snapshots that have been published to a report server are compiled and automatically upgraded to the new schema the first
time they are processed. If a report cannot be automatically upgraded, the report is processed using the backward-compatibility mode. The report definition remains in the original schema.
Reports are not upgraded when you upload a report definition file directly to the report server or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
After a report is upgraded locally or on the report server, you might notice additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying
problems in the report are detected. For more information, see Reporting Services Backward Compatibility.
For more information about new features for SQL Server 2014 Reporting Services (SSRS), see
What's New (Reporting Services).
Check the below Microsoft link for more information
http://msdn.microsoft.com/en-us/library/ms143674.aspx
Mudassar

How do I set up OCR on PDF's to integrate into Sharepoint Foundation 2010 on my SBS2011 Server?

I'm going to give an overview of my situation, and what I need to accomplish as a final goal.
I am administering a small network for a local firm. We are running Windows Small Business Server 2011 (Windows Server 2008 R2, and Sharepoint Foundation 2010) and 6 new Windows 7 workstations. We have a network copier installed in a central
location, which is the only place we get incoming scans. When we scan, we currently choose which desktop is our destination, and each user retrieves their scans independently, and does as they wish. Each workstation also receives PDF's through
email.
We need a solution which would allow us to use our scanner and send to a single location for all incoming scans. Then have that location OCR the scans into readable PDF's, and have those PDF's transferred to a folder on our Sharepoint Server.
We also need the same ability from incoming emails, or any existing PDF's we have.
This needs to be an extremely user friendly role on the client side, being as the users are not computer literate. If there is a button in outlook that says Send to sharepoint, and it automatically sends them to the OCR server, which forwards them
into Sharepoint that is perfect.
Our current server (i7-2700k, 32gb ram) is already slow with everybody on sharepoint and using the library. If there is software that can install on it and be directed to run the batch in the off hours, we can use the existing server, otherwise
I believe we will need an OCR scanner, being as the processes are CPU intensive.
Thoughts, ideas, what do I do?!... Our budget is less than $4000 and Windows Server skill level is 5/10. 1/10 being a complete n00b, 5/10 being as I got this thing setup entirely having never done it before, knowing only what I know from years of being
a PC repair tech. For this reason, I prefer an option with a company supporting it.

Hi,
Maybe a 'little' too late, but you could use Udocx
for this. With this application you get the same buttons to scan to SharePoint folders on the scanner and the pc, making it very user friendly.
Processing the scans/emails/documents to searchable PDF files is done in the cloud. This makes the documents accessible almost instantly, instead of having to wait till the off hours. There's no need to install software, and our solution is easily within
your budget. Furthermore, you can benefit from our in-house support.
Take a look at the Udocx website: www.udocx.com
Cheers
Iris
Iris vH

SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.) Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
specifically listed as a SQL DB user tries to use the front end they get an error of:
Microsoft SQL Server Login
Connection failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
Thanks a billion in advance ----

Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
all other roles, as well as allowing select only, and still have no access for the guest account.
The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
thru MS Access ACCDB, using a (by default) read only OCDB connection.
This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
since the result set would involve hundreds of thousands if not millions of records.
So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
as well as running our network on Microsoft's network software.

Sharepoint 2013 SSRS Interaction with Sql Server 2012 Reporting Services connecting to Sql Server 2008 R2 database

Hi
I'm working on upgrading sharepoint 2010 to sharepoint 2013 with sql server 2008 r2. I've ran into some problems but have been able to get a test farm upgraded. However to run SSRS 2013 it seems Sql Server 2012 Reporting Services are required. Upgrading
to a full sql server 2012 database isn't an option. I know that sql server 2012 reporting services can use sql server 2008 r2 as a catalog and content database so I was wondering could this be a workaround? Importantly would I need a separate machine/virtual
machine to host sql server 2012 reporting services? or could it live on the sql server 2008 r2 machine? Any pointers appreciated. Thanks Dan

Remember that SSRS must be deployed on the SharePoint server. Having said that, yes you can install SSRS 2012 SP1 on a server running SQL 2008 R2. And yes, you can use 2008 R2 as your Database Engine server while SSRS 2012 SP1 runs on the SharePoint server.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

RoboSource Control 3.1 compatibility with SQL Server R2

Are there any compatibility issues between RoboSource Control 3.1 and SQL Server 2008 R2?
We are looking to upgrade the server on which our repository resides.
Appreciate any input!!

According to this KB article SQL Server 2008 is not supported. I've also seen similar posts to yours in the past asking whether anyone has got RSC 3.1 to work with SQL Server 2008 but no one responded. To be honest there aren't a huge bunch of RSC users here.
The RoboColum(n)
@robocolumn
Colum McAndrew

Is SSRS 2012 compatible with SQL Server 2014?

Will it still work if a DW database is in SQL Server 2014 but the reporting services is in SSRS 2012?

Very likely. If not, probably will be at the next service pack.
Kalman Toth Database & OLAP Architect
T-SQL Scripts at sqlusa.com
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Sap b1 compatibility with SQL server 2008

Hello Experts
i have installed Sql Server 2008 in my system
and when installing SAP Business One server setup
the database selection is not coming .Where we can select MSSQL 2008 am not getting that selection of sql .
Thanx in advance
Regards
Krishna Vamsi

hi krishna
if u are nor getting the selection for sql i would like to ask u whether u can work on sql or not there could be one easy way out it has to be a problem with the installation of sql is it possible for you to reinstall sql that would solve problem.
Regards,
Manish

Database Ownership gets messed up with SQL Server 2014 AlwaysON

Hi All,
I am trying to build a nightly refresh process for SQL Server DB from on premise to Azure Cloud (IAAS). The Azure infrastructure is configured as 2 node always on. Every Day a new DB get created with retention period of 7 days. (Another script which deletes
old DB)
Nightly Build Process as Below:
1) DB Backup get copied to Azure Blob Storage
2) Restore DB on primary Server on Azure
3) Change DB owner to appropriate login on primary Server
4) Backup DB/Log from primary Server and restore it on Secondary Server.
5) Add DB to alwayson temp Group.
6) Failover temp Group and change DB owner to appropriate login. (Application Dependency to have login ID as the owner of the DB).
7) Failback and remove DB from temp group and add it to appropriate group.
During this process somehow the DB ownership gets messed up randomly either on primary or Secondary.
I can handle the primary server ownership mess-up by adding piece of code to set the ownership in the end, but for secondary I can't change the ownership as the DB is in readonly mode, resulting, when failover happens the application fails to open default DB.
Any lead on the solution would be appreciated.
Thanks,
Viral Shah
Thanks - Viral

Are you using contained databases? If not, is the login on your primary server on Azure the same as the login from your on-premise SQL Server instance as per this
KB article? Keep in mind that SQL Server looks at SID values and not login/password combination. If the login exists on both servers and the database backup is restored, it carries with it
the login SID assigned as the DB owner
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SharePoint Foundation 2010 SP2 running on Windows Server 2012 R2

Hello
I have upgraded a standalone Windows Server 2008 R2 running SharePoint Foundation 2010 SP2 to Windows Server 2012 R2. The upgrade completed OK and SharePoint Foundation 2010 SP2 is running OK as before upgrade.
Is anyone aware of any issues running SPF 2010 SP2 on WS2012 R2?

Hi
no issues using SP2
For more details check this official doc
http://support.microsoft.com/kb/2724471
Romeo Donca, Orange Romania (MCSE, MCITP, CCNA) Please Mark As Answer if my post solves your problem or Vote As Helpful if the post has been helpful for you.

MS SQL Server 2014: Error inserting into Temp table with index and identity field

In this thread, I mentioned a problem with SQL Server 2014:
SQL Server 2014: Bug with IDENTITY INSERT ON
The question was answered, it is a bug. To keep you informed on this issue, I open this discussion.
Problem:
The code below works perfectly fine on MS SQL Server 2008 R2 and MS SQL Server 2012, but gives an error every second time the proc is executed on MS SQL Server 2014. If I do not define any index on the temp table, the problem disappears. Defining the index
after the insert, does not help.
SET NOCOUNT ON
GO
IF EXISTS (SELECT 1 FROM sys.procedures WHERE name = 'usp_Test') DROP PROC dbo.usp_Test;
GO
CREATE PROC dbo.usp_Test AS
BEGIN
SET NOCOUNT ON
CREATE TABLE #Source(ID integer NOT NULL);
INSERT INTO #Source VALUES (1), (2), (3);
CREATE TABLE #Dest (ID integer IDENTITY(1,1) NOT NULL);
CREATE INDEX #IDX_Dest ON #Dest (ID);
PRINT 'Check if the insert might cause an identity crisis';
SELECT 'Source' AS SourceTable, * FROM #Source;
SELECT 'Destination' AS DestTable, * FROM #Dest;
SET IDENTITY_INSERT #Dest ON;
PRINT 'Do the insert';
INSERT INTO #Dest (ID) SELECT ID FROM #Source;
PRINT 'Insert ready';
SET IDENTITY_INSERT #Dest OFF;
SELECT * FROM #Dest;
DROP TABLE #Source;
DROP TABLE #Dest;
END;
GO
PRINT 'First execution of the proc, everything OK';
EXEC dbo.usp_Test;
PRINT '';
PRINT 'Second execution of the proc, the insert fails.';
PRINT 'Removing the index #IDX_Dest causes the error to disappear.';
EXEC dbo.usp_Test;
GO
DROP PROC dbo.usp_Test;
GO

There is some progress. Communication from a former Microsoft employee tells us this:
Shivendra Vishal
Engineer at Microsoft
I am no longer with MS, and I do not have code access, however from the public symbols, I could make out following:
sqlmin!SetidentI2I4+0x1f3:
000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] ds:00000000`00000000=????????????????
ExceptionAddress: 000007fef4d865d3 (sqlmin!SetidentI2I4+0x00000000000001f3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
This is a read AV and from registers it is clear that we were trying to move the value of location pointed by qword of register rax which is not valid:
rax=0000000000000000 rbx=0000000000000038 rcx=0000000000001030
rdx=0000000000000006 rsi=00000001f55def98 rdi=00000000106fd070
rip=000007fef4d865d3 rsp=00000000106fcf40 rbp=00000000106fcfe9
r8=0000000000000000 r9=00000001f55def60 r10=00000001f55defa0
r11=00000000106fcd20 r12=0000000000000000 r13=0000000000000002
r14=00000001f49c3860 r15=00000001f58c0040
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
The stack is:
# Child-SP RetAddr Call Site
00 00000000`106fcf40 000007fe`f30c1437 sqlmin!SetidentI2I4+0x1f3
01 00000000`106fd050 000007fe`f474e7ce sqlTsEs!CEsExec::GeneralEval4+0xe7
02 00000000`106fd120 000007fe`f470e6ef sqlmin!CQScanUpdateNew::GetRow+0x43d
03 00000000`106fd1d0 000007fe`f08ff517 sqlmin!CQueryScan::GetRow+0x81
04 00000000`106fd200 000007fe`f091cebe sqllang!CXStmtQuery::ErsqExecuteQuery+0x36d
05 00000000`106fd390 000007fe`f091ccb9 sqllang!CXStmtDML::XretDMLExecute+0x2ee
06 00000000`106fd480 000007fe`f08fa058 sqllang!CXStmtDML::XretExecute+0xad
07 00000000`106fd4b0 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
08 00000000`106fd5f0 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
09 00000000`106fd7e0 000007fe`f152cfaa sqllang!CSQLSource::Execute+0x86c
0a 00000000`106fd9b0 000007fe`f152c9e8 sqllang!CStmtExecProc::XretLocalExec+0x25a
0b 00000000`106fda30 000007fe`f152a1d8 sqllang!CStmtExecProc::XretExecExecute+0x4e8
0c 00000000`106fe1e0 000007fe`f08fa058 sqllang!CXStmtExecProc::XretExecute+0x38
0d 00000000`106fe220 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
0e 00000000`106fe360 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
0f 00000000`106fe550 000007fe`f0902267 sqllang!CSQLSource::Execute+0x86c
10 00000000`106fe720 000007fe`f0909087 sqllang!process_request+0xa57
11 00000000`106feee0 000007fe`f2bf49d0 sqllang!process_commands+0x4a3
12 00000000`106ff200 000007fe`f2bf47b4 sqldk!SOS_Task::Param::Execute+0x21e
13 00000000`106ff800 000007fe`f2bf45b6 sqldk!SOS_Scheduler::RunTask+0xa8
14 00000000`106ff870 000007fe`f2c136ff sqldk!SOS_Scheduler::ProcessTasks+0x279
15 00000000`106ff8f0 000007fe`f2c138f0 sqldk!SchedulerManager::WorkerEntryPoint+0x24c
16 00000000`106ff990 000007fe`f2c13246 sqldk!SystemThread::RunWorker+0x8f
17 00000000`106ff9c0 000007fe`f2c13558 sqldk!SystemThreadDispatcher::ProcessWorker+0x3ab
18 00000000`106ffa70 00000000`775d59ed sqldk!SchedulerManager::ThreadEntryPoint+0x226
19 00000000`106ffb10 00000000`7780c541 kernel32!BaseThreadInitThunk+0xd
1a 00000000`106ffb40 00000000`00000000 ntdll!RtlUserThreadStart+0x21
Unassembling the function:
000007fe`f4d8658e 4c8b10 mov r10,qword ptr [rax]
000007fe`f4d86591 4533e4 xor r12d,r12d
000007fe`f4d86594 410fb7d5 movzx edx,r13w
000007fe`f4d86598 4533c9 xor r9d,r9d
000007fe`f4d8659b 4533c0 xor r8d,r8d
000007fe`f4d8659e 488bc8 mov rcx,rax
000007fe`f4d865a1 4489642420 mov dword ptr [rsp+20h],r12d
000007fe`f4d865a6 41ff5230 call qword ptr [r10+30h]
000007fe`f4d865aa 8b5597 mov edx,dword ptr [rbp-69h]
000007fe`f4d865ad 4c8b10 mov r10,qword ptr [rax]
000007fe`f4d865b0 4489642438 mov dword ptr [rsp+38h],r12d
000007fe`f4d865b5 4489642430 mov dword ptr [rsp+30h],r12d
000007fe`f4d865ba 458d442401 lea r8d,[r12+1]
000007fe`f4d865bf 4533c9 xor r9d,r9d
000007fe`f4d865c2 488bc8 mov rcx,rax
000007fe`f4d865c5 c644242801 mov byte ptr [rsp+28h],1
000007fe`f4d865ca 4488642420 mov byte ptr [rsp+20h],r12b
000007fe`f4d865cf 41ff5250 call qword ptr [r10+50h]
000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] <=================== AV happened over here
000007fe`f4d865d6 488bc8 mov rcx,rax
000007fe`f4d865d9 4c8bf0 mov r14,rax
000007fe`f4d865dc ff5268 call qword ptr [rdx+68h]
000007fe`f4d865df 488d55e7 lea rdx,[rbp-19h]
000007fe`f4d865e3 4c8b00 mov r8,qword ptr [rax]
000007fe`f4d865e6 488bc8 mov rcx,rax
000007fe`f4d865e9 41ff5010 call qword ptr [r8+10h]
000007fe`f4d865ed f6450a04 test byte ptr [rbp+0Ah],4
I remember few issues with scan2ident function, I am not sure if they have fixed it however it appears that this is intoduced to SQL 2014 and we need help from MS to get this resolved as it needs code analysis.
It is not getting simulated for other versions of SQL apart from SQL 2014.
Also to add, interestingly, the value of rax is not visibly changed and it was successfully passed on to rcx, which has a valid value, so something should have changed the value of rax inside call to function using call qword ptr [r10+50h], and looking at this
it appears that it might be a list of functions and we are going at particular offset [50h]. So, bottom line is that the call to function qword ptr [r10+50h], should be changing something in rax, and debugging/analyzing this code might give us some more idea.

SharePoint Foundation 2010 Workspace problem

I've installed sharepoint foundation 2010 in a Windows server 2008 R2 standard environment. I've added some site collections and added some libraries to the site pages. Ive put in various permissions and groups and tested no problem using
Sharepoint workspace 2010 on a Windows 7 32 bit client.
But when I do a remote desktop connection to another server with 2008 R2 standard installed I can't get Sharepoint workspace 2010 to work properly. It opens an account and connects to my sharepont site but in the pane to the right where I would normally
see library documents listed all that comes up is an error stating - Error: Cannot Display Tool.
Also if I try to sync I get the following error:-
The parameter is incorrect
HResult: 0x80070057 (0x386d7565)
Process: Groove.exe (ID:17936(0x00004610))
No amount of googling has found a solution, no similar postings had any resolutions.
Any help would be much appreciated

My apologies. I'd focused on the error and hadn't adequately read the information you provided on the environment. The issue is probably with using SharePoint Workspace on the remote computer, not with SharePoint Foundation.
Here is what I understand you to be doing:
You use Remote Desktop to connect to the Windows Server 2008 R2 computer, where you log in with your domain account, which is a member of the local Users group.
On the remote computer, you start SharePoint Workspace.
On the Launchbar, you click New, click SharePoint Workspace, select your site, and then click
OK.
The workspace is created and appears (from the progress bar) to download content.
When you click Open Workspace, no content is displayed. Instead, you see the "Cannot Display Tool" error.
Is that correct?
There are three areas where SharePoint Workspace is complicated to run remotely:
Where SharePoint Workspace will be run by a user other than the one installing it, it must not be lauched during the installation. This seems the most likely to be the issue, as we have seen the same failure and error at a customer site where several
users had been given a computer image created on a computer where SharePoint Workspace had been launched before image creation.
Only one user should run SharePoint Workspace (Groove.exe) at a time. (Sometimes multiple instances work, but it's not reliable.)
You need to have a local profile on the computer which is running SharePoint Workspace. SharePoint Workspace is not supported with Roaming or Temporary profiles. Usually, this problem would prevent you from starting SharePoint Workspace, but some
environments with custom permissions can lead to other errors.
SharePoint Workspace uses the current user's permissions for SharePoint server access, In the case of Forms-Based authentication, it prompts for credentials at workspace creation, but then uses the credentials in the active browser session when opening
the workspace. I think this could only be related to your problem if you are logged in as another user in your browser, and that user has access to some, but not all, of the site your workspace connects to.

Sharepoint Foundation 2010 compatibility with SQL Server 2014

Similar Messages

Maybe you are looking for