WSUS wants our SQL server (running 2008 R2 SP2) to install SP1. Why?

We just installed a bunch of Windows Updates on our servers (that were pushed out from WSUS). One of the updates -- SQL Server 2008 R2
SP1 -- failed to install on our SQL server. But that's because it already had
SP2 installed. I ran a Discovery Report, and all of our SQL Server 2008 R2 components are at SP2. And yet, WSUS wants this server to install SP1.
Any suggestions as to why? I'd rather not re-install SP2 if it's not necessary.
Thank you!
p.s. I do see the following in the Sumary.txt file produced by the Discovery Report:
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       1
Installation edition:          EVAL
What is this "EVAL" version? I don't think we ever installed an evaluation version of SQL, though I suppose that's possible

Hi,
A similar thread discussed below was caused that reporting service didn’t work properly. And the solution is to run
Sp2 setup again and just select reporting service for upgrade.
For more information please refer to:
SQL Server 2008 R2 SP2 wants to install SP1 again via WSUS
http://social.technet.microsoft.com/Forums/en-US/6e711903-7c2c-4bec-a9d8-c0b56ba0f9f8/sql-server-2008-r2-sp2-wants-to-install-sp1-again-via-wsus?forum=sqlsetupandupgrade

Similar Messages

What does ERROR: DW050: - SQL Server Compact 3.5 SP2 x64: Install failed

What does ERROR: DW050: - SQL Server Compact 3.5 SP2 x64: Install failed mean

What Adobe software are you trying to install? Which operating system are you using? You may also want to review Troubleshoot with install logs | CS5, CS5.5, CS6 - http://helpx.adobe.com/creative-suite/kb/troubleshoot-install-logs-cs5-cs5.html as the error your posted is not very actionable at the moment.

SQL Server std 2008 R2 SP2 upgrade to 2014 std fails, SSRS issue?

I’m trying to make an in place upgrade from 2008 r2 sp2 to sql 2012. With old installation everything (including Reporting Services) works fine, there is only one instance named MSSQLSERVER and all stuff is on one server, ssrs is native mode, compatibility
level of databases is 100.
When I start upgrade process al things go fine till “Feature Rules” where “No Custom Rendering Extensions” fails (it says “The Report Server has some custom rendering extensions configured”). Into Windows Application Log appears the following “Report Server
(MSSQLSERVER) cannot connect to the report server database” and installation stops. We have not installed any extensions as far as I know. I’ve done some tweaking with RSReportServer.config but without success.
Any good advice?
Pekka

Hello,
Please verify you don’t have extension elements added on the RSReportDesigner.config file too.
Use the following article to remove any possible rendering extensions:
http://msdn.microsoft.com/en-us/library/ms152821(v=sql.105).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Multiple instance of Sql server running for Analyzer 7.0 install

Hi,I do have a Sql server instance where the server name is: abc\xyz. Will analyzer accetp a '\' as the server name. This instance of Sql server is not running is not running on the std port 1433. Let me know if there will be any issues whrn installing Analyzer 7.0.Thanks,

There can only be a single default instance and multiple named instances.
BOL: http://technet.microsoft.com/en-us/library/ms143547.aspx
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SQL Server Express 2008 no longer accepting remote connections

Last night our SQL Server Express 2008 (running on Windows 2003 server) stopped accepting remote connections.
1. We restarted the SQL Server -- no resolution.
2. We rebooted the host Windows 2003 server - no resolution.
3. telnet localhost 1433: says Could not open connection to the host on port 1433... connection failed.
4. netstat -an indicates that the server is not listening on port 1433
5. SQL Server Network Configuration -> Protocols for SQLEXPRESS2008A -> (properties) -> TCP-IP (enabled), Listen All (yes)
6. SQL Native Client 10.0 Configuration -> Client Protocols -> (properties) TCP-IP (enabled), Default port (1433)
Fragment from the server error log:
2014-03-26 08:50:41.09 Server      A self-generated certificate was successfully loaded for encryption.
2014-03-26 08:50:41.11 Server      Server is listening on [ 'any' <ipv4> 1026].
2014-03-26 08:50:41.11 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS2008A ].
2014-03-26 08:50:41.11 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS2008A\sql\query ].
2014-03-26 08:50:41.11 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the
trace flag 7806. This is an informational message only. No user action is required.
2014-03-26 08:50:41.11 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-03-26 08:50:41.11 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-03-26 08:50:41.29 spid10s     Clearing tempdb database.
2014-03-26 08:50:41.89 spid10s     Starting up database 'tempdb'.
2014-03-26 08:50:42.09 spid13s     The Service Broker protocol transport is disabled or not configured.
2014-03-26 08:50:42.09 spid13s     The Database Mirroring protocol transport is disabled or not configured.
2014-03-26 08:50:42.14 spid13s     Service Broker manager has started.
2014-03-26 08:50:42.14 spid7s      Recovery is complete. This is an informational message only. No user action is required.
2014-03-26 08:50:53.48 spid51      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2014-03-26 08:50:53.48 spid51      Using 'xpstar.dll' version '2007.100.1600' to execute extended stored procedure 'xp_enumerrorlogs'. This is an informational message only; no user action is required.
2014-03-26 08:51:35.68 spid54      Starting up database 'Web TimeSheet2'.
2014-03-26 08:51:38.47 spid54      Recovery is writing a checkpoint in database 'Web TimeSheet2' (6). This is an informational message only. No user action is required.
Note: the lines referring to xpstar.dll is new after this porblem. Previous logs do not have this,Any help will be appreciated.

Hi,
>>Server is listening on [ 'any' <ipv4> 1026].
Your sql server is not listening on default port 1433 but on 1026.When you connect to instance like hostname\instancename you should specify post no also.
like hostname\instancename ,1026
Can you try this.Makes sure TCP/IP and named pipes protocol is enabled
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

I want to give a user to read only rights on sql server agent 2008

I want to give a user to read only rights on sql server agent 2008.When I giving SQLAgentuser Role then user is only able to view SQL Server agent as Green but no job visible in job activity monitor.Currently he has db_reader rights on one user database.
What rights should I give?
Thanks

There are 3 SQL server Agent fixed database roles in sql server.
1.SQL AgentUSerRole:- To create and manage jobs
2.SQLAgentReaderRole: To grant read acces.
3.SQLAgentOperatorRole : to run and delete jobs.
For you question you can create a user and grant him SQLAgentReaderRole.
Example:
Create LOGIN test with Password='abc'
Use msdb;
GO
Create User test for login test
use msdb;
EXECUTE sp_addrolemember @rolename='SQLAgentReaderRole',@membername='test'
Hope this solves your problem!!!

How can I make sure that in RAM our sql server is not facing any mermory crunch issue?

The SQL server process always show RAM is highly used while its a default behaviour of sql server.
How can I make sure that in RAM our sql server is not facing any mermory crunch issue?
Thanks

The SQL server process always show RAM is highly used while its a default behaviour of sql server.
How can I make sure that in RAM our sql server is not facing any mermory crunch issue?
Thanks
The best way to make sure you are not facing memory pressure is to use perfmon counters and monitor various memory counters
For SQL Server 2005 - 2008 r2 use below counters
SQLServer:Buffer Manager--Buffer Cache hit ratio(BCHR): IIf your BCHR is high 90 to 100 Then it points to fact that You don't have memory pressure. Keep in mind that suppose somebody runs a query which request large amount of pages in that
case momentarily BCHR might come down to 60 or 70 may be less but that does not means it is a memory pressure it means your query requires large memory and will take it. After that query completes you will see BCHR risiing again
SQLServer:Buffer Manager--Page Life Expectancy(PLE): PLE shows for how long page remain in buffer pool. The longer it stays the better it is. Its common misconception to take 300 as a baseline for PLE. But it is not,I read it from
Jonathan Kehayias book( troubleshooting SQL Server) that this value was baseline when SQL Server was of 2000 version and max RAM one could see was from 4-6 G. Now with 200G or RAM coming into picture this value is not correct. He also gave the formula( tentative)
how to calculate it. Take the base counter value of 300 presented by most resources, and then determine a multiple of this value based on the configured buffer cache size, which is the 'max server memory' sp_ configure option in SQL Server, divided by 4 GB.
So, for a server with 32 GB allocated to the buffer pool, the PLE value should be at least (32/4)*300 = 2400. So far this has done good to me so I would recommend you to use it.
SQLServer:Buffer Manager--CheckpointPages/sec: Checkpoint pages /sec counter is important to know about memory pressure because if buffer cache is low then lots of new pages needs to be brought into and flushed out from buffer pool,
due to load checkpoint's work will increase and will start flushing out dirty pages very frequently. If this counter is high then your SQL Server buffer pool is not able to cope up with requests coming and we need to increase it by increasing buffer pool memory
or by increasing physical RAM and then making adequate changes in Buffer pool size. Technically this value should be low if you are looking at line graph in perfmon this value should always touch base for stable system.
SQLServer:Buffer Manager--Freepages: This value should not be less you always want to see high value for it.
SQLServer:Memory Manager--Memory Grants Pending: If you see
memory grants pending in buffer pool your server is facing SQL Server memory crunch and increasing memory would be a good idea. For memory grants please read this article:
SQLServer:memory Manager--Target Server Memory: This is amount of memory SQL Server is trying to acquire.
SQLServer:memory Manager--Total Server memory This is current memory SQL Server has acquired.
8. Free List Stalls/sec – Number of requests per second that had to wait for a free page
9. Free Pages – Total number of pages on all free lists (free lists track all of the pages in the buffer pool that are not currently allocate to a data page, and are therefore available for usage immediately)
NOTE: If you have NUMA system don't use PLE to monitor memory condition it wont give correct value
From 2012 Onwards
Memory management has become easy from 2012 onwards as
Max server memory also allocated memory for requests which require memory >8KB
SQLServer:Memory Manager:Free Memory (KB)
SQLServer:Memory Manager:Target Server Memory (KB)
SQLServer:Memory Manager:Total Server Memory (KB)
For NUMA system its also wort monitoring each node.
Object - SQLServer:Memory Node:Total Node Memory
(KB)
Object - SQLServer:Memory Node:Target Node Memory
(KB)
Object - SQLServer:Memory Node:Free Node Memory
(KB)
Ideally if target server memory is less than or equal to total server memory there wont be memory pressure if target is > total it does not always means its memory pressure
BCHR would also give you good idea about memory pressure
If memory grants pending is frequently non zero there is memory pressure
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Error Installing SQL Server Express 2008: '' is not a valid login or you do not have permission.

I have tried installing SQL Server 2008 multiple times on my machine, and I always receive this error about 3/4 of the way through: '' is not a valid login or you do not have permission.
I have tried installing both SQL Server Express 2008 with Tools and SQL Server Express 2008 with Advanced Services, and they both fail the same way. I am trying to do a new stand-alone installation.
I'm running Windows XP Home Edition SP3.
Looking into the error, some forums say I have to install it from THE Administrator account, and not an account with administrator permissions; it also cannot be in Safe Mode, because then the Windows Installer won't work. Unfortunately, I haven't been able to login to the Administrator account. I can go to the home login screen, do ctrl+alt+del twice, and attempt to login to the Administrator account, but I receive this error: Unable to Log You on because of an Account Restriction.
Other forums say that in the Server Configuration section, all you have to do is provide the username and a strong password from an administrative account on the computer, and it doesn't have to be THE Administrator. Well, I did that, but for some reason it doesn't recognize my username and password, it says something like "The credentials you provided for the SQL Server Agent are invalid". BUT THOSE ARE THE CORRECT CREDENTIALS FOR MY ADMINISTRATIVE USER! So I'm forced to use one of the accounts without a password, like NT AUTHORITY\SYSTEM. That's the only way I can get past this step.
Also, just FYI, on the next step, which is Database Engine Configuration, I am using Mixed Mode for the Security Mode. I AGAIN provide a password, and then add my current user (who IS an administrator on my machine!) to the SQL Server Administrators box.
But yet, it fails every single time.
This is pathetic and ridiculous. I must have tried to install this thing 15 times, that is not an exaggeration. I'm posting this on several other forums as well, maybe an MVP or Bill Gates himself can help me.
I have one of the log files from a failed installation. If someone would like to see it, I will post it.

Papy Normand wrote:
Hello,
Please, could you have a look on the excellent answer of Mike Wachal you will find here :
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=4160294&SiteID=1
Don't hesitate to post again for more help or explanations
Have a nice day
PS : if you are talking about the Sql Server Agent Service, it is disabled for Sql Server Express. It is enabled only for the Workgroup/Standard/Dev and Entreprise Editions
Sorry, but I've tried the suggestion in that link, and it hasn't helped me.
For anyone wonder, the link is talking about the problem in Server Configuration where I enter my Windows user account and password (which is in the Administrative group), but it says the credentials are invalid. The link suggests that you need to either enter your Windows account (which I did, and it wouldn't let me go to the next step), or to use one of the built in accounts (which I also tried, but it gave me the " '' is not a valid login" error during the installation).
Any other ideas?
I haven't had any answers from any other forums either, so I'll just post my log file in case anyone wants to look at this:
Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal):           -2068643839
Exit facility code:            1203
Exit error code:               1
Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time:                    2008-11-17 11:13:47
End time:                      2008-11-17 12:17:25
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xBE029E38%400x12C2466D
Machine Properties:
Machine name:                  STEVEN
Machine processor count:       2
OS version:                    Windows XP
OS service pack:               Service Pack 3
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x86
Process architecture:          32 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008
SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName:                   SQL2008
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         D:\x86\setup\
Installation edition:          DEVELOPER
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            STEVEN\Steven
ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\ConfigurationFile.ini
ENABLERANU:                    False
ERRORREPORTING:                False
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
MEDIASOURCE:                   D:\
NPENABLED:                     0
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSINSTALLMODE:                 DefaultNativeMode
RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           STEVEN\Steven
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature:                       SQL Client Connectivity SDK
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature:                       Analysis Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:      0x12C2466D
Configuration error description: '' is not a valid login or you do not have permission.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
Feature:                       Integration Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools SDK
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Books Online
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Microsoft Sync Framework
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\SystemConfigurationCheck_Report.htm

SQL Server Express 2008 and WOW64

Our software requires SQL Server Express 2008 to be installed on various computers. We have run into a problem with systems that have WOW64. When the SQL installer is going through it's check list, it marks the WOW64 as the reason that it cannot continue. In other cases I get a notification that tells me that windows installer 4.5 or higher is required but when I try to install windows installer 4.5 it tells me that the it is not the correct verson of windows installer for the system. I try a few different versions and get the same problem. I am confused as to why one windows software would not work with another.

Hi,
- Which version of Windows installer 4.5 are you trying to install ? For X86, X64 or IA64 ?
- Which version of your operation system ? Windows 2003 ? 2008 ? 2008 R2 ? .....
For information
Download the file that is appropriate for your operating system version and platform.
For Windows Vista, Windows Vista Service Pack 1 and Windows Server 2008:
x86 Platform: Windows6.0-KB942288-v2-x86.msu
x64 Platform: Windows6.0-KB942288-v2-x64.msu
IA64 Platform: Windows6.0-KB942288-v2-ia64.msu
For Windows XP Service Pack 2 and Windows XP Service Pack 3 (32-bit platforms):
x86 Platform: WindowsXP-KB942288-v3-x86.exe
For Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2 and Windows XP 64-bit Editions:
x86 Platform: WindowsServer2003-KB942288-v4-x86.exe
x64 Platform: WindowsServer2003-KB942288-v4-x64.exe
IA64 Platform: WindowsServer2003-KB942288-v4-ia64.exe
Extract of the documentation :
Windows Installer 5.0 will be released with, and require Windows Server 2008 R2 or Windows 7. Versions earlier than Windows Installer 5.0 were released with Windows Server 2008, Windows Vista, Windows Server 2003, Windows XP, and Windows 2000.
Windows Installer 4.5 requires Windows Server 2008, Windows Vista, Windows XP with Service Pack 2 (SP2) and later, and Windows Server 2003 with Service Pack 1 (SP1) and later.
Cheers,
Michel.
Michel DEGREMONT , my blog SQL Server

SQL Server express 2008 fails due to no useable instance

hi I am trying install a piece of software which requires SQL server express 2008. The server software comes with my software and is installed first but I cannot get it to install correctly. My operating system is Win7 64bit. Any ideas?.
thx
mark

Hi nield,
According to your description, before you installing SQL Server 2008 Express version on Windows 7 64bit, we need to verify if you install Microsoft .NET Framework 3.5 SP1 successfully on servers. After SQL Server setup completes, you need to apply SQL Server
Service Pack1(SP1) or a later service pack before you run SQL Server 2008 on the Window 7. There is detail about how to install SQL Server 2008 on Windows 7, you can review the following article.
http://www.codeproject.com/Articles/305113/How-to-Install-SQL-server-on-Windows
In addition, as other post, if you install failed, I recommend you help us to collect the detailed error message from the following error log. It is very useful for our research.
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\LOG\Summary.txt.
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\<YYYYMMDD_HHMM>\Detail.txt
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Cannot stablish a Database NEW connection with SQL Server Express 2008 R2 and Netbeans 8

Hi I appreciate it if someone could help to this case: I AM TRYING TO MAKE A CONNECTION TO MY SQL SERVER EXPRESS 2008 WITH MY NETBEANS 8 And I get ERROR ... APPARENTLY IS MY USER AND KEY BUT I AM PUTTING THE CORRECT USER AND KEY IN WHICH I CONNECT WITH MY
SQL SERVER EXPRESS 2008. I HAVE PUT IN PORT THE 1433 TCP / IP PORT. THE HOST, THE NAME OF MY DATABASE.
NO PASSING OR ERROR WHICH CAN BE ...

Hi DianaWeb,
It's glad to hear that your problem is resolved by changing the windows authentication into mixed authentication and use 'sa' user, namely an SQL Server authentication.
I believe the user name and password in the Netbean are for SQL Server Authentication to connect to SQL Server. The windows authentication you typed is not a valid SQL Server Authentication, that was why the connection failed.
In any case, if you want your J2EE project connects to SQL Server using Windows authentication(credentials of the user running Tomcat/Jboss where your application is deployed). Just build your JDBC URL like this:
jdbc:sqlserver://localhost;integratedSecurity=true;
See
Can I connect to SQL Server using Windows Authentication from Java EE webapp?
If you have any question, feel free to let me know.
Eric Zhang
TechNet Community Support

SQL Server Express 2008 Installation error. PLEASE HELP.

Hey guys anyone know what I should do to install SQL Server Express 2008?
Im running Vista Home Premium SP1 32bit
These are folders i got on framework folder:
    *      v3.5
    *      v3.0
    *      v2.0.50727
    *      v1.1.4322
    *      v1.0.3705
Installing SQL Server 2008 Express (run time only)
And this is the error I get during the process
"Attributes do not match. Present Attributes (Directory, Compressed), included attributes (0), excluded attributes (Archive, Compressed, Encrypted)."
I have downloaded and installed all Visual Studio 2008 SP1 Express Ed (C++, C#, VB, WebDev) and all worked well
I get this error during the "Feature Selection" setup process.
I also noticed when I tried to use Windows Update, I saw Microsoft SQL Server 2008 Service Pack 1 (KB968369) suddenly available (I have updated windows and installed all important updates before installing Microsoft Visual Studio and SQL). Then I used Windows Update to install SQL Server 2008 SP1 and I still got this error:
Error
Code 84B40000 Unknown error....
I also get this downloading error on SQL Server while installing all 4 Visual Studio Express Editions (C#, C++, VB, WebDev).
"The following cannot be downloaded:"
I've already tried the troubleshooting guide about BITS but the tool fix seems to only supports Windows XP Operating Systems.
Please please please Help Me (^_^).. thanks to all.
P.S.
I think this might have some connections to why I get errors on a simple 'Hello World' Website.
I was just trying to simply make a 'Hello World' Website .. Just THAT on my website.
A simple Website for me to start. Just showing those text on the website. But when I tried to run (debug) the program. This error shows...
'Firefox can't establish a connection to the server at localhost:5903.'
I have Build the Web Site and there was no error. Since it was just simply 'Hello World' text.
Im sure there's some problem but I'm completely stuck here. I dunno if its connected to the problem above.
Please help me solve this problem. Thank you so much.
I appreciate everyone's help.

In my case I had to uncheck "Allow files in this folder to have contents indexed in addition to file properties"
Right click on C:\Program Files\Microsoft SQL Server
Click Advanced on General Tab
Uncheck "Allow files in this folder to have contents indexed in addition to file properties"

SQL Server Express 2008 R2 and Windows 8.1 (Standard)

I recently re-engineered the backend of a legacy Access 2003 application because we knew that going forward we were going to loose the replication capability in Access. This is a small, departmental app, so the new SQL Server Express 2008 R2 backend is
hosted on a robust Windows 7 system. I tested the implementation with both Windows XP and Windows 7 clients running the updated Access 2003 frontend and everything worked great.
We are now in the midst of a company-wide upgrade to Windows 8.1 and I'm having issues. The legacy frontend works fine with Access 2013 (full version) when run locally on the Win7 machine, but I can't get any of the new Win 8.1 clients to connect to the
SQL database using the Access 2013 Runtime module. I CAN create ODBC connections to SQL Server from the clients and they test successfully, so I think I have a valid SQL connection to the Win 7 box.
To recap: old clients were WinXP Pro with Office 2003 Pro, new clients are Win 8.1 (non-Pro) with Access 2013 Runtime module.
Any ideas?

Hi ,
Glad to hear that you have found the solution. Thank you for coming back and let us know the result:)
Best Regards,
Tracy
Tracy Cai
TechNet Community Support

Getting error while installing sql server std 2008 R2 on win 7 prof. sp1 64bit

Hi,
I am getting error while installing sql server std 2008 R2 on win 7 prof. sp1 64bit. I have already tried all option but fail to installation
an error during the installation of assembly micro soft.vc80.crt

Hi,
I am getting error while installing sql server std 2008 R2 on win 7 prof. sp1 64bit. I have already tried all option but fail to installation
an error during the installation of assembly micro soft.vc80.crt
Can you please post summary.txt file here.Below link will help you in finding it.
http://technet.microsoft.com/en-us/library/ms143702(v=sql.105).aspx
Also with error you posted I guess it is a known issue .You need to install below package and then continue with fresh installation
http://www.microsoft.com/en-gb/download/details.aspx?id=15336
Please make sure before beginning fresh installation you make sure previous failed installation is removed completely.Use add remove program to remove failed SQL Server.If yu still face issue please post summary.txt file here
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Connection problem in Crystal Reports for Eclipse(SQL Server Express 2008)

I tried to connect into a local SQL Server Express 2008 database in Crystal Reports for Eclipse (CR4E), but always got the Ping failed message(TCP/IP connection failed) even I tests completed successfully using my Window XP Adminstrators Tools (SQL Server ODBC Data Source Test). I can connect successfully to a remote network Oracle database in CR4E. I would like to know
that is there any one who connect SQL Server Express 2008 local database successfully in CR4E?

Don,
Thanks for your suggestions. I will follow your instruction to connect to SQL Server Express 2008 database latelly. I can connect successfully with different Oracle databases (10g) in CR4E. I will try to connect MySQL database and Postgres database in CR4E to see if they can be successful or not. My project involves international entities with emphsizing in using OPEN SOURCE softwares (which means FREE - no license fees) in .NET platform for Oracle, SQL Server Express, MySQL and Postgres database servers. I am responsible for reports generation. I hope that CR4E can be connected successfully to SQL Server Express 2008 database server, otherwise I have to use JFreeReport/JFreeChart tools to do reports generation .

WSUS wants our SQL server (running 2008 R2 SP2) to install SP1. Why?

Similar Messages

Maybe you are looking for