I've two 64-bit Windows Server 2008 R2 machines. On one of the machines BizTalk Server 2010 Standard Edition is installed & on the other SQL Server 2008 R2 is installed.
When I use the 'BizTalk Server Configuration' on the BizTalk machine to create the necessary databases on the SQL Server machine, just the 'SSODB' gets created & then the configuration fails due to below errors
Failed to create the SQL database 'SSODB' on SQL Server 'SQLServerName' (with SSO Administrator account 'SSO Administrators').
(0xC0002A21) An error occurred while attempting to access the SSO database.
Could not find the account name 'SSO Administrators' on computer 'SQLServerName'. Configuration can proceed, but it might fail.
(0x800706BA) The RPC server is unavailable.
A few sites suggested to register both the 32-bit & 64-bit SSOSQL.dll using the regasm command to resolve this issue & I did the same. But, the issue still persists.
What is a solution for this?
Create "Domain user accounts/user groups" before configuring and use those instead of the local user accounts/user groups. (http://msdn.microsoft.com/en-us/library/aa577661(v=BTS.70).aspx)
Add the domain user account as sys-admin on the Sql server.
Most likely the above 2 steps will help you resolve this issue.
Related
I am trying to deploy a SSDT 2012 SSIS project using Deploy option. But I am getting below error:
TITLE: SQL Server Integration Services
A .NET Framework error occurred during execution of user-defined routine or aggregate "deploy_project_internal":
System.ComponentModel.Win32Exception: A required privilege is not held by the client
System.ComponentModel.Win32Exception:
at Microsoft.SqlServer.IntegrationServices.Server.ISServerProcess.StartProcess(Boolean bSuspendThread)
at Microsoft.SqlServer.IntegrationServices.Server.ServerApi.DeployProjectInternal(SqlInt64 deployId, SqlInt64 versionId, SqlInt64 projectId, SqlString projectName)
. (Microsoft SQL Server, Error: 6522)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.5058&EvtSrc=MSSQLServer&EvtID=6522&LinkId=20476
Any idea why this error? below is the screen shot of the error.
I have faced this issue after installation of Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012. After installation I started repair option of SQL server management studio by running SQL Server Setup. After restarting SQL Server Management studio issue resolved Now I can deploy SSIS package in Integration Service Catalog.
That error often means the SQL Server Agent account is missing a permission somewhere. The "A required privilege is not held by the client" in this case means the SQL Agent account is called to do something but isn't permitted to.
One thing to try is to use the SQL Server Configuration Manager, as administrator, to reset the account for SQL Server Agent (and possibly SQL Server itself). This will reinstate the required permissions if you have sufficient rights.
I have seen cases where Group Policy prohibited the assignment of the service account to needed permissions at the OS level, which really creates a problem.
Example: http://blogs.msdn.com/b/dataaccesstechnologies/archive/2012/08/20/error-while-deploying-ssis-2012-project-from-ssdt-to-ssis-catalog-system-componentmodel-win32exception-a-required-privilege-is-not-held-by-the-client.aspx
Went through most of the other solutions but using the repair option worked.
The problem could have been due to the installation of Visual Studio and SSDT after SQL was installed.
Would be nice if MS provided better support for their products rather than leaving to the community to fix the problem.
According to this Blog the required User Right may be
"Replace a process level token"
https://www.oraylis.de/blog/fixing-sql-2012-ssis-deployment-error-6522-a-required-privilege-is-not-held-by-the-client
I am creating my first SSIS package using Business Intelligence in Visual Studio 2012. I am adding the contents of an Excel sheet to an local VS database. In the Destination Assistant I am asked Destination Type = SQL Server, New: Provider - I see no .NET Framework option. The result seems to be that I am then unable to select my server and therefore databases.
Am I just missing the point?
I would recommend that you investigate the destination server and verify that you have the providers installed on that system. Typically these are installed at the time that SQL server is installed, but is possible via custom installation to specify the providers that are installed. It may be necessary for you to install any providers needed. A second option would be to point to a database that you know that you can connect to, say a localhost sandbox or other tried database. That would help you to determine if it's server side or client installation issues.
I have two virtual machines runs on my laptop, let's say their name are VMApp and VMDB, and both are runs the same OS, Windows Server 2008 R2.
On VMDB, I installed all SQL Server 2008 features except the Reporting Services. in contrast, I installed only SQL Server 2008 Reporting Services on VMApp.
I run Reporting Services Configuration Manager on VMApp and point the Server Name to the VMDB's computer name, then I got an error message
"A connection to the computer cannot be established"
I enabled the named pipe from SQL Server Configuration Tools on VMDB, but I still get that error message on VMApp.
I think the problem is not network connection because the VMs are connected in same domain network and they could ping each other.
Sorry for this dumb case because I am newbie in SQL Server, and I really appreciate any help from you guys!
Regards,
Chrisma Andhika
You cant set the DB path to SERVERNAME\INSTANCENAME on the configuration manager. There isnt even that option. First you set the server:
and then the DB:
where exactly are you having your issue?
FYI: try to enable SQL Browser on VMDB or to connect by IP if you cant enable browser
Having trouble getting my local IIS7 running C # MVC app to connect to a newly installed Sql 2008. IT was working wiht SQL Express, but we upgraded every machine to full SQL. Now, just my machine, will not connect to SQL 2008.
Followed many websites info, fooled wiht the user account both in IIS7 and SQL2008. Setting permissions to the DB's with db_owner(actually selected every permission) just not connecting.
I noticed the w3wp.exe service is not running. Not sure if that is the issue or if it was even running before.
Messed with the and tried all the sugeestions and tutorials out there that had to do with
Application pools are running, their set to the proper settings
IIs Account NetorkServices
Sql NT AUTHORITY\NETWORK SERVICE
created users for IIS APPPOOL\ASP.NET v4.0
When i check the sql logs there is no sign of it even trying to connect. The only message i get is when i restart IIs. Just says starting and stopping.
Been thru this before when i first tried to connect to SQL express, and was not this hard, and i did not touch anything in IIs when i installed sql 2008. So it should have connected.
Any other suggestions out there?
LLBL DataAccessAdapter should have string property ConnectionStringKeyName which contains app settings key (in web.config), which contains connection string. Visual studio does not use that connection string and you being able to connect to db from VS does not mean that connection string your application uses is valid.
Indirectly you lead me to the solution. lol
Started searching on running IIs and Sql 2008 on the same machine.
Running on a Win7 64bit, IIS7 an sql2008 R2.
Long story short, after hours and hours of fighting with IIS and SQL.
IIS7 --> Application Pools --> Select your pool --> Advanced settings --> General tab --> Enable 32-bit Applications set to true.
How it got to false, or why sqlexpress worked and sql2008 did not, not sure. But this fixed the issue.
I've installed sql2008 express sp1 on my laptop that's running the beta 1 of windows 7. The problem that I'm experiencing is a combination of dynamic ports/firewall/windows 7.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I was first experiencing this problem when I was trying to connect to sql with the management tools, but as soon as I enabled Sql Server Management Tools as a program to go through the firewall it worked out fine. Now the problem is when I launch my web site it gives me that error. I've also positive that sql browser is running and I've enabled tcp/ip and named pipes in the sql express service.
So does anyone have any thoughts as to how to resolve this?
Are you using the same instance name in both SSMS and your web application?
Commonly, people will try to connect based upon the machine name exclusively, for instance "MySQLServer". SQL Server Express installs a named instance by default, whose default name is SQLExpress. If this is the case, try connecting to "MySQLServer\SQLExpress" instead (omitting the quotes, of course).
Go into SQL Server Configuration Manager - under Programs - Microsoft SQL Server 2008 - Configuration Tools - and make sure that under SQL Server Network Configuration - Protocols for SQLExpress, that Named Pipes is enabled (by default it is not).
Yes, I'm aware of both scenarios. I've setup as a named instance and as a default instance as well, and adjusted the connection strings, neither worked.
I've also enabled named pipes and no go. It has everything to do with windows 7 firewall, but couldn't figure it out so I just installed server 2008 standard edition and voila.
I suspect the fact that it uses dynamic ports is another issue with windows 7.