Scenario:
Installed LocalDB 2012 64bit on Win2012
Wix Installer installs a 64bit Window Service with its own DB
The service cannot connect to the LocalDB
The error in the app's log is:
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible."
The Event Log indicated that LocalDB is corrupt, however, following the normal fix of deleting and recreating instances was ineffective. I don't believe there is any corruption.
When we set the service to run as a specific local admin account, it works.
We didn't have this issue before, but we've since upgraded LocalDB and rebuilt the project and the installer.
We also didn't have this issue on Windows 7. I ran this process on my laptop and on a clean VM of Windows 7.
Does anyone know why I can't use a Local System account for LocalDB on Windows 2012?
Related
I am running Lyris ListManager on a Win 2008 server. It connects to Oracle 12c on another machine.
I have successfully configured and tested the connection using the Net Manger (or Net Configuration Assistant). However, when I run ListManger, I receive this Oracle error (TNS: could not resolve the connect identifier specified).
I checked the configuration file for the ListManager (lmcfg.txt), which correctly specifies everything.
Previously, we had Oracle 11g database, and 11g client on this server, which worked fine. DB upgrade to 12c was successful (other applications, on other servers, work fine), and I removed 11g client and installed 12c. It successfully connects to the Oracle server with the correct service ID, but Lyris ListManger application can't connect.
What am I missing here?
The root of the problem was in multiple client installations. At some point during the troubleshooting, I installed, and then uninstalled 64-bit client. After that, I installed 32-bit client and got it to connect through the Net Manager. However, that 64-bit client wasn't correctly and completely removed, and the ODBC driver was still looking at its original path for DLL libraries (which weren't there anymore).
I had to add a new ODBC driver entry for the 32-bit Oracle client. Once this was properly configured, the ListManager application was able to connect to Oracle server.
I'm trying to restore the SharePoint 2010 portal from one server to another server and using the sharepoint 2010 backup and restore powershell commands. I have take the backup successfully, while restoring I'm getting the following error.
Error:
"Restore-SPSite : Your backup is from a different version of Microsoft
SharePoint Foundation and cannot be restored to a server running the
current version. The backup file should be restored to a server with
version '14.0.0.6117' or later"
Solution:
1) Download the hot fix from this link by register your Email id
http://support.microsoft.com/kb/2597150
2) Extract the file and run the exe
Note: don't run the SharePoint 2010 Configuration wizard during the installation...
3) After successful installation Restart your system.
4) Run SharePoint 2010 Configuration wizard setup.
5) Start the restore operation once again your problem get resolved
Some time you will get rendering error
To resolve this issue go to central administration then open
farm config and start the state service
I reinstalled SQL Server Management Studio in my computer, then I'm trying to restore all backups.
Unfortunately, I get an error when trying to open one.
What should I do?, How do I set the BackupDirectory in my Settings?
I just installed Sql Server Express 2012 Sp1, and problem solved
I have Windows 7 64bit. I had Sql Server 2008 R2 Express installed. I unistalled it and then I tried to install Sql Server 2008 R2 Web. Unfortunatelly on the Setup Support Rules page for 'Consistency validation for SQL Server registry keys' I got 'Failed'. I spent half of a day trying to solve it, but then I assumed that there must be realy something wrong with registry keys and it will be faster just to reinstall Windows.
After formatting the disk and reinstalling Windows 7, rebooting dozen of times I installed all Windows upadtes as well. I also did install some programs like Skype, Thundirbird etc. which has no influence on Sql Server setup.
And then I tried again to install Sql Server 2008 R2 Web. And again an error. A bit different one. Now when the setup is on the Setup Support Rules page I get an error message box with the title "FixSqlRegistryKey_x86 - Application Error" and content: The application was unable to start correctly (0xc000007b). Click OK to close the application. 'Consistency validation for SQL Server registry keys' gets 'Failed' status as well.
My team mate has exactly the same machine as mine. He had no problem with installation (he didnt even need to reinstall Windows).
I run the setup as administrator, from a local folder. I even tried to use the setup files copied from my team mate, for a case if my copy is corrupted. In the setup options I have chosen the 'x64' version.
Any ideas what can be the reason of the problem?
Problem solved.
Someone suggested to me that Web edition should not be installed on Win 7 (just on Windows Server). So perhaps installing a different version would work. My team mate perhaps succeeded acidentially - due to having sql server installed already in express edition... but it is just a guess.
Before I tried to install another edition of SqlServer, I downloaded 2008 Express version and I started the install. From the temporary folder created by the express edition I copied FixSqlRegistryKey_x86.exe file and I had overwritten the problematic file in the Web setup with this file.
I started the setup again. It passed the verification this time. But has crashed on a later point - setup unpacks the installation files to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 and runs from it. So I needed to again overwrite the problematic file in this location. Now the installation succeeded.
I am trying to upgrade my current Express edition to Express with Advanced Services for supporting full-text search.
The current system setup is:
OS version: Windows server 2008 R2 web server 64 bit
SQL Server 2008 R2 Express, SP1, v10.50.2500.0
I have downloaded the SQL Server with Advanced Services. I am unable to upgrade the edition. The installation step goes without any issues and even getting Edition upgrade completed page. But once I click the close this page, an error will pop up.
SQL Server Setup has encountered the following error: Invoke or
BeginInvoke cannot be called on a control until the window handle has
been created.
Can some please assist me here to the right direction?
I could see that the version of SQL Server Express with Advanced Services is 10.50.1600.1. Is this the cause? So should I downgrade the sp1 to normal Express r2 edition before upgrading?
Downloaded link for the Express with advanced services http://www.microsoft.com/download/en/details.aspx?id=25174
I got it working finally!!
I was getting the below error previously. It is a bug and is related to UI. So i have upgraded using the command line that too in QUIET mode to prevent any UI intervention.
"SQL Server Setup has encountered the following error:
Invoke or BeginInvoke cannot be called on a control until the window handle has been created."
Following are the steps i used:-
Downloaded the latest sp1 for SQL Server 2008 r2 with Advanced Services (SQLEXPRADV_x64_ENU.exe) from http://www.microsoft.com/download/en/details.aspx?id=26729
Extracted the SQLEXPRADV_x64_ENU.exe to D:\SQL2008
Open command prompt as "Administrator"
Executed the following commands
D:\sql2008\setup.exe /ACTION=editionupgrade /INSTANCENAME=MyInstance /IACCEPTSQLSERVERLICENSETERMS /FEATURES=SQL,RS /INDICATEPROGRESS /Q
*MyInstance is your sql server instance name
*/INDICATEPROGRESS will show the setup progress to command prompt(For a confirmation :) )
You can follow this doc for more setup parameters
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.105).aspx
Verified the upgrade has been successful.
Unfortunately FULL-TEXT Search feature was not enabled.
So Run the setup.exe as normall(double click) and added "FULL-TEXT Search" feature to the existing instance.
Everything works fine now. Thank you all.
I can verify that this bug and the same resolution also apply to SQL Server 2008 R2 Express SP2 v10.50.4000.0