Crystal 8.5 Error #599 Cannot open SQL Server
I have a user who is viewing Crystal reports (8.5 i think) from a window inside GoldMine CRM software.
they are getting an error saying Error #599: Cannot open SQL server.
Any ideas?
We don't support third party applications. Post your question to GoldMine Support
Similar Messages
-
Cannot open SQL Server error on 64 bit Windows 7
I have a client running a Crystal 8.5 report that includes an embedded subreport. The subreport based on a second database is not updating and sometimes the report reports an error "Cannot open SQL Server".
The database is open and available, and the report works on a 32-bit XP machine on the same database with the exact same report on the same network.
The report works on my development machine with the clients database and the exact same report (my system is Windows 7 32-bit) - different office setup.
Because the report only has problems on the 64-bit, I am wondering if there is a pathing problem from the Program files (x86) or some such issue.
I have copied the files in the c:\Windows\Crystal directory to the c:\Windows\system32 directory. I've come across issues with Terminal Services that required this in the past.
If it matters, the main report is based on the MS Text Driver running off csv files and the subreport is based on a MySQL database using the 3.51 ODBC driver.
Does anyone know any issues and/or solutions related to running Crystal/32 bit programs on a 64 bit system?
TIA, rasinc.CR 8.5 is not supported on 64 bit OS's or ANY Terminal Servers.
The location for 32 bit applications on a 64 bit OS is \windows\syswow64.
Good luck
Don -
Tons of Cannot Find SQL Server errors in ULS log
Background: I inherited the maintenance of this farm. The previous consultant migrated the client from WSS 3.0 to 2013 by way of 2007 MOSS and 2010 (unsure of version). I do not know if there was a "temporary" SQL server used during this process
that no longer exists. It seems likely given all of the errors regarding a missing SQL server.
The current 2013 Enterprise farm contains 1 WFE and 3 App servers, 2 of which comprise the search topology. There is one SQL server, not aliased. All machines are VMs. One of the search servers (App) is on a different ESXi host. The timer job that is creating
all of the ULS errors is running on the WFE. Beyond that, the farm has these symptoms:
It "works" albeit very slowly. Crawl rate of 2-7 dps for both external file shares and the SP content (both with and without Task Offloading / Chimney Offloading enabled). It seems to frequently recycle or take an otherwise long time to render
in the browser (any page). Finally, it spews tens of thousands of errors 24x7 on the WFE saying a SQL server (unnamed) cannot be contacted via Named Pipes.
Specifically: "Unknown SQL Exception 53 occurred. Additional error information from SQL Server is included below. 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)".
The next error in the sequence is: "An internal error occurred while running a timer job: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject,
UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)..."
This is followed by an error such as this: "There was an internal error invoking the timer job '{E4DDC92E-0056-4E7E-BD3F-1CF5670ACB7D}' for service '{6105D588-FB34-4F1C-82F6-479D7FE146EA}'."
Of course, each time the timer job mentioned is different.
One more error appears consistently with these although not as frequently: "The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPDiagnosticsMetricsProvider (ID 36e6942a-9a80-440f-94a4-e4a606362734) threw an exception. More information
is included below. Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in
time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=21276; handshake=0;"
I have been troubleshooting this for days but am not making much progress. How can I determine just what SQL server it says it cannot find and where that server name is stored? It seems like it has to be part of the Timer job configuration since the two
things are related.Hi,
Thanks for your sharing and have a good day.
Jason
Jason Guo
TechNet Community Support -
Cannot open SQL connection to liveCache LCA
Hi All,
when I'm trying to start liveCache I'm getting an error: "Cannot open SQL connection to liveCache LCA".
Operational state is online.
Kernel - 7.7.07
Next steps are successful:
"LC10 -> liveCache monitoring -> Tools -> dbmcli ::
a) sql_execute select * from users"
From Alert monitor I see an error: "Instance ONLINE, but no SQL access possible". If i try connection test, thenI see:
1. Connect. test with "dbmcli db_state" Successful
2. Connect. test with command mode "dbmrfc db_state" Successful
3. Connect. test with session mode "dbmrfc db_state" Successful
4. Connect. test with "native SQL" ( LCA ) No connection
SQL Code: 4025
For detailed information, see the developer trace for work process: 2
How to see this developer trace I do not know...Mark, I have this tool installed.
In those logs I found that:
Thread 0x1A8 Task 35 2010-11-30 23:30:20 Pager 20018: First DataCacheSegment:31
Thread 0x1A8 Task 1 2010-11-30 23:30:21 SrvTasks 31: Permanently reserved 13 servertasks for 'Backup / Restore'.
Thread 0x1A8 Task 1 2010-11-30 23:30:21 SrvTasks 31: Permanently reserved 2 servertasks for 'Backup / Restore'.
Thread 0x1A8 Task 1 2010-11-30 23:30:21 SrvTasks 31: Permanently reserved 1 servertasks for 'Savepoint'.
Thread 0x1A8 Task 1 2010-11-30 23:30:21 RTETask 18: Kernel initialization done
DESCRIPTION:
The initialization of the Kernel components has finished. All special tasks are started now.
Thread 0x1A5 Task - 2010-11-30 23:30:21 RunTime 3: State changed from STARTING to ADMIN
Thread 0x1A5 Task - 2010-11-30 23:30:21 STATE 19601: SERVERDB is ready
============================================ begin of write cycle ==================
Thread 0x1AA Task 71 2010-11-30 23:30:22 CONNECT 19633: Connect req. (LCI, T71, connection obj. 0x000007FFFFE30BF0, Node:'kleva', PID: 6676)
Thread 0x1AA Task 71 2010-11-30 23:30:22 ERR RTEIO 12: attach of volume DATA_VOLUME_0001 failed during open,VOLUME_NO=1,_FILE=RTEIO_VolumeInfo-k.cpp,_LINE=1776
DESCRIPTION:
An error accurred when trying to add the volume DATA_VOLUME_0001 with the logical number 1 to the configuration and physically attach it.
ACTION:
Contact your system administrator. Show him the error message which points to an operating system configuration error and then contact the database support if your system administrator can not fix the error.
2010-11-30 23:30:22 ERR RTEIO 1: The opening of path 'C:\sapdb\LCI\sapdata\DISKD0001' failed,DESCRIPTION=CreateFile(READWRITE,OPEN_EXISTING),ERRORTEXT=The system cannot find the file specified.
,RETURNCODE=2,_FILE=RTEIO_VolumeInfo-k.cpp,_LINE=2385
DESCRIPTION:
An attempt to open the path 'C:\sapdb\LCI\sapdata\DISKD0001' failed. The operating system returned the error code 2 and the error text 'The system cannot find the file specified.
'. The complete command line reads 'CreateFile(READWRITE,OPEN_EXISTING)'.
Thread 0x1AA Task 71 2010-11-30 23:30:22 ERR Admin 3: Database state: OFFLINE,_FILE=Kernel_Administration.cpp,_LINE=692
2010-11-30 23:30:22 KernelComm 6: Internal errorcode, Error code 9050 "disk_not_accessible"
2010-11-30 23:30:22 ERR Admin 20017: RestartFilesystem failed with 'I/O error',_FILE=Kernel_Administration.cpp,_LINE=410
Thread 0x1AA Task 71 2010-11-30 23:30:22 CONNECT 19651: Connection released (LCI, T71, connection obj. 000007FFFFE30BF0)
Thread 0x1AA Task 71 2010-11-30 23:30:22 RTEKernel 112: Offline KILL requested
Thread 0x1AA Task 71 2010-11-30 23:30:22 RunTime 3: State changed from ADMIN to SHUTDOWNKILL
Thread 0x1A0 Task - 2010-11-30 23:30:22 ERR Messages 7: Begin of dump of registered messages,_FILE=Msg_List.cpp,_LINE=3527
Thread 0x1A0 Task - 2010-11-30 23:30:19 RTEHSS 13951: No hot standby node configured -> No HotStandby configuration
Thread 0x1A0 Task - 2010-11-30 23:30:22 ERR RTEIO 1: The opening of path 'C:\sapdb\LCI\sapdata\DISKD0001' failed,DESCRIPTION=CreateFile(READWRITE,OPEN_EXISTING),ERRORTEXT=The system cannot find the file specified.
,RETURNCODE=2,_FILE=RTEIO_VolumeInfo-k.cpp,_LINE=2385
DESCRIPTION:
An attempt to open the path 'C:\sapdb\LCI\sapdata\DISKD0001' failed. The operating system returned the error code 2 and the error text 'The system cannot find the file specified.
'. The complete command line reads 'CreateFile(READWRITE,OPEN_EXISTING)'.
Thread 0x1A0 Task - 2010-11-30 23:30:22 ERR RTEIO 1: The opening of path 'C:\sapdb\LCI\sapdata\DISKD0001' failed,DESCRIPTION=CreateFile(READWRITE,OPEN_EXISTING),ERRORTEXT=The system cannot find the file specified.
,RETURNCODE=2,_FILE=RTEIO_VolumeInfo-k.cpp,_LINE=2385
DESCRIPTION:
An attempt to open the path 'C:\sapdb\LCI\sapdata\DISKD0001' failed. The operating system returned the error code 2 and the error text 'The system cannot find the file specified.
'. The complete command line reads 'CreateFile(READWRITE,OPEN_EXISTING)'.
Thread 0x1A0 Task - 2010-11-30 23:30:22 KernelComm 6: Internal errorcode, Error code 9050 "disk_not_accessible"
Thread 0x1A0 Task -Thread 0x1A0 Task - 2010-11-30 23:30:22 ERR Admin 3: Database state: OFFLINE,_FILE=Kernel_Administration.cpp,_LINE=692
2010-11-30 23:30:22 KernelComm 6: Internal errorcode, Error code 9050 "disk_not_accessible"
2010-11-30 23:30:22 ERR Admin 20017: RestartFilesystem failed with 'I/O error',_FILE=Kernel_Administration.cpp,_LINE=410
Thread 0x1A0 Task -Thread 0x1A0 Task - 2010-11-30 23:30:22 ERR Messages 8: End of the message list registry dump,_FILE=Msg_List.cpp,_LINE=3555
Thread 0x1A0 Task - 2010-11-30 23:30:22 RTEKernel 61: rtedump written to file 'rtedump'
Thread 0x1A6 Task 3 2010-11-30 23:30:22 Trace 20000: Start flush kernel trace
Thread 0x1A0 Task - 2010-11-30 23:30:22 RTEKernel 111: Tracewriter resumed
Thread 0x1A0 Task - 2010-11-30 23:30:22 RTEKernel 94: Waiting for tracewriter to finish work
Thread 0x1A0 Task - 2010-11-30 23:30:22 RTEKernel 116: Tracewriter termination timeout: 1200 seconds
Thread 0x1A6 Task 3 2010-11-30 23:30:22 Trace 20001: Stop flush kernel trace
Thread 0x1A6 Task 3 2010-11-30 23:30:22 Trace 20002: Start flush kernel dump
Thread 0x1A6 Task 3 2010-11-30 23:30:22 Trace 20003: Stop flush kernel dump
Thread 0x1A6 Task 3 2010-11-30 23:30:22 RTEKernel 110: Releasing tracewriter
Thread 0x1A0 Task - 2010-11-30 23:30:22 TASKING 19822: Thread 6712 joining
Thread 0x1A0 Task - 2010-11-30 23:30:22 TASKING 19822: Thread 6868 joining
Thread 0x1A0 Task - 2010-11-30 23:30:22 RTEThread 13: The thread Requestor_LCI is finished
Thread 0x1A0 Task - 2010-11-30 23:30:22 RTEThread 13: The thread LegacyRequestor is finished
Thread 0x1A0 Task - 2010-11-30 23:30:22 TASKING 19822: Thread 6836 joining
Thread 0x1AC Task - 2010-11-30 23:30:22 RTE 20214: CONSOLE thread stopped
Thread 0x1A0 Task - 2010-11-30 23:30:22 TASKING 19822: Thread 6716 joining
Thread 0x1A0 Task - 2010-11-30 23:30:22 TASKING 19822: Thread 6860 joining
Thread 0x1A0 Task - 2010-11-30 23:30:22 TASKING 19822: Thread 6708 joining
Thread 0x1A0 Task - 2010-11-30 23:30:22 TASKING 19822: Thread 6864 joining
Thread 0x1A0 Task - 2010-11-30 23:30:22 RTEKernel 58: Backup of diagnostic files will be forced at next restart
Thread 0x1A0 Task - 2010-11-30 23:30:22 RTEKernel 118: SERVERDB LCI has stopped
2010-11-30 23:30:22 RTEKernel 14: Kernel version: Kernel 7.7.04 Build 029-123-196-543
Thread 0x1A0 Task - 2010-11-30 23:30:22 RunTime 3: State changed from SHUTDOWNKILL to STOPPED
Thread 0x1A0 Task - 2010-11-30 23:30:22 TENANT 20005: Tenant database LCI has stopped
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Looks like I'm not authorized to created folders/files in 'C:\sapdb\LCI\sapdata\'? But I can... -
SAP Management Console : Error : MMC cannot open the file
We are installing the xmii system on a server, it was not installed completely.
Now we have deleted the xMII folders from Add and Remove in Control Panel.
After deleting these folders, when we are opening SAP Management Console, it is giving one <b>Error MMC cannot open the file "C:\WINDOWS\sapmmc.msc."</b>
Please help us to resolve this problem, we have no idea to resolve the same.
Regards,
Study SAPHi Alin,
Thanks for your reply, we have deleted only folders
- SAP xMII 11.5
- SAP xMII CMS 11.5
- SAP xMII Security 11.5
- Microsoft SQL Server folder
from control panel --> add and remove folder, when we were deleting these folders, IIS services were stopped by the system. After deleting the same we faced this problem.
Regards,
Study SAP -
Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"
I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 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.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server -
Cannot open SQL connection to liveCache LCA - SCM 5.0, LC 14
Good day,
After initial installation, MSSQL kernel 111 and LC 7.6.00 all working fine.
After patching the kernel to 146 and LC to 14, I get "Cannot open SQL connection to liveCache LCA" accompanied by the following in the trace files:
Loading SQLDBC client runtime ...
SQLDBC SDK Version : SQLDBC.H 7.6.0 BUILD 007-123-091-175
SQLDBC Library Version : libSQLDBC 7.6.3 BUILD 012-123-169-237
SQLDBC client runtime is MaxDB 7.6.3.012 CL 169237
SQLDBC supports new DECIMAL interface : 0
SQLDBC supports VARIABLE INPUT data : 1
Try to connect as LC5ADM/<pwd>@MBDEVSCM-LC5 on connection 1 ...
ue Apr 08 23:12:14 2008
ERROR => Connect to database failed, rc = -4008 (POS(1) Unknown user name/password combination)
bsdbsql.cpp 200]
***LOG BY2=> sql error -4008 performing CON [dbds#1 @ 1044] [dbds 1044 ]
***LOG BY0=> POS(1) Unknown user name/password combination [dbds#1 @ 1044] [dbds 1044 ]
Connect to LCA as LC5ADM with MBDEVSCM-LC5
Try to connect as LC5ADM/<pwd>@MBDEVSCM-LC5 on connection 1 ...
My User LC5ADM does work, I can connect with a SQL_CONNECT in dbmcli.
Is the following a possibility:
Version of SQLDBC SDK Version : SQLDBC.H 7.6.0 BUILD 007-123-091-175?
My kernel versions of dbmssslib.dll and dbmssslib.pdb(146?)
Should I patch dbmssslib.dll and dbmssslib.pdb to 152(available on SAPnet).
Many Thanks in advance,
DerekHi Natalia,
Thank you for your reply. I have already checked these from a previous post you have on SDN.
Here is the output of the commands for your review. The user LC5ADM is the correct user, here we go:
sql_execute select * from users
LC5>OK
END
'CONTROL';'';'CONTROL';'ADMIN';'MULTIPLE';(null);(null);(null);'DEFAULT';'20080408';'00170104';'20080408';'00170104';'20080408';'00170104';'LC5';'MBDEVSCM.neusiedler.local';0;'NO';(null)
'SUPERDBA';'';'SUPERDBA';'SYSDBA';'MULTIPLE';(null);(null);(null);'DEFAULT';'20080408';'00170104';'20080410';'00190253';'20080408';'00170104';'LC5';'MBDEVSCM.neusiedler.local';10;'NO';(null)
'SUPERDBA';'';'LC5ADM';'DBA';'MULTIPLE';(null);(null);(null);'UNICODE';'20080408';'00170116';'20080408';'00170116';'20080409';'00221530';'LC5';'MBDEVSCM.neusiedler.local';28;'NO';(null)
sql_execute user-type=SAP select user from dual
LC5>OK
END
'LC5ADM'
I have since deleted and recreated LCA, LDA and LEA.
When I tried to start LC, got the following error:
10.04.2008 19:36:32
Server: MBDEVSCM
Users: GALTD
Logical Command: DBMRFC
Parameter: exec_lcinit restart
Name and Server : LC5 - MBDEVSCM
DBMRFC Function : DBM_EXECUTE
Command : exec_lcinit restart
Error : DBM Error
Return Code : -24964
Error Message : ERR_EXECUTE: error in program execution#
Here is the contents of the trace file:
race file:
Loading SQLDBC client runtime ...
SQLDBC SDK Version : SQLDBC.H 7.6.0 BUILD 007-123-091-175
SQLDBC Library Version : libSQLDBC 7.6.3 BUILD 012-123-169-237
SQLDBC client runtime is MaxDB 7.6.3.012 CL 169237
SQLDBC supports new DECIMAL interface : 0
SQLDBC supports VARIABLE INPUT data : 1
SQLDBC supports keepAlive indicator : 0
Try to connect as LC5ADM/<pwd>@MBDEVSCM-LC5 on connection 1 ...
hu Apr 10 19:38:57 2008
ERROR => Connect to database failed, rc = -4008 (POS(1) Unknown user name/password combination)
bsdbsql.cpp 208]
***LOG BY2=> sql error -4008 performing CON [dbds#1 @ 1044] [dbds 1044 ]
***LOG BY0=> POS(1) Unknown user name/password combination [dbds#1 @ 1044] [dbds 1044 ]
Connect to LCA as LC5ADM with MBDEVSCM-LC5
Try to connect as LC5ADM/<pwd>@MBDEVSCM-LC5 on connection 1 ...
hu Apr 10 19:38:58 2008
ERROR => Connect to database failed, rc = -4008 (POS(1) Unknown user name/password combination)
bsdbsql.cpp 208]
***LOG BY2=> sql error -4008 performing CON [dbds#1 @ 1044] [dbds 1044 ]
***LOG BY0=> POS(1) Unknown user name/password combination [dbds#1 @ 1044] [dbds 1044 ]
Connect to LCA as LC5ADM with MBDEVSCM-LC5
Try to connect as LC5ADM/<pwd>@MBDEVSCM-LC5 on connection 1 ...
Any other suggestions will be appreciated.
Thank you and Regards,
Derek -
i bought an eBook from iTunes. I can view/read it perfectly on my iPhone but when I try to open the eBook file on my iPad, I get the error message, "Cannot open book. This book is protected by an incompatible technology." Any ideas for me? thx
Welcome to the Apple Community.
I have seen previous versions mentioned in a pop up message before on iCloud.com, but I'm not really sure at all how it would help, as I couldn't get it to do anything.
The best advice I have at this time is to back up your work on your iOS device by regularly saving it to iTunes, if anything goes wrong you can then either load it into the numbers app again on the device or recover it via iTunes on your computer.
My syncs are immediate, I never get chance to see if it works in the background, sorry. -
2010 Review Approval Workflow Error - Outlook cannot open a new form
Hi,
I set up an Approval - SharePoint workflow on a document library list in a webpart. When the approver got the email and tried to approve from outlook, she received the following error. She has approved documets in the past for the same page.
Can anyome please help me troubleshoot this? So much appreciated!
Word Error:
Could not open. http://<site ulr> _layouts/formsResource.aspx?templateFile=http://<site url_catalogs/wfpub/Approval - SharePoint 2010/Review Approval_Task_1033.xsn
Outlook Error:
Outlook cannot open a new form. To open the file, access to the folliwng form template is required
http://<site ulr> _layouts/formsResource.aspx?templateFile=http://<site url_catalogs/wfpub/Approval - SharePoint 201o/Review Approval_Task_1033.xsncan she open the approval form in web browser instead of Outlook?
According to the error message, it seems that the user does not have permission for the file http://<site url/_catalogs/wfpub/Approval - SharePoint 201o/Review Approval_Task_1033.xsn.
can she open see this file in SharePoint designer 2010? that is, open the site with SharePoint designer and navigate to All Files->_catalogs->wfpub->Approval - SharePoint 201o. If she can not see the file there, ask the workflow creator to publish
the workflow again. I had experienced strange issue in SharePoint designer 2007 and solved by check out all the workflow files and check in again
http://social.msdn.microsoft.com/Forums/en-US/sharepointworkflow/thread/b533cfa5-e858-4ff9-bd0d-96d19946b789. -
I just tried to update Firefox to version 9.0.1. It got to 13% extracting, then I got the error message, Cannot Open Output File.
The file could be downloaded incorrectly. Could you redownload it again from [http://getfirefox.com http://getfirefox.com]?
-
Plugin development for premiere, adobe example error LNK1104: cannot open file 'C:\Program Files\Ad
Hello,
I downloaded the Premiere Pro CS 5.5 Win SDK, i open the project SDK_Exporter in Visual Studio 2008, when i hit debug i get the following error
Error
1
fatal error LNK1104: cannot open file 'C:\Program Files\Adobe\Common\Plug-ins\CS6\MediaCore\ExporterSDK.prm'
How can i resolve ?RESOLVED LOOKING AT THE PAST
1.Zac Lam,01-dic-2013 10:43 in reply to Alex B MartinReport
Hi Alex, Are you launching Visual Studio with administrative privileges? If not, you won’t be able to generate the .aex in certain protected folders because of a Windows security restriction.
Was this helpful? Yes No
Reply
|Mark as:
Unmark as Correct
|Translate
7 posts
03-ene-2013
2.Alex B Martin,01-dic-2013 12:34 in reply to Zac Lam
Yes it works, thanks Note: For CS 5.5 Administrative privileges are not need, so thats only with visual studio 2010 and premiere cs6 where i need to run vs2010 as admin. -
having problems opening a pdf file with reader 10/11 get error msg cannot open close reader and try again any ideas
Hi George ,
Is it happening with all the PDF' or any specific one?
Could you please share the error message so that we can replicate at our end ?
Try repairing reader once and see if that fixes the issue.
Launch Reader>Navigate to Help>Repair Adobe Reader Installation
Regards
Sukrit Dhingra -
SAP Management Console : Error MMC cannot open the file "C:\WINDOWS\sapmmc.
Hi Experts,
We are installing the xmii system on a server, it was not installed completely.
Now we have deleted the xMII folders from Add and Remove in Control Panel.
After deleting these folders, when we are opening SAP Management Console, it is giving one <b>Error MMC cannot open the file "C:\WINDOWS\sapmmc.msc."</b>
Please help us to resolve this problem, we have no idea to resolve the same.
Regards,
Study SAPHi,
Looks like your mmc dll is corrupted, with your install and uninstall of software.
Two Options:
1. Upgrade the Kernel with latest Patch level, which comes with new SAPMMC.dll file
OR
2. Just download the SAPMMC*.sar file from service market place and extract in exe directory, since it is windows re-booting the server doesn't hurt.
Hope this helps. points are welcome.
-K -
Error LNK1104: cannot open file 'MSCOREE.lib'_In visual studio 2013
Hi,
I have upgrade the window application from vs 2008 to vs 2013 after upgradation, when i m trying to build madelineDll I am getting this error LNK1104: cannot open file 'MSCOREE.lib'
MadelineDLL
Can someone help me to resolve this ASAp.
Thanks in advance
Archana K.Hello archana,
From your description, this exception seems to be related with the C++, if so, i suggest you could post this issue to the C++ forum and i notice that this issue is caused by the upgradation of Visual Studio, you could aslo ask it on the Visual
Studio forum to confirm if the VS2013 has some changes compared with VS2008. I move it to the where the forum for, there are forum experts would help redirect it to a proper forum.
The current forum you posted to is for .NET class libraries.
Regards
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Hi Folks:
I am doing one Dll file for TestStand , and got an error : d:\teststand3.5\teststand 3.5\examples\modaldialogs\mfc\tsapivc.h(18) : fatal error C1083: Cannot open type library file: '..\..\bin\TsAdpApi.tlb': No such file or directory
Could anyone help me out of that ??
Thanks in advance !This type library for the adapter API is embedded in the teapi.dll. If you are using Visual Studio.NET, there is an attribute called tlbid that you can use with the #import directive in order to import that embedded library (see the MSDN documentation for more details). For example:
#import tlbid(2)
In VC++ 6.0, there is no way to import embedded type libraries. Therefore, you must use the attached type library file (.tlb) with the #import directive. For example:
#import "TsAdpApi.tlb"
Maybe you are looking for
-
Why i can´t active my Imessage account...i try everything.
Hello : I have tried all possible ways to activate iMessage ...Still nothing. Always say : Waiting Activation.
-
Content Server 6.40 on Raw Devices
Hi Folks! We'd like to install a Content Server 6.40 using raw devices (on Linux Suse SLES9). Do we need to install the MaxDB, if we use raw devices? At this point the InstGuide does not give a clear description of what to do. It looks we can use the
-
How to replace/ rename a certificate after ABAP refresh in STRUST
The system was refresh to Quality from Dev. My question was how do I replace (rename) the certificate from QA to DEV in strustsso2 or strust. The version of ABAP is 7.0. Thanks.
-
Hi All, we are having an issue in workflow, at a step where the system must send a notification (email), leveraging rule 00000168 (superior). Can anybody advice / give some hints? Thank you! Error '9' when calling service 'SO_OBJECT_SEND' Message no.
-
I have a problem that my ipad could not connect or sync to my pc, my iphone could but my ipad couldn't. I tried more than step all of them didn't work,restore or launching in safe mode or reboot, all of them didn't work, help please