in install SQL SERVER 2008 R2
when i cereate a databse diagram
following error is coming
serach on google then i fcound go to database properties but i Cant find database properties in this
in install SQL SERVER 2008 R2
when i cereate a databse diagram
following error is coming
serach on google then i fcound go to database properties but i Cant find database properties in this
Hi,
I'm trying to add reporting services to an existing 2008 R2 instance as a pre-requisite for a fresh CRM 2011 installation. I figured out that the "Installation Type" page that allows adding features to an existing instance does not show up. This is an SQL Server 2008 R2 Enterprise installation and the Data-base Engine is up and running and being used by SharePoint. The OS is Windows Server 2008 R2 with all updates installed.
Tried to run setup "as administrator", but didn't help. Tried Add/Remove from control panel, but no difference. Seems that the setup routine does not recognize the instance initially. Is there any command line switch that forces the Installation Type page to appear?
I'd be thankful for any hints.
So it's patching time this weekend again, and I am spending time waiting for reboot to finish between service pack installation, before I can start the cumulative update installation. So I thought I will ask this question:
I know that you can slipstream Service packs and Cumulative updates during the initial install. But is there a way to slipstream a CU with a SP install, independent of the RTM ?
Example:
I need to patch my SQL Server 2008 to SP3 and also apply CU9. Is there a way to achieve this patching using slipstream in one step?
Current.ly my process is
<> Install SP3. Reboot.
<> Install Cu9. Reboot.
Can I do SP3+CU9 and reboot just once? I am guessing not. But doesn't heart to ask, right?
Thanks,
-Aditya
Hi,
I have an application that uses WMI to determine the configuration of SQL Server instances in a computer. I have 2 versions of SQL Server installed, SQL 2008 R2 Express and SQL 2012 Express. Everything works fine until I uninstalled SQL 2012, now I'm receiving this error:
************** Exception Text **************...
*****************************************
First, I thought this could be a problem only in my computer, however I was able to replicate this error consistently on other computers.
Then I also used "wmiexplorer" to browse SQL WMI, although "wmiexplorer" did not throw an exception, it did not show any information
The error did not occur on SQL 2008 R2 uninstall when I tried it in different computers.
WMIExporer link: http://www.ks-soft.net/hostmon.eng/wmi/index.htm
Thanks.
Regards,
Dalahira
I keep getting this error when I try to install, repair or uninstall SQL 2012 which won't run because of another error? Here is the error..
sql server has encontoiured the following error:
Could not load file or assembly \\\ C:/program files/microsoft/sql server/ 110 blah blah blah huge path / Microsoft.SQLserver.Configuration.Setup.Extension.DLL Error Code 0x84b10001
I'm also not able to open SQL server management studio 2012. I have Management Studio 2008, but I need 2012 for my remote host which is using 2012. So, when I try with 2008 to open my db at the host, I get an error that I need 2012. This is driving me nuts..
I'm running Windows 7 Ultimate with 8gig of ram, solid state drive, on a lap top, latest updates, etc,. I also have VIsual Studio 2012 Pro, Webmatrix, and everything else works fine. Just this one damn SQL server Management studio that I need for it's visual tools to do relationships with, etc, and it doesn't work. Any help would be most appreciated.. I'm going to try to update SQL server again and the computer in general to see if that helps..
A search gives me a lot of stuff about 2008 sql, but nothing with the same error, so I'm afraid to try those solutions since they don't seem to be the same problem as I'm having!
Tim
Tim
Hello,
I'm shortly to be upgrading a SQL Server 2005 instance to SQL Server 2008 R2 on a Windows 2003 R2 box. Whilst following suggested practice I ran the Upgrade Advisor and got the following issue reported "
Method not found: 'System.Collections.Generic.IEnumerable`1<Microsoft.SqlServer.Management.SqlParser.Parser.Error> Microsoft.SqlServer.Management.SqlParser.SqlCodeDom.SqlCodeObject.get_Errors()'. |
". This was for many commands such as DROPSYSOBJ, OUTPUTINTOFULLTEXT, OLDSYSTEMTABLES, DUMPLOAD, MERGE, ...
The status of these issues is critical and it is suggested that they be resolved prior to the upgrade, but I don't know what the issue means let alone how to resolve it. Can anyone shed any light on this for me please?
Mike
I am on SQL Server 2008 R2 on Windows 7. I want to rebuild my master database (this is for learning) using
setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=PREMTESTCOMPUTE\pmehrotr /SAPWD=xxxxxxx
When I run this command, I get error:
Final result: Failed: see details below
Exit code (Decimal): -2068643838
Exit facility code: 1203
Exit error code: 2
Exit message: The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for further details.
Requested action: RebuildDatabase
I have looked in various summary log files in Setup Bootstrap \Log drcetory and I cannot find the roort cause as something missing, do not have premssions etc. In different files it shows the same exit message; so it is frustrating how to troubleshoot this problem. I have also looked in event viewer and no information related to this error.
My database instance MSSQLSERVER has several accounts with sysadmin role. I just sepcified one:
setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=PREMTESTCOMPUTE\pmehrotr /SAPWD=xxxxxxx
Hello all,
I am planning to try to move some SQL2005 and SQL2008 from a 2nodes (VMs) to another 2nodes (physical).
A. What I plan to do is :
1. add physical machines as 3rd and 4th node of Windows cluster and form a 4node Windows cluster
2. stop all scheduled user created jobs (backups etc.)
3. for each instance existing, run on 1st physical machine (3rd node) the "add node" for all existing SQL2005 and SQL2008 failover clustered instances (FCIs) and Service Packs
4. for each instance existing, run on 2nd physical machine (4th node) the "add node" for all existing SQL2005 and SQL2008 failover clustered instances (FCIs) and Service Packs
5. one-by-one, faiolover the instances from VMs to physical nodes and do all the ckecks for the health of the system. If ok run backups and continue failover the next one. If there is anything wrong failback check and retry.
6. Run backups, enable jobs
the tricky part is that the systems is a live system.
we plan to do the installations during non-maintenance window an do the failover inside maintenance window.
Is there anything causing the SQL Server to actually failover DURING sql setup of "add node"? (e.g.: cluster validation before addign to cluster)?
B. We have all kind if services to be installed, includingn SSAS, SSIS, SSRS and thye already exist in VMs in one resource group per instance. I guess that during each "add node" run per instance they are all going to be installed at once for this instance, right?
C. anything special we should be aware of?
thank you very much!
kind regards, Thomas G. Apostolou
We have an InstallShield installation package that spawns an installation of MS SQL Server 2008 R2, depending on what components the user selects to install. This has worked fine, but now we need to support Windows Server 2012 and Windows 8, so we want to
distribute SP2 of SQL Server 2008 R2 Express Edition instead of the original SP1. The only difference made to the installation package is to replace the redistributable of SQL Server R2 Express Edition SP1 with SP2. If the SP1 version is used Windows 2012
and Windows 8 will popup a message saying that there is compatibility issues with that version of SQL Server.
When the installation package use SQL SP2 the SQL Server installation starts, extracts files etc and and begins the installation, but then freezes at the step ExecuteStandardTimingsWorkflow displayed in the installer UI.
There is no significant CPU usage and no increase in memory by any process like msiexec or similar and there is no error message displayed.
It is not possible to cancel the installation either (cancel button disabled). Reviewing the SQL Server log files shows the following lines in the Detail_ComponentUpdate log
2012-08-23 08:33:06 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\9.0
2012-08-23 08:33:06 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
2012-08-23 08:33:06 Slp: Sco: Returning service status Running
2012-08-23 08:33:11 Slp: Sco: Returning service status Running
2012-08-23 08:33:16 Slp: Sco: Returning service status Running <- repeated indefintely until the installer is killed in task manager
When using SP1 the same log files says the following
2012-08-23 11:00:57 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\9.0
2012-08-23 11:00:57 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
2012-08-23 11:00:57 Slp: Sco: Returning service status Stopped
The problems appears to be that the installer cannot shutdown the msiserver service and just loops indefinitely.
The following conditions apply to all tested machines which is Windows 8, Windows Server 2012 RC, Windows Server 2008 R2
Machine is clean, no existing versions of SQL Server exists prior to installation. All security updates etc. applied.
Logged in user is local administrator.
Installation is successful if the SP1 version of SQL Server 2012 is used instead of the SP2 version
The SP2 version can be installed successfully from the command prompt (run as administrator). In this case I use the following command
line (replaced password with ****):
SQLEXPR_x86_ENU.exe /ACTION=install /INSTANCENAME=PRODACAPO /IACCEPTSQLSERVERLICENSETERMS /HIDECONSOLE /QUIETSIMPLE /SECURITYMODE=SQL /SAPWD=**** /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
Display language is US English and SQL Server package is US English. Input/keyboard language is Swedish.
Windows Installer service cannot be shutdown from services as Stop and Restart options are disabled.
No summary.txt file is created when the installation freezes
Are there any changes in the behavior of the installation package from SP1 to SP2? Since SP1 works it seems that InstallShield cannot be blamed for this problem? However, installing from the command prompt works which means that the problem seem to lie in with
how the SQL installation is spawned from InstallShield. Currently this problem is preventing us from supporting Windows Server 2012 and Windows 8 properly.
If you need any log files or other info I can provide that promptly.
Related problems for other users:
http://stackoverflow.com/questions/11741803/fail-to-install-sql-server-2008-r2-as-a-feature-pre-requisite-in-a-wix-project
http://social.msdn.microsoft.com/Forums/en-NZ/sqlsetupandupgrade/thread/ce69b4e1-939f-4a64-9b44-e6ffdad3b9c8
The SP2 redistributable I use can be downloaded from here (SQLEXPR_x86_ENU.exe):
http://www.microsoft.com/en-za/download/details.aspx?id=30438
Thanks
Fredrik
Frede
I'm trying to install MSSQL 2008r2 Enterprise edition. Getting the following error message
The following error has occurred:
An error occurred during the installation of assembly
'Microsoft.VC80.MFCLOC,version="8.0.50727.4027",publicKeyToken="1fc8b3b9a1e18e3b",processorA
rchitecture="x86",type="win32". Please refer to Help and Support for more informatio. HRESULT:
0x800703F9.
All the articles I can find refer only to Windows Vista as it relates to the 0x800703F9 error.
I am running Windows 7 Enterprise, 4GB RAM and Quad Core Processor.
It was installed successfully previously. Had to uninstall to demo an install and it will not install again. I have also tried SQL Express,
Developer edition.
I have been fighting this and other SQL issues for almost 3 weeks now. I have searched all over the web and tried many of the solutions including sfc /scannow (which threw an error as well). I've tried uninstalling and re-installed .NET 4.0 (had issues with that). I'm just so frustrated. All I want is to install SQL and get my front end software running again.
Hi Team,
Am unable to view Databases for SQL Server 2000 in Enterprise Manager.
REquesting you all to help/advice me on the same, I am attaching my screenshot of the error message.
I have a install for my software that depends on SQL. I want to install SQL 2008 or 2012 express versions if SQL does not exist on the system. However, it is possible and likely that the system has been configured in a way that causes the SQL install to fail. I want to run a pre-install check to make sure SQL has the correct permissions to install before I attempt the install. Is there a way to call the SQL install so that you can get a return of errors without actually installing SQL. Or is there a program I can run as part of my install to check the system will not block the SQL install. My ultimate goal is to problematically set the polices and permissions of the system, Install SQL and then reset the computer permissions to the way they were before the install.
I have just updated the installation of SQL Server 2008 Developer Edition on my PC to SQL Server 2012 Developer. During the process, a small dialogue box popped up asking me to insert a VS2010 CD. I was running VS2010 at the time and did not relate this dialogue box to the SS2012 installation. I therefore cancelled the dialogue box.
However, it became clear later that a VS2010-related part of the SQL Server 2012 had failed. Everything else was fine.
My problem is that that I have no idea how to fix that failure. Any advice would be much appreciated.
David
Hi All,
I have created a cube using SSDT in SQL Server 2012.
Now for deployment, I was told that the client cannot provide SQL Server 2012 and will just use SQL Server 2008 R2 Standard Edition instead.
I have tried restoring the backup file (.abf) and I got "Instance versions used are incompatible".
Is there any way or tool that can downgrade cube? Just like for db, I can use SSMS and generate script and specify the SQL Server version.
Regards,
Charllemagne