At my application I'm installing sqlexpr32.exe by doing this:
Code Block
System.Diagnostics.Process proc1 = System.Diagnostics.Process.Start(
Environment.ExpandEnvironmentVariables("%SQLHome%")+ @" sqlexpr32.exe", "/norebootchk /qb reboot=ReallySuppress addlocal=all " + "instancename=SQLEXPRESS SQLAUTOSTART=1");
proc1.WaitForExit();
proc1.Close();
when I do this for the first time the sql setup runs but gives me an error saying that the file sqlncli.msi (Native Client) was not found
but if I go to the temp directory the msi is there..
when I run the app for the second time the sqlexpr32.exe detects the Native Client setup file and does the installation perfectly..
We are upgrading our customers from MSDE to SQL Express 2005 (SQLEXPR32.EXE - not the advanced services version). However, I accidently via PCAnywhere installed the advanced version (SQLEXPR_ADV.exe); and, to make things more interesting, we want to change the name of the Server Instance from the default of SQLExpress.
I have asked in this newsgroup before, and was told that if the Advanced Services are not used, then it does not matter that it was installed on a computer without IIS. It will simply function the same as SQL Express 2005. I presume that is correct (and seems to be by experience).
Question 1) To install a new named instance, I have to run the .EXE over again. What happens if I run SQLEXPR32.EXE for a new instance when I have already run SQLEXPR_ADV.exe for the existing instance of SQLExpress? Which should I use for the new instance when I really want SQLEXPR32.EXE installed?
Question 2) Additionally, I understand how to remove an SQL instance, but how do you remove the program itself, ie SQL Express with Advanced Services? Either version of SQL Express only seems to allow you to remove instances, not the program itself.
Question 3) Does SQL Express with Advanced Servies install additional programs to manage the SQL, or does it give extra features that can be used in programing, or both?
I installed SQL Express (SQLEXPR32.EXE, not with advance services) and choose to install all components, and got the following message (the machine is Pentium 4, 2.4 GHz CPU, 512MB Ram, 100 gig drive) Minimum hardware requirement (warning) T he current system does not meet the recommended hardware requirements for this sql server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online. I looked at the SQL Books Online, and don€™t see where this system does not meet recommended hardware requirements. Any ideas what is going on? It seems to work ok. Thanks, Bob
Do we have to manually install the ODBC 3.70 drivers for SQL server 7.0, or do they get automatically installed during the SQL server 7.0 installation. I did not see anything when I installed. So I am thinking that the drivers have to be installed separately
I really don't understand this, in an attempt to upgrade/install SP3a, I download the file sql2kdesksp3.exe, which from the documentation, you can either use for upgrading or new installs. I run a new install; in the new instance, I execute "select @@version" and get "Service Pack 1"??
this may well be the wrong place for my post, if so please move it.
I have a variety of boxes with SQL tools installed on them. For some reason last week several of them seem to have gone a bit squif.
Server 1. Enterprise manager fails to run, giving message MMC could not create the snap-in. QA runs fine.
Server 2. Load EM click on a database and try Tools --> QA it comes back with File Not Found. Add isqlw as an external tool and you can run that ok, but still File Not found on the QA tab.
I know its not data corruption, but I hope someone can give me a clue on this!
I am currently attempting to install SQL Server 2005. I had to install once due to a faulty install now when I try re-install it says all components are installed and won't continue install procedure and shuts itself down. Anyone else have this issue and know the work around or fix?
I had a working SQL 2005 that I had to uninstall. I tried to verify things were cleaned up appropriately after the uninstall and rebooted afterwards.
When I went to reinstall I choose to install on another logical drive under raid 5 (lets say H:) in the EXACT same configuration as it was previously installed sans some of the services. Post-installation the data, Install etc folders you would expect to be under H:Program FilesSQL Server are actually under C:Program FilesSQL Server and the only thing installed under the H: selection was the 90/ folder. We uninstalled again and went back through the process and confirmed the selection of drive H: and AGAIN it installed it all to C:.
I completed an install of SQL 2005 SP2 on Windows Server 2003. Everything worked fine I can connect while logged into the box, while connected thru RDP. I can create databases add users without any issue. Until!!!!
I have a third party application (Tririga) which I run the install and indicate the SQL database (in this case local) The application begins to install but when I get to the point of adding the SA password the install fails. "login fails for sa) 18456 sev 8 (wrong password) but it is the same password I use to connect to the DB. So I change the sa assword and try again and it still fails. any suggestions would be nice. by the way on machines on which I have run an upgrade from 2000 (sql) to 2005 (sql) the install does not fail.
Hi,anyone could explain this : I have installed the same asp.net application on 2 distinct hosts, each with its own SQL Server 2000 database.However, in some SQL queries in Stored Procedures, the results do not come out the same.For example, on one server the query "select @value = (select ....)-(select ...)" works and on the other one it returns a null valueAny hint ?Thanks for your helpJohann
I have a quick question about automating installation of SQL 2005. This question doesn't relate as much to SQL 2005 as it does setting up a database server.
I know that it's usually standard practice to allow SQL to "lock pages in memory". What I am trying to do is find a command line utility that will allow me to add this step to the SQL install script. Any help is appreciated. Thank you.
I am trying to install SQL 2005 that came with my Visual Studio 2008 on my Vista Machine, it will install successfully, but when I want to get to say, the Management Studio, or the Configuration Manager, there is no "Microsoft SQL 2005" node in my All Programs. what gives? you kind of need those. thanks.
With Vista Ultimate (release), I installed SQL server 2005 Developer edition. I installed SP1, apparently successfully. But my Windows update history shows the SP being installed successfully every night. I have automatic updating turned on (via AD policy).
Has anyone seen this, and does anyone know how to fix it?
I nabbed a couple from some recent installs I did, and, assuming I can get my SAN guy to always give drives the same letter assignment, it looks fairly useful.
There's still a bunch of additional stuff to do, like turn on instant file initialization, size/create additional tempdb files, and set up alerts and database mail, etc.
Can the configuration file be expanded to handle any of that? Do you use something else to template/automate your SQL installs? The more I do it, the less I want to keep doing it.
I have created a setup in visual studio and set the sql server as a pre-requsites.
now when the setup is run from
setup.exe
it checks whether sql server is installed... if installed then continues otherwise install sql server express edition, now this installation is silent,
I need to set the sa password during installation of sql server . i have no option to set the password during installation, can any one help
I am intsalling SQL 2005 in an activepassive cluster. The OS is Windows 2003 with SP1. Everything installs OK but the sql server service cannot start afterwards. There are many access errors in the Security Event log - see example below - and numerous "SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. " errors in both the SQL and Application event logs. I have tried installing SQL in both mixed mode and under Windows Authentication and get the same errors. I can install SQL 2005 outside of the cluster on both nodes. Other items of note: This was a SQL 2000 cluster. I uninstalled SQL 2K, the virtual name was changed (IP remained the same) and the DNS entry was updated to reflect the new name. Early in the installation process - 3 or 4 days ago - I got a few errors about the Server Principal Name had to be updated but when I do a setspn -l the both nodes are listed and the entries look fine, though there are no entries for the sql service (MSSQLSvc). Not sure if there should be entries for the virtual name, but there aren't any for either the old or new name. Does the new virtual name need to be added to AD? Here is the security error - Event ID is 560 and it looks like there's a problem with Remote Access and is generated when trying to access either node: Category: Object Access Type: Failure Audit Event_ID: 560 User: NT AuthorityNetwork Service Object Open: Object Server: SC Manager Object Type: SERVICE OBJECT Object Name: RemoteAccess Handle ID: - Operation ID: {0,134558507} Process ID: 1516 Image File Name: C:WINDOWSsystem32services.exe Primary User Name: CM-OHCO-DS006B$ Primary Domain: SWNA Primary Logon ID: (0x0,0x3E7) Client User Name: NETWORK SERVICE Client Domain: NT AUTHORITY Client Logon ID: (0x0,0x3E4) Accesses: Query status of service
One other informational message that may be of use - looks like there's a problem with dll's for remote access, though this isn't pertaining to SQL: The description for Event ID ( 0 ) in Source ( srmservice ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: srmservice error: 0, Started the agent (srmagent.exe)..
I have successfully installed SQL Server 2005 SP1 but when I go to the "Microsoft Update" site it is still shown as required. I have tried going back to an old image of the PC and installing SQL Server 2005 and SP1 again but still the "Microsoft Update" page is not picking up the fact that SP1 has installed successfully. Anyone had the same problem or know of a fix?
I've had some problems with Reporting Services and getting connected to the database server after configuration. I am now getting the following error message:
The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) (rsRPCError)
In my Database Setup everything runs fine when I click apply except for the Setting Connection Info for Reporting Server this has a yellow triangle with a ! and says that the report server cannot access internal information.
I also have not been able to Initialize as there are no instances to initialize and none are created when I go through setup. Is there something I need to delete from the registry or the file system that does not get removed upon uninstall?
Finding the "pieces of information" I need to successfully install the SQL Server Express edition is so complex. Uninstalls do "not" really uninstall completely, leading to failure of SQL install. Can you suggest a thorough, one-stop site for directions for the order of app uninstalls and then the order for app installs for the following...
SQL Server Express edition
Visual Studios 2005
Jet 4.0 newest upgrade
.Net Framework 2.0 (or should I use 3.0)
VS2005 Security upgrade
Anything else I need for just creating a database for my VS2005 Visual Basic project?
I was trying to use MS Access as my backend db but would like to try SQL Express
When I installed VS 2005, it installed the default version of SQL Server 2005 Express that ships with Visual Studio 2005 installer media.
How can apply SQL Server 2005 Express SP1 to update this existing instance?
Currently, if I run this query:
SELECT @@version
I get the following:
Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
After applying SP1, I should get 9.00.2047.00.
Should I just go to this link and download & install the SQL Server 2005 Express Edition SP1:
