SQL server 2008 restore and access error

hi
(provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server
I restored a backup which i was not created to a new database and if i connect above said issue is coming , if i generate script from restored DB and running without data in another new database and connecting to the same is working .. can you plz tell what
will be the exact problem and i found one database level user is there as below in the script.
CREATE USER [appointment_bee] WITHOUT LOGIN WITH DEFAULT_SCHEMA=[dbo]
kindly let me know whats the problem ..
regards,
martin

Hi Martin,
As Nag said, it's hard for us to understand your issue. For the error "Could not open a connection to SQL Server".
There could be several reasons you get these error messages. To avoid this issue, please refer to the steps that provided on the links below.
http://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/
http://blog.sqlauthority.com/2007/04/23/sql-server-fix-error-40-could-not-open-a-connection-to-sql-server/
If this is now what you want, please provide us more information about your issue, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Similar Messages

How to install BIDS for SQL Server 2008 R2 and Visual Studio 2008(SSRS,SSIS)

Hi,
I want to install SQL Server 2008 R2 and Visual Studio to use SSRS tool, where to download these application. And my System Configuration is Window 8.1,64 Bit.
Please share step by step information to download and installation. Kindly Reply soon.
Thank you
Pravesh Kumar

Hi Pravesh Kumar,
As Visakh16 suggestted that you can download sql 2008 r2 standard and developer editon.
If you have a subscription associated with your Microsoft account, you can download sql 2008 r2 standard and developer editon from below link, but these two editions are not for free:
https://msdn.microsoft.com/subscriptions/securedownloads/
Microsoft also provide the evaluation edition for free use of 180 days. This software is for evaluation and testing purposes. The evaluation is available in ISO format. Web, Standard, Enterprise and Datacenter editions are available via the same download:
http://www.microsoft.com/en-us/download/details.aspx?id=11093
More details information about the feature supported by different editions in the article below:
Features Supported by the Editions of SQL Server 2008 R2
If you still have any problem, please feel free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

SQL Server 2008 KB2977321 Failed with Error code 1642

As part of application of security patches via windows update, sql server KB2977321 was applied along with a number of OS security patches.
Prior to applying the patches, I stopped the agent, engine, reporting, analysis and full text services.
The Sql server build prior to windows update was (for both instances):
ProductVersion
ProductLevel
Edition
10.0.5500.0
SP3
Standard Edition (64-bit)
After the update process, my main instance is showing (the second instance is not in use yet and I have left it in its stopped state)
Microsoft SQL Server 2008 (SP3) - 10.0.5520.0 (X64)
Jul 11 2014 16:11:50
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
In the Administrative Logs after the OS patches were applied (and all were reported as successful by windows update), I found the following errors listed:
Log Name:
Application
Source:
MsiInstaller
Date:
11/18/2014 7:16:45 PM
Event ID:
1024
Task Category: None
Level:
Error
Keywords:
Classic
User:
SYSTEM
Computer:
SJCDB3.intranet.co.st-johns.fl.us
Description:
Product: Microsoft SQL Server 2008 Database Engine Services - Update '{9145CF54-462E-4A28-8FB5-A44C93AD3716}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot
issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1024</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-19T00:16:45.000000000Z" />
<EventRecordID>1764186</EventRecordID>
<Channel>Application</Channel>
<Computer>SJCDB3.intranet.co.st-johns.fl.us</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data>Microsoft SQL Server 2008 Database Engine Services</Data>
<Data>{9145CF54-462E-4A28-8FB5-A44C93AD3716}</Data>
<Data>1642</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B38373544383436332D313135422D343444322D414432352D3731454337453833423843437D207B39313435434635342D343632452D344132382D384642352D4134344339334144333731367D2031363432</Binary>
</EventData>
</Event>
In the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_191448\Detail.txt file I found the following around the time the error was reported
2014-11-18 19:16:30 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu32
BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_rs_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_rs_Cpu64 - NotInstalled on the baseline msi package sql_rs_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu32 BaselineVersion=10.3.5500.0;
PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_is_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_is_Cpu64 - NotInstalled on the baseline msi package sql_is_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_is_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_is_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_is.msp PatchCode={E870296C-24CC-4D82-BB59-CD136692E2BD}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_bids_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_bids_Cpu64 - NotInstalled on the baseline msi package sql_bids_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_bids_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_bids_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_bids.msp PatchCode={EA407FA6-C2D1-4D3D-9227-B9E06DDDEFD0}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_ssms_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_ssms_Cpu64 - NotInstalled on the baseline msi package sql_ssms_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_ssms_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_ssms_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_ssms.msp PatchCode={8A81B870-E8F0-415D-AC80-13BEAA3EC8C8}
2014-11-18 19:16:30 Slp: Baseline Package Id: sql_common_core_Cpu64 - No patches are found by SQL Discovery on the installed package whose ProductCode is {5340A3B5-3853-4745-BED2-DD9FF5371331}
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_common_core_Cpu64 - NotInstalled on the baseline msi package sql_common_core_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_common_core_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_common_core_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_common_core.msp PatchCode={CF023E0F-3A19-4DBF-BCA3-0F664B447EDB}
The instance came up successfully and seems to be operating normally. Was there an error or was the KB installed correctly as the result of the windows update process indicated?
Is there a way I can verify this?

I did some research on this particular KB article and it seems to be related to Master Data Services which I am not using. The KB was pushed automatically and I am not sure that it was a required update in our situation. I'd like to understand exactly
what caused the error message before initiating a repair as this is a production and not a test environment. Everything appears to be functioning properly and I have received direction from Microsoft in the past that information in some logs identified
as level 'error' are in fact to be ignored. I checked the windows update and this KB shows 'Successful' rather than failed or cancelled.
I would also like more information on why sql server services should not be stopped prior to allowing the OS patches to be applied.   I have received messages in the past that stopping the services before service packs are applied
prevent the necessity for a reboot of the machine. I've never heard before that it is a best practice not to stop Sql service prior to applying patches. Once the services are stopped, I have our infrastructure admin start a VM snapshot on
the machine then kick off the windows update process. When done, I reboot the machine, test out Sql Server processes and then if all goes well give the ok to release the VM snapshot. I've supported various databases for 12 years, Sql Server for 5
years and this is the first time I've heard stopping the service manually can cause problems. If that is the case, I will certainly change how I do things....
I did run the discovery report and the results follow:
Microsoft SQL Server 2008 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
SQL Server Replication
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Full-Text Search
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSAS10.MSSQLSERVER
Analysis Services
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSRS10.MSSQLSERVER
Reporting Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
EVAULT
MSSQL10.EVAULT
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Basic
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Complete
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Connectivity
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Backwards Compatibility
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools SDK
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Integration Services
1033
Standard Edition
10.3.5520.0
No

"a network related or instance specific error in sql server 2008..." error in sbs 2011 standard.

Hi All,
When we try to open "Sql Server 2008 R2" in SBS 2011.......... we are getting the error message" “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: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) ”
How can we resolve the issue?
Thanks in advance.
Ram.
Ramakrishna

Hi Ram, you can check the solutions in the following links and see if that helps:
A network-related or instance-specific error occurred while establishing a connection to SQL Server
http://social.technet.microsoft.com/wiki/contents/articles/a-network-related-or-instance-specific-error-occurred-while-establishing-a-connection-to-sql-server.aspx
A network-related or instance-specific error occurred while establishing a connection to SQL Server
http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/3a1c4d72-300c-4f9b-a0ac-23027ce04d1c/
Also, rather than a SBS specific issue, it seems only relate to SQL server, you can also post it to SQL server forum so that SQL server experts there can provide more accurate solutions:
http://social.technet.microsoft.com/Forums/en-US/category/sqlserver
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

SQL Sever Management Studio intellisense issue in SQL Server 2008 R2 and in SQL Sever 2012

Hi Team,
Intellisense in sql server management studio is working fine when i am accessing the databases in my local server.
But Intellisense is not working when ever i am trying to connect to the remote servers with the client
I tried different blogs and i tried to configure all the options i have upgraded to some patches upgraded for sql 2008 r2 client to sql 2012 client.
But Intellisense is not working with the remote server databases in the sql management studio .
Intellisense is working in the server but the same is not working when we are trying to access with client from our local machines.
Please provide me help to fix this issue
Regards
Karthik Kattamudi

Did you try to refresh the cache by hitting CTRL+SHIFT+R?
Also, these remote servers, are they SQL Server 2008 R2 as well or different version?
Please mark the answer as helpful if i have answered your query. Thanks and Regards, Kartar Rana

SQL Server 2008 R2 and storage replication

Hello All !
On a Production site, I have a SQL Server 2008 R2 for a fat application. On a DRP site, I have the same SQL Server 2008 R2 fat application.
The production and DRP sites are interconnected with a physical SAN storage (synchrone replication). SAN LUNs are synchronous replicated (Data + logs).
In this case, is it necessary to keep logshipping beetween the 2 sites or the LUNs replication is sufficient ?
Thanks for advance for your ideas / help - Regards - Have a nice day ! RHUM2

<<In this case, is it necessary to keep logshipping beetween the 2 sites or the LUNs replication is sufficient ?>>
That question is impossible for us to answer, since we don't know your requirements (SLA etc). But if you re-phrase your question, we can give feeback with which you hopefully can make that decision:
What can log ahipping protect me from which SAN replication can't? I can think of a couple of things (others are free to chime in):
Corruption at the page level. SAN replication give you a binary image of the data. If a page is corrupt at site A, it will be corrupt at site B. Log shipping work by retorting transaction log backups.
Delayed log restore. If a problem happens at site A, you can decide to have delayed log restores at site be and restore a log backup until just prior to the accident.
Both above assumes that you know what you are doing have basically have planned for these things. But technically, they are examples of things that log shipping allows for.
Tibor Karaszi, SQL Server MVP |
web | blog

Install SQL server 2008 in win8.1 (error : compatibility issues)

Hi it's Omka,
I've been trying to install sql 2008 express on my win8.1 for almost a week now.When installing the program it has a pop up window with "compatibility issue", but I just ignore that continued the installation, then this appeared
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
Invoke or BeginInvoke cannot be called on a control until the window handle has been created..
BUTTONS:
OK
After that I've tried changing the compatibility mode to windows xp(SP3), but it's not working, "restart computer" in setup support is having error.
Do I need to install other version of SQL or change any settings ?
Please help :)

Hello,
Please try to perform an slipstream installation of SQL Server 2008 + Service Pack 4 to solve the error and the compatibility
issues.
https://support.microsoft.com/en-us/kb/955392
http://www.microsoft.com/en-us/download/details.aspx?id=44278
This issue was first fixed with the following update hence my suggestion above.
https://support.microsoft.com/en-us/kb/975976/en-us
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2008 R2 SP3 install error - caspol.exe Fatal error

When I attempt to install sql server 2008 r2 sp3 I get caspol.exe - Fatal error. Unable to load Jit Compiler:(mscorjit.dll): file may be missing or corrupt. Please check or rerun setup. Then after I click ok I get the Microsoft Windows
popup that says Microsoft .NET Framework CAS Policy Manager has stopped working. This is on a Windows 2008 Enterprise Server, service pack 2. I am wondering if my .NET Framework had become corrupt on the server. Any ideas? This has
been on a stable production sql server that has been running fine for many years.
Thanks for reading my post.
Joe Sitver

Unable to load Jit Compiler:(mscorjit.dll): file may be missing or corrupt. Please check or rerun setup.
Hi Joe,
Mscorjit.dll (Microsoft .NET Runtime Just-In-Time Compiler) is a component of Web developing applications and the most prominent program that makes use of this file is the Microsoft.NET Framework.
The most common reason of the above error is that there is an improper installation/update of your .NET framework. Please
use this
tool to repair .NET framework. If the issue persists, you might need to uninstall and reinstall your
.NET framework.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

SQL Server 2008 R2 Reporting Service Error

Hi everybody,
I have an error when i try to access
http://localhost/ReportServer
The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)
I have found lots of posts according this error but any of it describes my error.
Do you have any ideas about problem reason?

i have serious problem about SSRS 2008 R2.i could not implement custom form authentication to SSRS 2008 R2.i have problem -useridentity-about below code ; i always get "Anonymous logon is not configured. userIdentity should not be null!" my report
server log.
public void GetUserInfo(out IIdentity userIdentity, out IntPtr userId)
         // If the current user identity is not null,
         // set the userIdentity parameter to that of the current user
         if (HttpContext.Current != null
               && HttpContext.Current.User != null)
               userIdentity = HttpContext.Current.User.Identity;
         else
         // The current user identity is null. This happens when the user attempts an anonymous logon.
         // Although it is ok to return userIdentity as a null reference, it is best to throw an appropriate
         // exception for debugging purposes.
         // To configure for anonymous logon, return a Gener
             System.Diagnostics.Debug.Assert(false, "Warning: userIdentity is null! Modify your code if you wish to support anonymous logon.");
             throw new NullReferenceException("Anonymous logon is not configured. userIdentity should not be null!");
         // initialize a pointer to the current user id to zero
         userId = IntPtr.Zero;

[Error] Microsoft SQL Server 2008 Setup. Error reading from file msdbdata.mdf

Hi all
I'm trying to install SQL 2008 Express on my Computer: Hp compact DX7300 Slim tower.
and get this error:
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:Error reading from file d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template\msdbdata.mdf. Verify that the file exists and that you can access it.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0&EvtType=0xF45F6601%25401201%25401
Log file
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: 2014-12-09 23:22:03
End time: 2014-12-09 23:40:28
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\sql_engine_core_inst_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1823.0
Machine Properties:
Machine name: VISTA-PC
Machine processor count: 2
OS version: Windows Vista
OS service pack: Service Pack 1
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:\8268cd7b247d294de359c9\x86\setup\
Installation edition: EXPRESS
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141209_232121\ConfigurationFile.ini
ENABLERANU: True
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
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: SQLExpress
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: d:\8268cd7b247d294de359c9\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: VISTA-PC\VISTA
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\20141209_232121\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
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\20141209_232121\SystemConfigurationCheck_Report.htm
I will very appriciate if someone can help me solve it. I was trying to set Full control for my account in Properties/Security of root folder and try again but error is still.
Many thanks

Hi Foreverduy,
Before you run SQL Server 2008 express setup, make sure that you have installed Windows installer 4.5 and.NET Framework 3.5 SP1 manually. For more information about the process, please refer to the article:
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.100).aspx. Moreover, please turn off all the third-party softwares which could prohibit the installation process.
According to your error message, the issue could be due to that your account has no rights to install SQL Server, or the corruption on the media.
Firstly, please ensure that your account has admin rights. Also make sure that you right-click the setup.exe and choose “Run as administrator” to complete the installation.
Secondly, please check if "msdbdata.mdf" file exists at d:\8268cd7b247d294de359c9\x86\setup\sql_engine_core_inst_msi\PFiles\SqlServr\MSSQL.X\MSSQL\Binn\Template. If it exists, please make sure that your account has read permission to the extracted
folder.
However, if the file doesn't exist in the extraction, the media could be corrupt. Please download the
media
again and check if the issue still occurs.
Regards,
Michelle Li

Backup Restore With SQL Server 2008 R2 although it succeeded with SQL Server 2008

Dears;
I have a Full backup of some DB of around 417 GB within SQL Server 2008 R2 , and when I tried to restore it , i get stuck several times with the error below :
Restore failed for Server (Microsoft.SqlServer.SmoExtended)
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider
running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical
Although I have restored
successfully other several Full+ Deferential backups for the same DB while it was in SQL Server 2008 not 2008 R2.
And so I have rounded all different possible assumptions for such common know error by Microsoft for SQL Server 2000, 2005, 2008 but
no way as next:
1-
I have attempted to restore it within 2 environments clustered and non-clustered of SQL Server 2008 R2.
2-
I have attempted to restore verify it and it was so fine .
3-
I have attempted to restore it using Continue_after_error ,no_checksum but no way.
4-
I have attempted to move Backup file to another Storage but no way.
5-
I have scheduled jobs to DBCC
Checkdb the live DB and it wasn’t any errors since long time right now
6-
I have also DBCC check all master +msdb+model+Tempdb ,and they are so fine
7-
I have also checked all I/O subsystem of SAN and Network controllers , but they are fine evidenced much more by my trial on 2 different environments.
8-
I have also checked Memory and it is so fine all the time since I have 128 GB memory and I control it also so well.
For DB Design +Structure :
It has 20 Files containing tables partitioned horizontal +Vertically
(Schema Partitioning +File Stream partitioning ) through these 20 files.
I have Data compression of the required tables only.
I have one table of more than 300 GB alone which is partitioned as mentioned above.
I have implemented Read Committed Snapshot isolation level using row versioning integrated so well with File stream technology since it is a new feature of SQL 2008 R2.
DB is in simple recovery model for garbage collection of all file stream data as a result of much Delete /update in images themselves.
So any one has any idea about such case..How to solve it…?

Hi Ashwin,
When i searched with no answers these are listed out. So i thought this is still existing. Now on wards let me check the data and time of latest reply. Thanks for guidance.
It was happening by oversight. Thanks for guidance.
Regards, Pradyothana DP. Please Mark This As Answer if it solved your issue. Please Mark This As Helpful if it helps to solve your issue. ========================================================== http://www.dbainhouse.blogspot.in/

Attempted to perform an unauthorized operation error on windows 8.1 while installing SQL server 2008

Hi,
I am getting the error "Attempted to perform an unauthorized operation" on windows 8.1 while installing
SQL server 2008.
The specific error is The error is Attempted to perform an unauthorized operation."
at stepSqlBrowserConfigAction_install_ConfigNonRC_Cpu32 .
I have tried everything from copying to the C drive. I am the admin on the machine. I also checked access in registry. It already has acesss to HKLM\System\CurrentControlSet\Control\WMI\security
Can someone comment on how to resolve this issue. I also tried NT
AUTHORITY\SYSTEM but getting the same error.
Any help would be appreciated.

Hello,
Please note that SQL Server 2008 requires Service Pack 3 (SP3) to make it compatible with
Windows 8.1. Please perform an slipstream installation of SQL Server 2008 + SP3:
http://support.microsoft.com/kb/955392
If it fails again, please share with us the Summary.txt log file and the details.txt log file. The following article
may help you locate those files on disk::
http://msdn.microsoft.com/en-us/library/ms143702(v=sql.100).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

CFMXE 7.x and SQL Server 2008

Hello - a client recently upgraded to SQL Server 2008 and we can no longer connect from CFMXE 7.x.
I have asked them to go through the steps outlined here <http://blog.mxunit.org/2009/02/connecting-sql-server-2008-to.html> but errors persist. The DSN is defined using the standard SQL Server driver - is there an updated one that is required for 2008?
The error I have now is Cannot open database "database" requested by the login. The login failed.
Caveats - I have no access to the database server.
Suggestions?

I know we have a couple of CF 7 servers that are connecting using the built in sql drivers to sql 2008 without issue, so out of the box it should work.
I would suggest seeing if dynamic ports are enabled on the sql server, which would maybe cause a problem if there is a firewall involved and perhaps with the CF drivers.
To ensure you stay on port 1433, I think in CF 7 you can specify additional connection params in the DSN under the advanced dialog. I don't have a machine in front of me. I'd have to try it out.
Alternatelly you could try the "other" driver for the DSN, and use a JDBC connection string to connect and specify the port. If you need a better example, email me and I'll send over an example.
Our 2005 - 2008 Sql upgrades have been very smooth with regards to the DSN, and we didn't have to update anything aside from the server ip, so it should work.
Byron Mann
[email protected]
[email protected]
Software Architect
hosting.com | hostmysite.com
http://www.hostmysite.com/?utm_source=bb

Windows 8 and IE 10 crashed after printing from Report Manager SQL server 2008 / 2008 R2

We have a problem with Windows 8 in combination with IE 10 and printing reports.
When we print a report from the Report Manager 'http://<servername>/reports' the browser crashed after a print.
Sometimes before printing and somthimes after printing or when you close the browser.
Al other operating systems like XP, Vista, Windows 7 with different IE versions have no problem.
I tried the report manager from SQL Server 2008 and SQL Server 2008 R2.
The same error occured when printing from our Internet application and the reportviewer.
(ASP application written in Visual Studio 2010 and reportviewer version 10.)
The event log shows two different messages.
Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16453, time stamp: 0x509b0dfb
Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82
Exception code: 0xc0000005
Fault offset: 0x00061252
Faulting process id: 0x780
Faulting application start time: 0x01ce03a294f7d1d5
Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d4a72486-6f96-11e2-be6e-10604b6a74ed
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16384, time stamp: 0x50107ee0
Faulting module name: rsclientprint.dll, version: 2009.100.1600.1, time stamp: 0x4bb67a74
Exception code: 0xc0000005
Fault offset: 0x00017e7a
Faulting process id: 0x9c8
Faulting application start time: 0x01ce02f35c70ab85
Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
Faulting module path: C:\Windows\Downloaded Program Files\rsclientprint.dll
Report Id: a13fccc6-6ee6-11e2-be67-10604b6a74ed
Faulting package full name:
Faulting package-relative application ID:
Is there a fix for this problem?

Dear Mike Yin,
Thank you for your response. Your answer was the
reason for finding the real problem.
In december 2010 a SQL Server 2008 fix was the cause. I don't remember exactly the problem, but we changed the RSCLIENTPrint-x86.cab file. But instead to use the version of SQL Server 2008 we used the version of SQL Server 2008
R2 (10.50.1600.1). This worked until
Windows 8 (Internet Explorer crashed when printing).
We fixed this problem by using the RSClientPrint-x86.cab file from SQL server 2008 (10.0.5500.0).
But we now get the known problem that the
activeX always must be installed again.
The reason for this is that the version of
the SQL Server (10.0.5512.0)
and the rsclientprint.dll (10.0.5500.0) is different. SQL Server is newer (caused
by a security patch (KB2716436)).
Do you know when this problem will be resolved
by Microsoft?
Work arrounds
I've also tried to install the RSClientprint.dll
every time automatically (without user interaction).
But this will be delayed the printing for more
than 4 seconds. This
is very annoying.
Another workaround is to generate a PDF and print the PDF. But this is also
a lot slower.
Uninstall the security patch. but I don't know the security risk.

SQL Server 2008 Installation Error

I found this error when i am try to Install SQL Server 2008 on Windows 8
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:
Error getting file attributes for 1392. Please make sure that the drive is formatted and accessible.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0xF45F6601%25401201%25401
BUTTONS:
OK

Hi,
Did you check what the message ask you to?
Are you using local disk for the installation? Are you trying to install on a disk different from the OS disk (C:\) ?
Please try to give more information.
[Personal Site] [Blog] [Facebook]

SQL server 2008 restore and access error

Similar Messages

Maybe you are looking for