SQL Server database save error

I am encountering an issue every few days or so whereby, for some reason, my metadata database LDF log file is growing to a very large size (> 5GB in size). This could be due to specific settings for my database, however I don’t believe I’m doing anything
unusual so it’s probably worth recording.
When the LDF grows to a large size, I start to see the following I/O error messages in the windows event viewer for the SQL database service:
2014-08-28 16:18:25:
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [C:\SCM\Databases\PPGallium_Metadata_New4_log.ldf] in database [PPGallium_Metadata_New4] (7).  The OS file handle is 0x0000000000000A64. 
The offset of the latest long I/O is: 0x000000fe4f3200
This is followed by further follow-on errors in saving data to the database (from Gallium database service log for same time):
-28 16:19:05.960] DEBUG (   90) PP.Workflow.Service.Database.MetadataProvider - Saving 13 items(s) on model with ID 'd022f598-4f25-4f87-a8fd-e8dc2825c916'...
[2014-08-28 16:19:06.341] DEBUG (   88) PP.Workflow.Service.Database.ScheduleProvider - Saving 1 items(s) on model with ID 'f16fac97-3cdd-471a-bf8c-7a839a386f7f'...
[2014-08-28 16:19:06.347] DEBUG (   88) PP.Workflow.Service.Database.ScheduleProvider - Committing...
[2014-08-28 16:19:06.354] DEBUG (   88) PP.Framework.Model.Sync.Database.SqlDataContext - Committing...
[2014-08-28 16:19:06.357] DEBUG (   88) PP.Framework.Model.Sync.Database.SqlDataContext - Committed.
[2014-08-28 16:19:06.360] DEBUG (   88) PP.Workflow.Service.Database.ScheduleProvider - Item(s) saved.
[2014-08-28 16:19:06.672] DEBUG (   89) PP.Workflow.Service.Database.MetadataProvider - Saving 5 items(s) on model with ID 'd022f598-4f25-4f87-a8fd-e8dc2825c916'...
[2014-08-28 16:19:06.722] DEBUG (   92) PP.Workflow.Service.Database.MetadataProvider - Saving 5 items(s) on model with ID 'd022f598-4f25-4f87-a8fd-e8dc2825c916'...
[2014-08-28 16:19:06.860] DEBUG (   54) PP.Workflow.Service.Database.ScheduleProvider - Purging...
[2014-08-28 16:19:06.865] DEBUG (   54) PP.Framework.Model.Sync.Database.SqlDataContext - SQL output received ('There are no more objects to purge').
[2014-08-28 16:19:06.867] DEBUG (   54) PP.Workflow.Service.Database.ScheduleProvider - Purging complete. 0 item(s) purged. 25 item ID(s) remain cached.
[2014-08-28 16:19:06.962] DEBUG (   88) PP.Workflow.Service.Database.MetadataProvider - Saving 6 items(s) on model with ID 'd022f598-4f25-4f87-a8fd-e8dc2825c916'...
[2014-08-28 16:19:13.553] ERROR (   60) PP.Workflow.Service.Database.DatabaseService - Failed to save ('Failed to commit transaction ('Failed to merge 'Object' data from staging table due to an SQL error ('Timeout expired.  The timeout
period elapsed prior to completion of the operation or the server is not responding.')')').
[2014-08-28 16:19:13.586] DEBUG (   22) PP.Workflow.Service.Database.MetadataProvider - Committing...
[2014-08-28 16:19:13.603] ERROR (   17) PP.Workflow.Service.Database.DatabaseService - Failed to save ('Failed to commit transaction ('Failed to merge 'Object' data from staging table due to an SQL error ('Timeout expired.  The timeout
period elapsed prior to completion of the operation or the server is not responding.')')').
[2014-08-28 16:19:13.617] ERROR (   20) PP.Workflow.Service.Database.DatabaseService - Failed to save ('Failed to commit transaction ('Failed to merge 'Object' data from staging table due to an SQL error ('Timeout expired.  The timeout
period elapsed prior to completion of the operation or the server is not responding.')')').
[2014-08-28 16:19:13.621] DEBUG (   89) PP.Workflow.Service.Database.MetadataProvider - Committing...
[2014-08-28 16:19:13.623] DEBUG (   32) PP.Workflow.Service.Database.MetadataProvider - Committing...
When I then restart the database service, I get the following unhandled exception:
2014-08-28 16:21:15.874] DEBUG (    6) PP.Workflow.Service.Database.ScheduleProvider - Purging complete. 0 item(s) purged. 25 item ID(s) remain cached.
[2014-08-28 16:21:16.625] FATAL (Database Cache Pre-fetch) PP.Workflow.Service.Database.DatabaseWindowsService - Unhandled exception on worker thread ('Failed to get child BLOB properties for object '233fd1db-67c2-4745-91ce-8ff5c5bdf044' due to an SQL error
('Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.')').
PP.Framework.Model.Sync.Core.SyncModelProviderException: Failed to get child BLOB properties for object '233fd1db-67c2-4745-91ce-8ff5c5bdf044' due to an SQL error ('Timeout expired.  The timeout period elapsed prior to completion of the operation or
the server is not responding.') ---> System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation
timed out
   --- End of inner exception stack trace ---
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader()
   at PP.Framework.Model.Sync.Database.SqlDataContext.GetListBlobProperties(Guid itemId, Nullable`1 updateId) in c:\SCM\Workflow Applications MS0\Sync Framework\PP.Framework.Model.Sync.Database\SqlDataContext.cs:line 1147
   --- End of inner exception stack trace ---
   at PP.Framework.Model.Sync.Database.SqlDataContext.GetListBlobProperties(Guid itemId, Nullable`1 updateId) in c:\SCM\Workflow Applications MS0\Sync Framework\PP.Framework.Model.Sync.Database\SqlDataContext.cs:line 1164
   at PP.Framework.Model.Sync.Database.DatabaseProvider`1.ReadModelItem(Type type, Guid id, ISyncModelItem parent, IDatabaseDataContext dataContext, Dictionary`2 itemInfosById, Nullable`1 updateId) in c:\SCM\Workflow Applications MS0\Sync Framework\PP.Framework.Model.Sync.Database\DatabaseProvider.cs:line
421
   at PP.Framework.Model.Sync.Database.DatabaseProvider`1.<>c__DisplayClass2.<StartPrefetching>b__0() in c:\SCM\Workflow Applications MS0\Sync Framework\PP.Framework.Model.Sync.Database\DatabaseProvider.cs:line 189
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
[2014-08-28 16:21:16.631] FATAL (Database Cache Pre-fetch) PP.Workflow.Service.Database.DatabaseWindowsService - Inner Exception (level 1) ('Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.').
System.Data.SqlClient.SqlException (0x80131904): Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader()
   at PP.Framework.Model.Sync.Database.SqlDataContext.GetListBlobProperties(Guid itemId, Nullable`1 updateId) in c:\SCM\Workflow Applications MS0\Sync Framework\PP.Framework.Model.Sync.Database\SqlDataContext.cs:line 1147
ClientConnectionId:2ce295e4-ad9d-4fa5-82e8-06351e1bee00
[2014-08-28 16:21:16.633] FATAL (Database Cache Pre-fetch) PP.Workflow.Service.Database.DatabaseWindowsService - Inner Exception (level 2) ('The wait operation timed out').
System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out.
Has anyone experienced any issues like this?
Thanks
Ian

Hi Ian,
According to your description, the error message indicates SQL Server I/O bottlenecks. The SQL Server I/O bottleneck can be caused by many reasons, for example, there is firmware issue or misconfiguration issue in I/O subsystem , or some other process on
your system is saturating the disks with I/O requests.
To troubleshoot this issue, I recommend the following steps.
1. Exclude SQL Server files from antivirus scan.
2. Do not place SQL Server FILES on compressed drives.
3. Distribute SQL Server data files and transaction log files across drives.
4. Collect perfmon counters to get more information about I/O operation.
For more details, please review this blog:
I/O requests taking longer than 15 seconds to complete on file.
Thanks,
Lydia Zhang

Similar Messages

  • JDeveloper link to MS SQL Server database MDS errors

    The database connection to the SQL server can be successfully created and used (after putting the sqljdbc4.jar file into the project's path). Then when I try to use that db connection for a SOA-MDS connection, the "Messages" tab in JDev displays the following error:
    WARNING: Error reading db partitions for connection name Connection1. Reason : MDS-00003: error connecting to the database
    Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: Error during pool creation in Universal Connection Pool Manager MBean: oracle.ucp.UniversalConnectionPoolException: Error during pool creation in Universal Connection Pool Manager: java.sql.SQLException: Invalid Universal Connection Pool configuration: java.sql.SQLException: Unable to create factory class instance with provided factory class name: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
    To get around this error, I explicitly added the sqljdbc4.jar file to the classpath by doing the following:
    In the jar “C:\Oracle\Middleware_2\jdeveloper\jdev\extensions\oracle.mds.dt.jar”, need to modify the META-INF/extension.xml to include the classpath:
    <classpath>C:/Oracle/Middleware/jdeveloper/lib/sqljdbc4.jar</classpath>
    Once this is done, then I can successfully create the SOA-MDS connection. I can also explore the MDS connection and see the names of available resources. However, the problem then comes again when a resource is actually chosen to be referenced in a composite. When choosing the resource or when trying to build after choosing the resource, an error is displayed that is the same as the original (reference above).
    I tried following both of the workarounds located in the following link, but it does fix the error when attempting to use MDS resources. http://efreedom.com/Question/1-5805190/JDeveloper-DB-Based-MDS-Connection-Issue
    It seems to me like JDeveloper uses multiple different class paths when doing different actions (creating DB link, creating MDS connection, using MDS resources, compiling projects that use MDS resources, etc.).
    Please let me know if you know how to use an MDS that is based in a Microsoft SQL Server DB.
    Ben

    I found a different way to implement the database connection that is used by the SOA-MDS connection. Instead of using the microsoft provided sqljdbc4.jar for the SQLServerDriver, I setup the db connection to instead use the Weblogic provided wlsqlserver.jar. I no longer need any of the workarounds mentioned previously and everything appears to be working. I can navigate the MDS resources as well as viewing and choosing to use them in the composites.
    As a side note, any user that is used for the DB connection for MDS connections must have the SOA_MDS (or DEV_MDS, depending on the setup) schema as its default (Jdev assumes the user’s default schema and thus doesn’t define the whole path). Also, the user must have select and execute privileges on the SOA_MDS schema (direct or role-based) as it needs to query tables and execute stored procs.

  • Oracle and SQL Server Database Link errors

    I am having following error messages while setting up the ODBC connection. I want to access SQL Server tables from within Oracle8i. I have followed all the instruction of Oracle Generic Connectity document and have tested ODBC connection with ODBCPING as well as with TNSPING. Have created Database Link also within Oracle for SQL Server. But when I access the SQL Server table from within Oracle I get the following error messages.
    ORA-12500: TNS:listener failed to start a dedicated server process
    Could any body suggestion the solution please.
    Thanks and regards,
    Ghulam Mallah

    There is a Heterogenous Services/ Generic Connectivity forum that is probably going to have a lot more people familiar with these issues than you'll find in this forum. I would suggest posting over there.
    Justin

  • Configure Synchronization Connections An error has occurred while accessing the SQL Server database

    Hi,
    i am getting following error message
    Central Administration --> Synchronization Connections
    An error has occurred while accessing the SQL Server database or the SharePoint Server Search service.
    If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.
    Central Administration -->  Manage Profile Service: User Profile Service Application --> Manage User Properties
    Error
    An unexpected error has occurred.
    Troubleshoot issues with Microsoft SharePoint Foundation.
    Correlation ID: 3bce5a11-f2dc-4788
    Please tell how to fix it.
    iffi

    Event ID 5555 -> i have change the Timer jobs recycling time AM to PM
    for  User profile page not display  number of count in the page first check services , connection , 
    IISRESET /NOFORCE   /  timer services restart 
    Deepesh Yevle MCTS

  • Error while invoking SQL Server Database

    hello all,
    please help me with this error...I have given the datasource name in the XA datasource tab of connection factory..
    <bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [InsertData.ScsApTransactions]. Caused by weblogic.jdbc.sqlserverbase.ddc: [FMWGEN][SQLServer JDBC Driver][SQLServer]Invalid object name 'dbo.SCS_AP_Transactions'.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-208" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>[FMWGEN][SQLServer JDBC Driver][SQLServer]Invalid object name 'dbo.SCS_AP_Transactions'.</detail></part><part name="code"><code>208</code></part></bindingFault></bpelFault>
    Thanks,

    I figured out the solution for my problem today....
    I have not selected the option "support global transactions " for my Non-XA SQL Server datasource...now i can get the data from SQL Server Database...

  • Microsoft SQL Server 2014 Setup error: Wait on the Database Engine recovery handle failed

    Hi,
    Having this annoying error trying to install SQL Server 2014 (RTM). I saw it's been asked several times... But each post seems a different cause and no definitive answer...
    I'm not doing an upgrade, so no "sa account" issue.
    Tried different media. Even three different distributions: trial, Standard and Enterprise.
    Tried disabling Microsoft antivirus/firewall.
    Of course tried restarting, updating, installing, uninstalling, repairing, etc., etc.
    I noticed the users folders under C:\Users weren't created. (Maybe something related to permissions?) After playing around, I managed for the users to be created and the service started. Though I couldn't log in.

    Summary for last "repair" attempt:
    Overall summary:
    Final result: Failed: see details below
    Exit code (Decimal): -2068578302
    Start time: 2014-04-27 23:54:21
    End time: 2014-04-27 23:59:48
    Requested action: Repair
    Setup completed with required actions for features.
    Troubleshooting information for those features:
    Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
    Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
    Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
    Next step for LocalDB: Use the following information to resolve the error, and then try the setup process again.
    Machine Properties:
    Machine name: CHARLY13C
    Machine processor count: 4
    OS version: Windows 8
    OS service pack:
    OS region: United States
    OS language: English (United States)
    OS architecture: x64
    Process architecture: 64 Bit
    OS clustered: No
    Product features discovered:
    Product Instance Instance ID Feature Language Edition Version Clustered Configured
    SQL Server 2012 DENALI MSSQL11.DENALI Database Engine Services 1033 Enterprise Edition 11.1.3128.0 No Yes
    SQL Server 2012 LocalDB 1033 Express Edition 11.1.3128.0 No Yes
    SQL Server 2014 HEKATON MSSQL12.HEKATON Database Engine Services 1033 Enterprise Edition 12.0.2000.8 No Yes
    SQL Server 2014 HEKATON MSSQL12.HEKATON Full-Text and Semantic Extractions for Search 1033 Enterprise Edition 12.0.2000.8 No Yes
    SQL Server 2014 HEKATON MSSQL12.HEKATON Data Quality Services 1033 Enterprise Edition 12.0.2000.8 No Yes
    SQL Server 2014 Management Tools - Basic 1033 Enterprise Evaluation Edition 12.0.2000.8 No Yes
    SQL Server 2014 Management Tools - Complete 1033 Enterprise Evaluation Edition 12.0.2000.8 No Yes
    SQL Server 2014 Client Tools Connectivity 1033 Enterprise Evaluation Edition 12.0.2000.8 No Yes
    SQL Server 2014 LocalDB 1033 Express Edition 12.0.2000.8 No Yes
    Package properties:
    Description: Microsoft SQL Server 2014
    ProductName: SQL Server 2014
    Type: RTM
    Version: 12
    SPLevel: 0
    Installation location: F:\x64\setup\
    Installation edition: Enterprise
    User Input Settings:
    ACTION: Repair
    AGTDOMAINGROUP: <empty>
    AGTSVCACCOUNT: <empty>
    AGTSVCPASSWORD: <empty>
    AGTSVCSTARTUPTYPE: Manual
    ASCONFIGDIR: Config
    ASSVCACCOUNT: <empty>
    ASSVCPASSWORD: <empty>
    CLTSTARTUPTYPE: 0
    CLTSVCACCOUNT: <empty>
    CLTSVCPASSWORD: <empty>
    CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140427_235420\ConfigurationFile.ini
    CTLRSTARTUPTYPE: 0
    CTLRSVCACCOUNT: <empty>
    CTLRSVCPASSWORD: <empty>
    ENU: true
    FAILOVERCLUSTERGROUP: <empty>
    FAILOVERCLUSTERNETWORKNAME: <empty>
    FTSVCACCOUNT: NT Service\MSSQLFDLauncher$HEKATON
    FTSVCPASSWORD: <empty>
    HELP: false
    IACCEPTSQLSERVERLICENSETERMS: false
    INDICATEPROGRESS: false
    INSTANCENAME: HEKATON
    ISSVCACCOUNT: NT AUTHORITY\Network Service
    ISSVCPASSWORD: <empty>
    ISSVCSTARTUPTYPE: Automatic
    QUIET: false
    QUIETSIMPLE: false
    SQLSVCACCOUNT: NT Service\MSSQL$HEKATON
    SQLSVCPASSWORD: <empty>
    UIMODE: Normal
    X86: false
    Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140427_235420\ConfigurationFile.ini
    Detailed results:
    Feature: Management Tools - Complete
    Status: Passed
    Feature: Client Tools Connectivity
    Status: Passed
    Feature: Management Tools - Basic
    Status: Passed
    Feature: Database Engine Services
    Status: Failed: see logs for details
    Reason for failure: An error occurred during the setup process of the feature.
    Next Step: Use the following information to resolve the error, and then try the setup process again.
    Component name: SQL Server Database Engine Services Instance Features
    Component error code: 0x84B40002
    Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
    Feature: Data Quality Services
    Status: Failed: see logs for details
    Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
    Next Step: Use the following information to resolve the error, and then try the setup process again.
    Component name: SQL Server Database Engine Services Instance Features
    Component error code: 0x84B40002
    Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
    Feature: Full-Text and Semantic Extractions for Search
    Status: Failed: see logs for details
    Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
    Next Step: Use the following information to resolve the error, and then try the setup process again.
    Component name: SQL Server Database Engine Services Instance Features
    Component error code: 0x84B40002
    Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
    Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
    Feature: SQL Browser
    Status: Passed
    Feature: SQL Writer
    Status: Passed
    Feature: LocalDB
    Status: Failed: see logs for details
    Reason for failure: An error occurred during the setup process of the feature.
    Next Step: Use the following information to resolve the error, and then try the setup process again.
    Feature: SQL Client Connectivity
    Status: Passed
    Feature: SQL Client Connectivity SDK
    Status: Passed
    Feature: Setup Support Files
    Status: Passed
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140427_235420\SystemConfigurationCheck_Report.htm

  • Error Connecting to remote sql server database

    The sql server database is hosted on Godaddy hosting service.
    I am able to connect with many other remote computers so the issue resides on the remote computer.
    The remote computer is windows 7 32 bit 2009 service pack 1
    using the ODBC administrator we add a user DSN select SQL Server Version 6.01.7601.17514
    For the server we put in the server from godaddy somthing like   XYZDatabase.db.1110002.hostedresource.com
    Once enter the login id and password we get the following error.
    Any help would much appreciated.
    Remember, we have multiple other remote computers connecting with no issues.

    Hello,
    If connection works for several machines, but fails on others then may because the access is blocked by firewall. You have to unblock IP port 1433 for in- and outbound.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Error message when trying to connect to a SQL Server Database

    All:
    I get the following message when I try to connect to a SQL Server Database within a form:
    "Connection for Source DataConnection failed because the environment is not trusted"
    Can anyone help me solve this problem?
    Thanks,
    BR

    Hi Brian,
    In Acrobat, security concerns dictate that you cannot specify an ODBC connection string by using the Driver=; syntax. Therefore, the client computer using the form needs to have a DSN pre-configured for ODBC connections.
    Denver
    Adobe Enterprise Developer Support

  • SQL Server sysadmin rights error

    Greetings,
    I am trying to install SCCM using a remote SQL configuration, and cannot get past this “SQL Server sysadmin rights” error. When I run the Prerequisite Checker, I put in the SQL server, since I am trying to connect to the SQL default instance, I am typing
    in the server name only, and I put in LOCALHOST for the SDK server.
    After reading another post that this error is not always accurate, I ran the install option and got as far as the following error.
    Server environment is using the following: SCCM 2007 SP2 on Windows 2008 R2 SP1; SQL 2005 SP3 on Windows 2008 R2 SP1
    I am sure the SQL server is configured accurately, I have done this before and use the following links when preparing the SQL server.
    How to Install Configuration Manager Using a Remote SQL Server
    http://technet.microsoft.com/en-us/library/bb693554.aspx
    Appendix B: Configure Remote SQL for WSUS
    http://technet.microsoft.com/en-us/library/dd939912%28WS.10%29.aspx
    I have already added the machine account of the SCCM server to the local Administrators group of the remote SQL server as described in the first link above. The user account I am using for the install also has the
    sysadmin SQL server role assigned.
    Another test that I did to verify the remote SQL server configuration and my user account sysadmin rights, I ran the Prerequisite Checker from another Windows 2008 server in the domain.
    As you can see from the screen shot above, this means something is messed up on my SCCM server and not the SQL server. The following error is from the ConfigMgrPrereq.log.
    <03-29-2012 09:53:22> <<<RuleCategory: Access Permissions>>>
    <03-29-2012 09:53:22> <<<CategoryDesc: Checking access permissions...>>>
    <03-29-2012 09:53:22> Could not connect to SQL database.
    <03-29-2012 09:53:22> SQL2005;    SQL Server sysadmin rights;   
    Error; Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance targeted for site database installation or the SQL Server instance could not be contacted to verify permissions.
    Setup cannot continue.
    <03-29-2012 09:53:22> <<<RuleCategory: Access Permissions>>>
    <03-29-2012 09:53:22> <<<CategoryDesc: Checking access permissions...>>>
    <03-29-2012 09:53:28> LOCALHOST could connect to SQL server.
    <03-29-2012 09:53:30> LOCALHOST;    SMS Provider Communication;   
    Passed
    I know there are plenty of options for verbose logging after installation, but does anyone know if there is a way to do this with the SCCM Prerequisite Checker, before installation? I checked the setup.exe command line switches and there was no option for
    this.
    Any other suggestions would be appreciated, Thanks.

    Yes, my user account is a member of Domain Admins, Enterprise Admins, and Schema Admins. The SQL Server service is running using a service account, and I have also registered the SPN. Below are copies of the log files.
    Conents of the ConfigMgrPrereq.log.
    <03-30-2012 09:10:03> ********************************************
    <03-30-2012 09:10:03> ******* Start Prerequisite checking. *******
    <03-30-2012 09:10:03> ********************************************
    <03-30-2012 09:10:03> CPrereqManager: - Since Registry values empty, this is for fresh installation.
    <03-30-2012 09:10:15> Executing prereq functions...
    <03-30-2012 09:10:15> <<<RuleCategory: Access Permissions>>>
    <03-30-2012 09:10:15> <<<CategoryDesc: Checking access permissions...>>>
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Administrative rights on site system;    Passed
    <03-30-2012 09:10:15> <<<RuleCategory: System Requirements>>>
    <03-30-2012 09:10:15> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Unsupported site server operating system version for setup;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Domain membership;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Schema extensions;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Software updates KB911897;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Software updates KB912818;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Software updates KB913538;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Software updates KB914389;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Software updates KB925903;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Software updates KB932303;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    FAT Drive on Site Server;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Short File Name (8.3) Support (Site system);    Passed
    <03-30-2012 09:10:15> <<<RuleCategory: Dependent Components>>>
    <03-30-2012 09:10:15> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Microsoft Management Console (MMC) version;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Minimum .NET Framework version;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Microsoft XML Core Services 6.0 (MSXML60);    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    WSUS SDK on site server;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    WSUS 3.0 SP1 is required on site server;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Windows Server 2003-based schannel hotfix;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Windows Remote Management (WinRM) v1.1;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    Microsoft Remote Differential Compression (RDC) library registered;    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    MMC updates for Configuration Manager (Software Updates);    Passed
    <03-30-2012 09:10:15> OAGCS-SUV-LDC;    .NET update for Configuration Manager (Software Updates);    Passed
    <03-30-2012 09:10:15> <<<RuleCategory: Access Permissions>>>
    <03-30-2012 09:10:15> <<<CategoryDesc: Checking access permissions...>>>
    <03-30-2012 09:10:15> Could not connect to SQL database.
    <03-30-2012 09:10:15> OAGCS-SAV-WTS1;    SQL Server sysadmin rights;    Error;    Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server
    instance targeted for site database installation or the SQL Server instance could not be contacted to verify permissions. Setup cannot continue.
    <03-30-2012 09:10:15> <<<RuleCategory: Access Permissions>>>
    <03-30-2012 09:10:15> <<<CategoryDesc: Checking access permissions...>>>
    <03-30-2012 09:10:22> LOCALHOST could connect to SQL server.
    <03-30-2012 09:10:24> LOCALHOST;    SMS Provider Communication;    Passed
    <03-30-2012 09:10:24> <<<RuleCategory: System Requirements>>>
    <03-30-2012 09:10:24> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <03-30-2012 09:10:24> LOCALHOST;    Domain membership;    Passed
    <03-30-2012 09:10:24> LOCALHOST;    Short File Name (8.3) Support (Site system);    Passed
    <03-30-2012 09:10:24> LOCALHOST;    Installed version of WAIK (SMS Provider);    Passed
    <03-30-2012 09:10:24> <<<RuleCategory: Dependent Components>>>
    <03-30-2012 09:10:24> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <03-30-2012 09:10:24> ***************************************************
    <03-30-2012 09:10:24> ******* Prerequisite checking is completed. *******
    <03-30-2012 09:10:24> ***************************************************
    <03-30-2012 09:10:24> Updating Prerequisite checking result
    <03-30-2012 09:10:24> Connecting to OAGCS-SUV-LDC registry
    <03-30-2012 09:10:24> Setting registry values
    Contents of the ConfigMgrSetup.log
    <03-30-2012 09:10:03>
    ===================== << Starting SMS V4 SP2 Setup >> =====================
    <03-30-2012 09:10:03> Commandline :
    "E:\CM\CONFIGMGR07SP2_RTM_SELECT_ENU\SMSSETUP\BIN\I386\SETUP.EXE" /prereq /input
    <03-30-2012 09:10:04> This is 64 bit.
    <03-30-2012 09:10:04> Verifying the Reg for AssetIntelligence Installation
    <03-30-2012 09:10:04> Setting the default CSV folder path
    <03-30-2012 09:10:04> SMS Build Number = 6487
    <03-30-2012 09:10:04> SMS Version = 4.0
    <03-30-2012 09:10:04> SMS Minimum Build Number = 800
    <03-30-2012 09:10:04> Verifying SMS Active Directory Schema Extensions.
    <03-30-2012 09:10:04> DS Root:CN=Schema,CN=Configuration,DC=csdtest,DC=csnet,DC=gov
    <03-30-2012 09:10:04> Verifying SMS Active Directory Schema Extensions.
    <03-30-2012 09:10:04> DS Root:CN=Schema,CN=Configuration,DC=csdtest,DC=csnet,DC=gov
    <03-30-2012 09:10:04> The command line options are /PREREQ
    <03-30-2012 09:10:15> IsValidNetBIOSName validation of 'OAGCS-SAV-WTS1' succeeded
    <03-30-2012 09:10:15> IsValidNetBIOSName validation of 'LOCALHOST' succeeded
    <03-30-2012 09:10:15> Registered type OAGCS-SAV-WTS1 MASTER for OAGCS-SAV-WTS1 master
    <03-30-2012 09:10:15> Registered type SMS Master for OAGCS-SAV-WTS1 master
    <03-30-2012 09:10:15> Registered type OAGCS-SAV-WTS1 SMS_ for OAGCS-SAV-WTS1 SMS_
    <03-30-2012 09:10:15> Registered type SMS ACCESS for OAGCS-SAV-WTS1 SMS_
    <03-30-2012 09:10:15> Start prerequisite checking.
    <03-30-2012 09:10:15> Could not connect SQL Server 'master' db.
    <03-30-2012 09:10:15> Could not check if OAGCS-SAV-WTS1 is cluster SQL.
    <03-30-2012 09:10:15> The prereq rules for primary site fresh installation are being run.
    <03-30-2012 09:10:15> Verifying SMS Active Directory Schema Extensions.
    <03-30-2012 09:10:15> DS Root:CN=Schema,CN=Configuration,DC=csdtest,DC=csnet,DC=gov
    <03-30-2012 09:10:15> NtfsDisable8dot3NameCreation is set to 0.
    <03-30-2012 09:10:15> Success in GetMMCVersion. Version is 3.0.
    <03-30-2012 09:10:15> .NET Framework Version: 50727
    <03-30-2012 09:10:15> The current user does not have access right to site OAGCS-SAV-WTS1.
    <03-30-2012 09:10:15> The prerequisite checking stopped on this machine.
    <03-30-2012 09:10:24> NtfsDisable8dot3NameCreation is set to 0.
    <03-30-2012 09:10:27> Completed prerequisite checking.

  • Full Database Backup in DB13 for MS SQL Server databases

    Hello,
    We have some SAP systems using the MS SQL Server database. I want to know if it is possible to setup the Full Database Backup option in transaction DB13 to store the files in a hard disk space.
    I already did this type of configuration in SAP systems in Oracle databases and for this I used the init<SID>.sap where we can put all the configuration, for instance the disk path where we want to save the backup files! But for MS SQL Server databases, in DB13, I don´t know how to do that, when I add the "Full Database Backup" option in DB13, this show me some options but only for tape, but I don´t want to store the backup files in tapes, I want to store/save the files on the server disk itself or else to an external disk but I don´t see where I can set this way of storage!
    This is what you see in DB13 (when using a MS SQL Server database) in "Full Database Backup" and as you see I only have options for TAPE not for a disk or other type of storage! How can I do that? (if that is possible):
    Can you help me please?
    Kind regards,
    samid raif

    Hello Raja
    Sorry for the delay of my answer! Many thanks for that tip, it helps a lot and it solve the last error/problem that I reported here, in fact, the problem was we had named the device with two words containing a space. So we removed that space from the backup device (in SQL management studio) with one word only and the job runs successfully without any errors!
    It works in Development and Quality systems but in our Production system (AM1) the Full backup option in DB13 stopped with the following error, in fact the error is on verification of backup, it means that the Full backup finished with success, but when it does the backup verification, the job in DB13 stops with an error, the following one:
    ***************************** SQL Job information   ******************************
    Jobname:    SAP CCMS Full DB Backup of AM1 [20140417103726-4-103726]
    Type:       TSQL
    DB-Name:    AM1
    For Run:    20140417  10:37:26
    **************************** Job history information  *****************************
    Stepname:   CCMS-step 1
    Command:    declare @exeStmt nvarchar(2000) exec am1.sap_backup_databases @dbList=
                "AM1",@r3Db="AM1",@bDev="fullprd",@expDays= 27,@jobName= "SAP CCMS Ful
                l DB Backup of AM1 [20140417103726-4-103726]",@bkupChecksum="Y",@bkupT
                ype="F",@nativeBkup="N",@exeDate = "20140417103726",@bkupSim = "N",@fo
                rmat = 0,@init = 0,@bkupDb = "AM1",@unload = 0,@exeStmt = @exeStmt OUT
                PUT
    Status:     (success)
    Message:    3014
    Severity:                                                                                                                                                                                                                                                    0
    Duration:   4  hours(s)  41 min(s) 22 sec(s)
    Last msg:   Executed as user: am1. Processed 7434328 pages for database 'AM1', fil
                e 'A01DATA1' on file 1. [SQLSTATE 01000] (Message 4035)  Processed 315
                1504 pages for database 'AM1', file 'A01DATA2' on file 1. [SQLSTATE 01
                000] (Message 4035)  Processed 4574152 pages for database 'AM1', file
                'A01DATA3' on file 1. [SQLSTATE 01000] (Message 4035)  Processed 44363
                92 pages for database 'AM1', file 'A01DATA4' on file 1. [SQLSTATE 0100
                0] (Message 4035)  Processed 25598 pages for database 'AM1', file 'A01
                LOG1' on file 1. [SQLSTATE 01000] (Message 4035)  BACKUP DATABASE succ
                essfully processed 19621974 pages in 16881.638 seconds (9.521 MB/sec).
                 [SQLSTATE 01000] (Message 3014).  The step succeeded.
                        <------------- End of Job Step History --------------->
    Stepname:   CCMS-step 2
    Command:    declare @exeStmt nvarchar(2000) exec am1.sap_verify_backups @nativeBku
                p = "N",@bkupSim = "N",@bDev = "fullprd",@bkupChecksum = "Y",@exeDate
                = "20140417103726",@unload = 1,@dbCnt =1,@exeStmt = @exeStmt OUTPUT
    Status:     (failure)
    Message:    3201
    Severity:                                                                                                                                                                                                                                                   16
    Duration:   0  hours(s)  8  min(s) 30 sec(s)
    Last msg:   Executed as user: am1. Cannot open backup device 'fullprd(\\10.0.0.45\
                backupsap\prd\prdfullqua.bak)'. Operating system error 1265(error not
                found). [SQLSTATE 42000] (Error 3201).  The step failed.
                        <------------- End of Job Step History --------------->
    **************************** Job history information  *****************************
    Can you help me please with this one!? Can you tell me why in verification it stops with that error?
    Kind regards,
    samid raif

  • Unable to install SQL Server 2012 Standard: Error code 0x851A0019

    Hi All,
    I am trying to install sql server 2012 standard edition on windows server 2008R2 but at the end of the installation it is giving me the following error message: 
    "The following error has occurred:
    Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes."
    And in the log file I got the following error message:
    Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
    (I have posted part of the log file)
    Need your help to resolve this issue.
    Thanks,
    MKNayeem

    Hi,
    Thanks for your reply.
    I have already followed that article. I have changed the user to local account user, but it did not work.
    Like you said the sql server is installed, but it is not starting the services. Following is the error log file message:
    2015-03-16 10:12:15.27 Server      Microsoft SQL Server 2012 - 11.0.2100.60 (X64) 
    Feb 10 2012 19:39:15 
    Copyright (c) Microsoft Corporation
    Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
    2015-03-16 10:12:15.27 Server      (c) Microsoft Corporation.
    2015-03-16 10:12:15.27 Server      All rights reserved.
    2015-03-16 10:12:15.29 Server      Server process ID is 5724.
    2015-03-16 10:12:15.29 Server      System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
    2015-03-16 10:12:15.29 Server      Authentication mode is MIXED.
    2015-03-16 10:12:15.29 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\Log\ERRORLOG'.
    2015-03-16 10:12:15.29 Server      The service account is 'NT Service\MSSQL$BNG1SECISO'. This is an informational message; no user action is required.
    2015-03-16 10:12:15.29 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\mastlog.ldf
    2015-03-16 10:12:15.29 Server      Command Line Startup Parameters:
    -s "BNG1SECISO"
    2015-03-16 10:12:15.57 Server      SQL Server detected 2 sockets with 1 cores per socket and 1 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2015-03-16 10:12:15.57 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2015-03-16 10:12:15.57 Server      Detected 16383 MB of RAM. This is an informational message; no user action is required.
    2015-03-16 10:12:15.57 Server      Using conventional memory in the memory manager.
    2015-03-16 10:12:15.67 Server      This instance of SQL Server last reported using a process ID of 2452 at 16-03-2015 07:03:13 (local) 16-03-2015 01:33:13 (UTC). This is an informational message only; no user action is required.
    2015-03-16 10:12:15.67 Server      Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational
    message only. No user action is required.
    2015-03-16 10:12:15.69 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2015-03-16 10:12:15.69 Server      Software Usage Metrics is disabled.
    2015-03-16 10:12:15.70 spid6s      Starting up database 'master'.
    2015-03-16 10:12:15.78 Server      CLR version v4.0.30319 loaded.
    2015-03-16 10:12:15.82 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2015-03-16 10:12:17.36 spid6s      Error: 824, Severity: 24, State: 2.
    2015-03-16 10:12:17.36 spid6s      SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:377; actual 261:2228225). It occurred during a read of page (1:377) in database ID 1 at offset 0x000000002f2000 in
    file 'C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\master.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and
    must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    Thanks
    MKNayeem

  • ERROR – SQL Server Login Failed, Error 11001

    We have an application that uses MSDE as its ‘Back-end’. 
    It has been working fine for years.  We have however had to recently re-build the Operating System on our own Server that it was running on. 
    Original O/S Environment
    We used Windows Server 2008 r2, using
    Hyper-V to run Windows Server 2003 so that we can use
    MSDE to run our application. 
    We do not want to change to later versions of SQL Server Express as they no-longer support Replication.
    NEW O/S Environment
    When we re-built the Server we went for Windows Server 2008 r2, using
    Hyper-V to run Windows 7 Enterprise so that we can use
    MSDE to run our application. 
    We have used this setup many times before and know that MSDE runs quite happily under Windows 7. 
    Servers have been renamed
    The real Windows Server 2008 r2 machine used to be called FILESERVER. 
    It is now called FILE-SERVER.
    The virtual machine running our application was originally called GEMSERVER. 
    It is now called GEM-SERVER. 
    What’s happening on the Server
    The application is running fine.  We can access the underlying MDSE Database with SQL Server 2005 Management Studio Express without problem.
     We can build a test ODBC Data Source and connect to the ‘SQL Server’ Database, again without problems. 
    What’s happening on the Client PC
    The application does not connect.  I get:
         An error occurred while connecting.
         [DBNETLIB]ConnectionOpen (Connect())SQL Server does not exist
         or access denied.
    When I build a ODBC Data Source to test the Connection I get:
    Microsoft SQL Server Login
    Connection failed:
         SQLState: '01000'
         SQL Server Error: 11001
         [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
         (Connect()).
         Connection failed:
         SQLState: '08001'
         SQL Server Error: 6
         [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL
         server not found
    I can Ping GEM-SERVER from the Client PC without problems. 
    I have disabled Firewalls an Anti-Virus Software on both the GEM-SERVER and the Client PC – to no avail. 
    I’ve tried connecting with:
    Named Pipes,
    TCP/IP,
    IP Address of GEM-SERVER – 192.168.16.122,
    Using Specific Port 1433 in connection.
    NONE of it worked.  L
    ANYBODY any ideas what to try next?

    Here's the solution that we came up with to our own problem:
    This problem was actually caused by a bug in our own Application. 
    For some reason when we restored our MDSE Database the correct SQL Server Access Protocols were not setup correctly.  (It is designed to handle these setup issues for us and has done so previously.) 
    We still have to determine why it happened and rectify the problem within our Software. 
    However to correct the problem with our own 'Server' we had to manually:
    Run netsvrcn.exe using command prompt as an Administrator on the ‘Server’ running the MSDE Database,
    Enable TCP and NAMED PIPES protocol
    Restart SQL Server instance
    Exclude the ports SQL Server normally listens on, from the firewall using ‘Windows Firewall Advanced Security’ for both in-bound and out-bound rules:
    1433 TCP port
    1434 UDP port
    We then tested the ODBC connection from client machine and found that it worked fine, as indeed did our application.
    However we still have a residual problem. 
    For we cannot connect to our Server called GEM-SERVER using GEM-SERVER\GEMSQLSRVR we have had to use 192.168.16.122\GEMSQLSRVR. 
    We are not sure why.  We obviously wish to use the machine’s name rather than its IP Address, as its IP Address is dynamically assigned by a DHCP server so may change in future. 
    Do I need to raise this remaining problem as a separate issue?

  • How to create a .mdf SQL Server database from a Data-Tier Application file that has data?

    This is a noob question, though I do use SQL Server databases all the time with Entity Framework when I code in C# using Visual Studio 2013.  The development environment is found below at [A].  I am trying to make a clone of a SQL Server 2008 R2
    database (.mdf)  that exists online.  I can read, connect and work with this database in Visual Studio 2013, but I wish to make a local copy of the database, as an .MDF file.  Somewhere in my notes I have a way of creating a local copy from
    an online database when using Visual Studio but I forgot how (it seems, reviewing my notes, that it deals with ADO.NET which is deprecated in Visual Studio 2013 these days, or so it seems).  So I'm looking for another way.  What I did was create
    (or export) a "Data-Tier Application File" from the online SQL Server database, with data, and it seems to have worked in that this Data-Tier Application file exists on my hard drive and seems to have data in it ("SQL Server Replication Snapshot"
    is the format it seems).  It contains skeleton code to create a database, but when I tried to execute it with SQL Server 2014 Management Studio, I got a bunch of errors.
    So my question is:
    1) Can I somehow create a .MDF SQL Server Database from an Data-Tier Application file that has data?  What tool do I use?  I saw this link, http://social.technet.microsoft.com/wiki/contents/articles/2639.how-to-use-data-tier-application-import-and-export-with-a-windows-azure-sql-database.aspx 
    and it relates to Azure, but is there a tool for C#Visual Studio 2013, standalone?
    2) If there's an easy way to create a .mdf SQL Server Database file from an online file, within SQL Server Management Studio?  I don't think so, since it would require Administrator permissions on the online server, which I don't have. I have permission
    to read, update, delete the online database file, but strangely not to download it (the service I use has a tool for backup, but not for download).
    3) same question as 2), but for Visual Studio 2013?  I don't think so, since I notice none of the templates even mentions ADO.NET anymore, but instead they go with Entity Framework.  Using EF I can of course do anything I want with the online database
    (CRUD), but it remains online.  Maybe there's a switch to make a local copy?  I guess I could write a short program to suck all the data out of the online database and put it into a new, duplicate database having the same tables, that I create on
    my localhost, but my question here is if there's an easier way than this, maybe a tool or command I can run from inside Visual Studio?
    Any advice on any of the above questions is appreciated.
    Thank you,
    Paul
    [A] Microsoft Visual Studio Professional 2013
    Version 12.0.21005.1 REL
    Microsoft .NET Framework
    Version 4.5.51641
    Microsoft Web Developer Tools 2013   2.0.40926.0
    SQL Server Data Tools   12.0.30919.1
    Microsoft SQL Server Data Tools
    Windows Azure Mobile Services Tools   1.0
    Windows Azure Mobile Services Tools

    Thanks but these links are too general to help.
    "2. what do you mean by online file?" - I mean the SQL Server database file is on a remote web server that I rent from, but I am not the administrator of.  I can access my database using SQL Server Authentication, but nothing more.
    Paul
    What do you mean by too general? It explains on how you can use data tier application to create and deploy databases
    May be this will help you to understand better
    http://www.databasejournal.com/features/mssql/article.php/3911041/Creating-Data-Tier-Applications--in-SQL-Server-2008-R2.htm
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Unable to connect to sql server database

    i run on CMD:
    aspnet_regsql -C "Data Source  =Davidchamoun/sqlexpress : intergrated security= true" -ssadd -sstype p
    i got 
    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: 25 – connection string is not valid
    unable to connect to sql server database.
    im using sql sever 2012 express, microsoft visual studio web 2008 express.
    please help me.

    i run it as :
    aspnet_regsql -C "Data Source =Davidchamoun\sqlexpress : integrated security= true" -ssadd -sstype p
    i got the same error :
    an error has occurred . details of the exception:
    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: 25 – connection string is not valid
    unable to connect to sql server database.
    im using also windows 8.1
    pls help me
    ty for ur reply

  • Not able to connect with Sql Server Database

    Hi,
    I'm not able to connect with Sql Server database.during making connection I'm getting the following error:
    "Status : Failure -I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property."
    Please help
    Regards,
    Neeraj Goel

    Hi,
    I'm using Sql Server 2000.
    I downloaded the driver from the given site and still having the same problem. Do I need to copy the driver file in some specific folder.
    Regards,
    Neeraj Goel

Maybe you are looking for