HTTP Service Fails on Install
Dear Readers:
I hope you can help me to debug an error I am getting on install of both the Oracle 9i database (9.2.0.1.0) and the Oracle9iAS Release 1 (V1.0.2.2). After the database install is complete I am getting the following error on the start up of the HTTP Service:
[Fri Jul 12 22:59:38 2002] [crit] (10045)The attempted operation is not supported for the type of object referenced: Parent: WSADuplicateSocket failed for socket 1028.
[Fri Jul 12 22:59:38 2002] [error] master_main: create child process failed. Exiting.
[Fri Jul 12 23:00:38 2002] [error] forcing termination of child #0 (handle 1256)
[Fri Jul 12 23:08:28 2002] [crit] (10045)The attempted operation is not supported for the type of object referenced: Parent: WSADuplicateSocket failed for socket 1092.
[Fri Jul 12 23:08:28 2002] [error] master_main: create child process failed. Exiting.
[Fri Jul 12 23:09:28 2002] [error] forcing termination of child #0 (handle 1320)
As far as I know I am taking care to uninstall according to the documentation and reinstall; however, I am still getting the same errors. I hope someone can help with this very urgent request, as I have a demo to show a client next Friday.
Bests,
Harjeet
I was just able to get it working on mine on a VMMR2 Cluster (hyper-v on 2012 and 2012 R2 hosts with the same success) and the Service Template using a VM template with Server 2008R2 Enterprise. I don't know if you did the same steps but:
created a fresh VM in VMM - install Virtual Guest Services.
convert that VM to a VM Template - VMM then copies the VM files to a location on your VMM Library.
create Service template using the new VM template - with no services.
I've had problems in the past with trying to convert a VM to a template, and the VM would fail at the 'Fix up differencing disks' .. It wasn't until I did a fresh install instead of trying to convert a VM copy of a copy of a copy of a V2V migration..
Mine completes successfully but with an error couldn't install Virtual Guest Services when they are already installed. hmmm.. The VM/Service is running fine however.
---------------------------- Error I got -------------------------------
Error (13233)
Unable to install Virtual Guest Services on virtual machine TEST_SERVICE. The Hyper-V Integration Services setup exited with error code 60001.
Recommended Action
For more information, refer to the Hyper-V documentation for virtual machine integration services at
http://go.microsoft.com/fwlink/?LinkId=118036 and then try the operation again.
Similar Messages
-
Windows Search Service failing to install on Windows Server 2008 R2 Terminal Server
Hi,
I am unable to install the Windows Search Service on a Server 2008 R2 Terminal Server. I want to install this to enable indexing options within Outlook 2013 for all users.
Server Manager > Add Roles > File Services > Select only Windows Search Service > Install.
The error I receive: "Attempt to configure Windows Search Service failed with error code 0x80070057. The parameter is incorrect."
Thanks,
BjornHi,
I did the test and could install the Windows Search Service without problem.
Which role did you installed on the terminal server?
Did you try to install it on another windows server?
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Installation issue : sql server 2008 r2 some services failed to installed on windows 7
I have been facing this problem while installing sql server 2008 r2.. i tried so many times but same result .. it shows sql server installed with some errors
database engine service : failed
SQL Server Replication : failed
Full-Text Search : failed
Analysis Services : failed
Reporting Services : failed
And my Log file (or) summary file is (it is in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log):
Overall summary:
Final result: User cancelled
Exit code (Decimal): -2068380094
Exit facility code: 1207
Exit error code: 1602
Exit message: User has cancelled.
Start time: 2014-08-14 21:15:26
End time: 2014-08-14 21:23:58
Requested action: AddNode
Machine Properties:
Machine name: MANJU-PC
Machine processor count: 4
OS version: Windows Vista
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Database Engine Services
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER SQL Server Replication
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Full-Text Search
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSAS10.MSSQLSERVER Analysis Services
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSRS10.MSSQLSERVER Reporting Services
1033 10.0.1600.22
No
Sql Server 2008
Management Tools - Basic 1033 Developer Edition
10.0.1600.22 No
Sql Server 2008
Management Tools - Complete 1033 Developer Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Connectivity 1033 Developer Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Backwards Compatibility 1033 Developer Edition 10.0.1600.22 No
Sql Server 2008
Client Tools SDK 1033
Developer Edition 10.0.1600.22 No
Sql Server 2008
Integration Services 1033 Developer Edition
10.0.1600.22 No
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\x86\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: AddNode
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
CONFIGURATIONFILE:
FAILOVERCLUSTERGROUP:
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTANCENAME: <empty>
MEDIASOURCE: D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\
PID: *****
QUIET: False
QUIETSIMPLE: False
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\ConfigurationFile.ini
Detailed results:
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
Message:
User has cancelled.
Stack:
at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)Requested action: AddNode
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Database Engine Services
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER SQL Server Replication
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSSQL10.MSSQLSERVER Full-Text Search
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSAS10.MSSQLSERVER Analysis Services
1033 10.0.1600.22
No
Sql Server 2008 MSSQLSERVER MSRS10.MSSQLSERVER Reporting Services
1033 10.0.1600.22
No
Sql Server 2008
Management Tools - Basic 1033 Developer Edition
10.0.1600.22 No
Sql Server 2008
Management Tools - Complete 1033 Developer Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Connectivity 1033 Developer Edition 10.0.1600.22
No
Sql Server 2008
Client Tools Backwards Compatibility 1033 Developer Edition 10.0.1600.22 No
Sql Server 2008
Client Tools SDK 1033
Developer Edition 10.0.1600.22 No
Sql Server 2008
Integration Services 1033 Developer Edition
10.0.1600.22 No
Instead of installing SQL server instance you selected add node which is to be selected when SQL server installation is to be made on Node which is being added to cluster. Since your OS is not clustered I am sure you selected worng option.
Please right click on setup file and select run as administrator. Now installation window which pops up on that on left hand side select
installation and then on page that appears select 'New server standalone installation or add feature to existing installation'.
You already have SQL server 2008 installed on your machine as per feature discovery report
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles -
Error 1920 : Service failed to install. How to resolve?
My application is installing a service. while repackaging, i captured the applicaiton. Adjusted services in serviceControl\ServiceInstall table but when i m trying to install msi, it is throwing error. I have run MSI as admin as well as in SystemContext.
Please help
Regards, Firoz Ahmad (Cheeeeeerrrrssssss)Might ask them over here.
http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=vslanguages&filter=alltypes&sort=lastpostdesc
http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?category=windowsdesktopdev
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. -
Failed to install Active directory domain services
Hi,
I've installed the AD Domain Services on Windows2008R2 by following this guide http://technet.microsoft.com/en-gb/library/cc755059%28WS.10%29.aspx. After click 'Install', step 6, it showed failed to install but there is no clue why it was failed, at all.
Here is a log I copied from C:\Windows\logs\ServerManager.log
2204: 2011-01-05 12:57:54.333 [InstallationProgressPage] Loading progress page...
2204: 2011-01-05 12:57:54.411 [InstallationProgressPage] Begining Sync operation...
2204: 2011-01-05 12:57:54.458 [Sync]
Sync Graph of changed nodes
==========
name : Active Directory Domain Services
state : Changed
rank : 1
sync tech: CBS
guest[1] : Active Directory Domain Controller
guest[2] : Identity Management for UNIX
ant. : empty
pred. : empty
provider : null
name : Active Directory Domain Controller
state : Changed
rank : 4
sync tech: CBS
ant. : .NET Framework 3.5.1
pred. : Active Directory Domain Services, .NET Framework 3.5.1
provider : Provider
2204: 2011-01-05 12:57:54.458 [Sync] Calling sync provider of Active Directory Domain Controller ...
2204: 2011-01-05 12:57:54.473 [Provider] Sync:: guest: 'Active Directory Domain Controller', guest deleted?: False
2204: 2011-01-05 12:57:54.473 [Provider] Begin installation of 'Active Directory Domain Controller'...
2204: 2011-01-05 12:57:54.473 [Provider] Install: Guest: 'Active Directory Domain Controller', updateElement: 'DirectoryServices-DomainController'
2204: 2011-01-05 12:57:54.473 [Provider] Installation queued for 'Active Directory Domain Controller'.
2204: 2011-01-05 12:57:54.473 [CBS] installing 'DirectoryServices-DomainController ' ...
2204: 2011-01-05 12:57:55.020 [CBS] ...parents that will be auto-installed: 'NetFx3 '
2204: 2011-01-05 12:57:55.020 [CBS] ...default children to turn-off: '<none>'
2204: 2011-01-05 12:57:55.036 [CBS] ...current state of 'DirectoryServices-DomainController': p: Staged, a: Staged, s: UninstallRequested
2204: 2011-01-05 12:57:55.036 [CBS] ...setting state of 'DirectoryServices-DomainController' to 'InstallRequested'
2204: 2011-01-05 12:57:55.051 [CBS] ...current state of 'NetFx3': p: Installed, a: Installed, s: InstallRequested
2204: 2011-01-05 12:57:55.051 [CBS] ...skipping 'NetFx3' because it is already in the desired state.
2204: 2011-01-05 12:57:55.098 [CBS] ...'DirectoryServices-DomainController' : applicability: Applicable
2204: 2011-01-05 12:57:55.114 [CBS] ...'NetFx3' : applicability: Applicable
2204: 2011-01-05 12:57:55.770 [CbsUIHandler] Initiate:
2204: 2011-01-05 12:57:55.770 [InstallationProgressPage] Installing...
2204: 2011-01-05 12:58:49.176 [CbsUIHandler] Error: -2147021879 :
2204: 2011-01-05 12:58:49.176 [CbsUIHandler] Terminate:
2204: 2011-01-05 12:58:49.254 [InstallationProgressPage] Verifying installation...
2204: 2011-01-05 12:58:49.270 [CBS] ...done installing 'DirectoryServices-DomainController '. Status: -2147021879 (80070bc9)
2204: 2011-01-05 12:58:49.270 [Provider] Skipped configuration of 'Active Directory Domain Controller' because install operation failed.
2204: 2011-01-05 12:58:49.270 [Provider]
[STAT] ---- CBS Session Consolidation -----
[STAT] For
'Active Directory Domain Controller'[STAT] installation(s) took '54.7870005' second(s) total.
[STAT] Configuration(s) took '0.0003053' second(s) total.
[STAT] Total time: '54.7873058' second(s).
2204: 2011-01-05 12:58:49.270 [Provider] Error (Id=0) Sync Result - Success: False, RebootRequired: True, Id: 110
2204: 2011-01-05 12:58:49.286 [Provider] Error (Id=0) Sync Message - OperationKind: Install, MessageType: Error, MessageCode: -2147021879, Message: <null>, AdditionalMessage: The requested operation failed. A system reboot is required to roll back changes
made
2204: 2011-01-05 12:58:49.286 [InstallationProgressPage] Sync operation completed
2204: 2011-01-05 12:58:49.286 [InstallationProgressPage] Performing post install/uninstall discovery...
2204: 2011-01-05 12:58:49.286 [Provider] C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
2204: 2011-01-05 12:58:49.286 [CBS] IsCacheStillGood: False.
2204: 2011-01-05 12:58:49.786 [CBS] >>>GetUpdateInfo--------------------------------------------------
2204: 2011-01-05 12:59:46.520 [CBS] Error (Id=0) Function: 'ReadUpdateInfo()->Update_GetInstallState' failed: 80070bc9 (-2147021879)
2204: 2011-01-05 12:59:46.520 [CBS] <<<GetUpdateInfo--------------------------------------------------
2204: 2011-01-05 12:59:46.598 [DISCOVERY] hr: -2147021879 -> reboot required.
2204: 2011-01-05 12:59:46.739 [InstallationProgressPage] About to load finish page...
2204: 2011-01-05 12:59:46.739 [InstallationFinishPage] Loading finish page
2204: 2011-01-05 12:59:46.801 [InstallationFinishPage] Finish page loaded
I also checked the event viewer, here are the event properties occurred during the installation:
Initiating changes to turn on update DirectoryServices-DomainController of package DirectoryServices-DomainController-Package. Client id: RMT
Update Directoryservices-DomainController of package DirectoryServices-DomainController-Package failed to be turned on. Status: 0x80070bc9
Installation failed. A restart is required.
Roles:
Active Directory Domain Services
Error: The server needs to be restarted to undo the changes
Please help.
Thanks,
balrogzAnother thing to check is to ensure the server service is up and running.
http://blogs.dirteam.com/blogs/paulbergson/archive/2014/04/29/can-t-add-the-role-quot-active-directory-domain-services-quot-to-my-2008-r2-server.aspx
Paul Bergson
MVP - Directory Services
MCITP: Enterprise Administrator
MCTS, MCT, MCSE, MCSA, Security, BS CSci
2012, 2008, Vista, 2003, 2000 (Early Achiever), NT4
Twitter @pbbergs http://blogs.dirteam.com/blogs/paulbergson
Please no e-mails, any questions should be posted in the NewsGroup.
This posting is provided AS IS with no warranties, and confers no rights. -
I am unable to instal itunes (greater than version 7) as it gives me the error,"Bonjour service failed to start, verify you have sufficient privileges" , i have checked on apple support and the only help for this error says that mcafee antivirus is blocking the services however i have never had mcafee installed on my pc. Anyone any other ideas as to what could be wrong?
Hi doywks,
The Apple Mobile Device is a component of iTunes that communicates between your computer and your iPhone or iOS device. The error message you are seeing "verify that you have sufficient privileges to start system services" has to do with the Windows operating system. It's possible that you are not logged in as the administrator for your Windows PC. Or, you may have antivirus software stopping the Apple Mobile Device from running.
If you are having issues updating iTunes on your PC, follow the steps in the article below.
If you can't install or update iTunes for Windows - Apple Support
https://support.apple.com/en-us/HT201668
How to restart the Apple Mobile Device Service (AMDS) on Windows - Apple Support
https://support.apple.com/en-us/HT203188
I hope this information helps ....
- Judy -
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 -
KB2977326 - Security Update for SQL Server Service Pack 1 repeatedly fails to install
This update fails to install every day when I shut down my computer. Here is the WindowsUpdate.Log:
2014-12-02 15:50:11:469
420 44c
AU #########
2014-12-02 15:50:11:469
420 44c
AU # Initiating install at shutdown
2014-12-02 15:50:11:469
420 44c
AU # Approved updates = 1
2014-12-02 15:50:11:516
420 44c
AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {685C12BB-7AA9-4A31-9620-8F306EEE31C3}]
2014-12-02 15:50:11:516
420 44c
Shutdwn InstallAtShutdown starts.
2014-12-02 15:50:11:516
420 1528
Agent *************
2014-12-02 15:50:11:516
420 1528
Agent ** START ** Agent: Installing updates [CallerId = AutomaticUpdates]
2014-12-02 15:50:11:516
420 1528
Agent *********
2014-12-02 15:50:11:516
420 1528
Agent * Updates to install = 1
2014-12-02 15:50:11:531
420 1528
Agent * Title = Security Update for SQL Server 2012 Service Pack 1 (KB2977326)
2014-12-02 15:50:11:531
420 1528
Agent * UpdateId = {E0D65CC4-3B13-4352-BD89-A28C5F4C5017}.200
2014-12-02 15:50:11:531
420 1528
Agent * Bundles 1 updates:
2014-12-02 15:50:11:531
420 1528
Agent * {C076E757-1A4F-44DB-823B-CFFC07CD7D38}.200
2014-12-02 15:50:11:547
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:50:12:327
420 d4c
Report CWERReporter finishing event handling. (00000000)
2014-12-02 15:50:20:548
420 44c
AU WARNING: Pending directive, 'Install Approval', is not applicable
2014-12-02 15:50:24:417
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:50:24:432
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:50:24:432
420 1528
DnldMgr Preparing update for install, updateId = {C076E757-1A4F-44DB-823B-CFFC07CD7D38}.200.
2014-12-02 15:50:25:119
2052 608
Misc =========== Logging initialized (build: 7.6.7600.320, tz: -0600) ===========
2014-12-02 15:50:25:119
2052 608
Misc = Process: C:\Windows\system32\wuauclt.exe
2014-12-02 15:50:25:119
2052 608
Misc = Module: C:\Windows\system32\wuaueng.dll
2014-12-02 15:50:25:119
2052 608
Handler :::::::::::::
2014-12-02 15:50:25:119
2052 608
Handler :: START :: Handler: Command Line Install
2014-12-02 15:50:25:119
2052 608
Handler :::::::::
2014-12-02 15:50:25:119
2052 608
Handler : Updates to install = 1
2014-12-02 15:50:25:119
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:52:23:991
420 44c
AU AU setting next sqm report timeout to 2014-12-03 21:52:23
2014-12-02 15:54:39:587
2052 608
Handler : WARNING: Command line install completed. Return code = 0x84b20001, Result = Failed, Reboot required = false
2014-12-02 15:54:39:587
2052 608
Handler : WARNING: Exit code = 0x8024200B
2014-12-02 15:54:39:587
420 16d8
AU >>## RESUMED ## AU: Installing update [UpdateId = {E0D65CC4-3B13-4352-BD89-A28C5F4C5017}]
2014-12-02 15:54:39:587
2052 608
Handler :::::::::
2014-12-02 15:54:39:587
2052 608
Handler :: END :: Handler: Command Line Install
2014-12-02 15:54:39:587
2052 608
Handler :::::::::::::
2014-12-02 15:54:39:587
420 16d8
AU # WARNING: Install failed, error = 0x80070643 / 0x84B20001
2014-12-02 15:54:39:587
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:54:39:711
420 1528
Report REPORT EVENT: {DFA9CDC8-334A-4E57-9588-77B8E980833D}
2014-12-02 15:54:39:587-0600 1
198 101
{E0D65CC4-3B13-4352-BD89-A28C5F4C5017}
200 80070643
AutomaticUpdates Failure
Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for SQL Server 2012 Service Pack 1 (KB2977326).
2014-12-02 15:54:39:727
420 1528
Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2014-12-02 15:54:39:727
420 1528
Report WER Report sent: 7.6.7600.320 0x80070643 E0D65CC4-3B13-4352-BD89-A28C5F4C5017 Install 101 Unmanaged
2014-12-02 15:54:39:727
420 1528
Report CWERReporter finishing event handling. (00000000)
2014-12-02 15:54:39:805
420 1528
Agent *********
2014-12-02 15:54:39:805
420 16d8
AU Install call completed.
2014-12-02 15:54:39:805
420 1528
Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
2014-12-02 15:54:39:805
420 16d8
AU # WARNING: Install call completed, reboot required = No, error = 0x00000000
2014-12-02 15:54:39:805
420 1528
Agent *************
2014-12-02 15:54:39:805
420 16d8
AU #########
2014-12-02 15:54:39:805
420 16d8
AU ## END ## AU: Installing updates [CallId = {685C12BB-7AA9-4A31-9620-8F306EEE31C3}]
2014-12-02 15:54:39:805
420 16d8
AU #############
jim...Hello,
Please examine the Summary.txt log file. The following article may help you locate the file on disk:
http://msdn.microsoft.com/en-us/library/ms143702(v=sql.110).aspx
If you find the sentence “A failure was detected for a previous installation” on the Summary.txt log file, please repair SQL Server using the following article:
http://msdn.microsoft.com/en-us/library/Cc646006(v=sql.110).aspx
If you find other errors, please share the content of the Summary.txt log file with us.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Error while Installation: Windows Setup failed to install (...) while offline servicing the image
Hello,
I'm facing some issues while installing an image from configuration file of Windows Embedded 8 Standard. I get an error message which I've tried to indentify using this guide
Use Log Files to Diagnose Image Builder Wizard Installation Problems (Standard 8). I haven't succeeded at all. The errors I have are the following:
At setuperr.log
2015-03-13 11:43:00, Error CBS Failed to process single phase execution. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-03-13 11:43:00, Error CBS Failed to perform operation. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-03-13 11:43:18, Error [0x060766] IBS ApplyUnattendFileUsingDism: DISM returned error exit code 2
2015-03-13 11:43:18, Error [0x06076d] IBS ApplyUnattendFileUsingDism: See DISM log file [D:\$WINDOWS.~BT\Sources\Panther\cbs_unattend.log] for more details.
2015-03-13 11:43:18, Error [0x060768] IBS ApplyUnattendFileUsingDism: Failed to use DISM to install modules and apply settings. Error code = 0x80070002
At cbs_unattend.log
2015-03-13 11:41:50, Info DISM Embedded Manager: PID=460 TID=544 Success coping module from "C:\AutoUnattend_Files\offlineServicing\vvvv_45beta33.7~0000000000000000~amd64~~1.0.0.0.emd" to "D:\Windows\servicing\Modules\PendingInstall\vvvv_45beta33.7~0000000000000000~amd64~~1.0.0.0.emd" - ModuleInstaller::CopyForPostboot
2015-03-13 11:41:50, Info DISM DISM Package Manager: PID=460 TID=544 CBS session options=0x0! - CDISMPackageManager::Internal_Finalize
2015-03-13 11:42:01, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:01, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:01, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:01, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:15, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:58, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:43:00, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: (null) (CBS HRESULT=0x80070002) - CCbsConUIHandler::Error
2015-03-13 11:43:00, Error DISM DISM Package Manager: PID=460 TID=544 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM Package Manager: PID=460 TID=544 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80070002)
2015-03-13 11:43:02, Error DISM Embedded Manager: PID=460 TID=544 Failed to process package installation(s) - ModuleInstaller::InstallModules(hr:0x80070002)
2015-03-13 11:43:02, Error DISM Embedded Manager: PID=460 TID=544 Failed to install modules - CEmbeddedManager::Apply(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM Unattend Manager: PID=460 TID=544 Error applying unattend for provider: Embedded Manager - CUnattendManager::Apply(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM Unattend Manager: PID=460 TID=544 base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:674 - CUnattendManager::InternalExecuteCmdLine(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM Unattend Manager: PID=460 TID=544 base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:623 - CUnattendManager::ExecuteCmdLine(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=80070002
2015-03-13 11:43:02, Info DISM DISM Provider Store: PID=460 TID=544 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
I've googled for them and I've read that the 0x80070002 may be related to updates, but nothing particular about the other.
Could anyone please tell me what can be happening?
I've uploaded cbs_unattend.log and setupact.log in case they are helpful.
http://www.filedropper.com/cbsunattend
http://www.filedropper.com/setupactIt's strange, because I can install that package, and all the other custom ones without error if updates, security updates and hotfixes are not included. It must be one of those packages which is causing the install to fail. I tried to install updates manually
once I deployed the image but after the updates some of my custom applications didn't work well.
All of this just happening on the intel board, not the amd one. -
Adobe Anchor Service CS3 fails to install
Trying to install Photoshop CS3, it always fails due to a component installation failure:
Adobe Anchor Service CS3
Skipping operation because required operation failed with code: 2
Followed a lot of forum suggestion, CS3Clean, uninstall this and that, the problem persists.
Both GUI and silent install have the same problem.
Tried installing AdobeALMAnchorServiceAll directly with
msiexec /i AdobeALMAnchorServiceAll.msi ADOBE_SETUP=1 UPGRADINGPRODUCTCODE=1 /qbDionysus_82 please see Error "Failed to Install" Creative Cloud Desktop application - http://helpx.adobe.com/creative-cloud/kb/failed-install-creative-cloud-desktop.html for information on how to resolve your current error.
-
I ran SQL Server 2012 express setup as user with administrator privileges and still it's failing to install "Database Engine Service" and "SQL Server Replication".
Any and every ideas on how to resolve this issue is greatly appreciated.Three weeks passed and I am yet to find a fix for the the failed installation of the database engine on sql server 2012 express installation. I have tried various work-around including uninstalling, deleting all the directory paths, and reinstallation. Still
not able to successfully install sql server 2012 express.
I will greatly appreciate any and every contribution towards resolving this issue. Thanks in advance.
Here is the content of log file after the latest failed installation:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2013-12-23 14:42:45
End time: 2013-12-23 15:07:51
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: mymachine1
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2012 SQLEXPRESS_GT MSSQL11.SQLEXPRESS_GT Database Engine Services
1033 Express Edition 11.0.2100.60 No
SQL Server 2012 SQLEXPRESS_GT MSSQL11.SQLEXPRESS_GT SQL Server Replication
1033 Express Edition 11.0.2100.60 No
SQL Server 2012
Management Tools - Basic 1033 Express Edition
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9b6607e524727c7fe1defd80\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Product Update Status:
Success: KB 2674319
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, CONN, BC, SDK, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: c:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: <empty>
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Manual
SQLSYSADMINACCOUNTS: MH\gt038676t
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131223_144132\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
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, 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: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025
Feature: SQL Server Replication
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, 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: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131223_144132\SystemConfigurationCheck_Report.htm -
Since a few weeks all my iTunes Updates fail to install. After the installation trial, the previous installation is damaged – a service is missing :
To fix this I have to deinstall all components of Apple Software in exact order as you reveal on your web site. Than reinstall iTunes from Scratch.
I am using Windos 7 64 bit Professional German edition.Hi,
to see the cause of Windows 8 update failures, we must look for error messages in the following log files:
Please run the Windows Explorer and go to the folder "C:\Windows\Logs\CBS\" and copy all files to your document folder, also copy the setupapi.dev.log from the folder C:\Windows\Inf, the "C:\Windows\WindowsUpdate.log" and the file "C:\Windows\winsxs\poqexec.log"
to your document folder (otherwise you can't upload it), zip all files into 1 ZIP and upload the zip to your SkyDrive [1] and post a link here.
André
[1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
"A programmer is just a tool which converts caffeine into code" -
im on firefox 4 ,recently ,i tried new addon for firefox 4 called start up faster, i removed it, just as comparison to see boot up times , and then when i tried to install again i get the message create service failed, the icon stays on my desktop, want to check this addon is still performing its role, or could i fix something to make sure its properly on my addon list, thank you,
Is it still showing up in your ad-on manager?
-
Hi, I'm trying to re-install the latest iTunes on my Gateway w/ Windows XP. I had to update it a while back to put songs on my brother's iPod, but my computer froze halfway through and nothing has worked right since.
I keep getting the message "Service 'Bonjour Service' (Bonjour Service) failed to start. Verify that you have sufficient privileges to start system services."
I looked through older discussions that told me to go to right click My Computer - Manage - Services and Applications - Services - Find Bonjour and restart it.
Well, the only option that I can click on is Start. When I do, it says "Windows could not restart the Bonjour Service service on Local Computer. Error 2: The system cannot find the file specified."
Where do I go from here? Help would be greatly appreciated, I've been trying to fix this for over a year now with no dice. Also, I cannot do a factory reset (last effort) because it says the administor's account is disabled and I do not have the disc.Sorry if double posting is a no-no here, but I forgot to add that I've already tried disabling Spyware Doctor.
-
Service for network file system fails to install
Installation of the File Service and Service for NFS in Windows 2008 R2 server fails. Following are the steps used to perform the install.
Open Server Manager from Start> All Programs> Administrative Tools> Server Manager.
Click on the Roles node in the left pane, and then click the
Add Roles link.
On the Add Roles Wizard welcome page, click Next to continue.
From the list of roles to install, select File Services, and click
Next to continue.
On the Introduction to File Services page, click Next to continue.
On the Select Role Services page, keep the File Server box checked and select
Services for Network File System. Click Next to continue.
On the Confirmation page, review the settings and click the Install button.
Click Close when the wizard completes.
ServerManager Log:
From the ServerManager.log file under C:/Windows/Logs I can see the below.
2272: 2013-02-12 16:13:51.479 [CBS] IsCacheStillGood: True.
2272: 2013-02-12 16:14:05.534 [Provider] System changed since last refresh: False
2272: 2013-02-12 16:15:45.816 [InstallationProgressPage] Loading progress page...
2272: 2013-02-12 16:15:45.831 [InstallationProgressPage] Begining Sync operation...
2272: 2013-02-12 16:15:45.842 [Sync]
Sync Graph of changed nodes
==========
name : File Services
state : Changed
rank : 1
sync tech: CBS
guest[1] : File Server
guest[2] : Distributed File System
guest[3] : File Server Resource Manager
guest[4] : Services for Network File System
guest[5] : Single Instance Storage
guest[6] : Windows Search Service
guest[7] : Windows Server 2003 File Services
guest[8] : BranchCache for network files
provider : FileServerRoleProvider
name : Services for Network File System
state : Changed
rank : 2
sync tech: CBS
provider : FileServerRoleProvider
name : File Server
state : Changed
rank : 2
sync tech: CBS
provider : FileServerRoleProvider
2272: 2013-02-12 16:15:45.842 [Sync] Calling sync provider of Services for Network File System ...
2272: 2013-02-12 16:15:45.843 [FileServer] Sync:: guest: 'Services for Network File System', guest deleted?: False
2272: 2013-02-12 16:15:45.843 [FileServer] Begin installation of 'Services for Network File System'...
2272: 2013-02-12 16:15:45.843 [FileServer] Install: Guest: 'Services for Network File System', updateElement: 'ServicesForNFS-ServerAndClient;ClientForNFS-Infrastructure;NFS-Administration;ServerForNFS-Infrastructure'
2272: 2013-02-12 16:15:45.843 [FileServer] Installation queued for 'Services for Network File System'.
2272: 2013-02-12 16:15:45.843 [Sync] Calling sync provider of File Server ...
2272: 2013-02-12 16:15:45.843 [FileServer] Sync:: guest: 'File Server', guest deleted?: False
2272: 2013-02-12 16:15:45.843 [FileServer] Begin installation of 'File Server'...
2272: 2013-02-12 16:15:45.843 [FileServer] Install: Guest: 'File Server', updateElement: 'CoreFileServer'
2272: 2013-02-12 16:15:45.843 [FileServer] Installation queued for 'File Server'.
2272: 2013-02-12 16:15:45.844 [CBS] installing 'ServicesForNFS-ServerAndClient ClientForNFS-Infrastructure
NFS-Administration ServerForNFS-Infrastructure CoreFileServer ' ...
2272: 2013-02-12 16:15:46.315 [CBS] ...parents that will be auto-installed: '<none>'
2272: 2013-02-12 16:15:46.316 [CBS] ...default children to turn-off: '<none>'
2272: 2013-02-12 16:15:46.325 [CBS] ...current state of 'ServicesForNFS-ServerAndClient': p:
Staged, a: Staged, s: UninstallRequested
2272: 2013-02-12 16:15:46.325 [CBS] ...setting state of 'ServicesForNFS-ServerAndClient' to
'InstallRequested'
2272: 2013-02-12 16:15:46.335 [CBS] ...current state of 'ClientForNFS-Infrastructure': p: Staged,
a: Staged, s: UninstallRequested
2272: 2013-02-12 16:15:46.336 [CBS] ...setting state of 'ClientForNFS-Infrastructure' to 'InstallRequested'
2272: 2013-02-12 16:15:46.345 [CBS] ...current state of 'NFS-Administration': p: Staged, a:
Staged, s: UninstallRequested
2272: 2013-02-12 16:15:46.345 [CBS] ...setting state of 'NFS-Administration' to 'InstallRequested'
2272: 2013-02-12 16:15:46.354 [CBS] ...current state of 'ServerForNFS-Infrastructure': p: Staged,
a: Staged, s: UninstallRequested
2272: 2013-02-12 16:15:46.354 [CBS] ...setting state of 'ServerForNFS-Infrastructure' to 'InstallRequested'
2272: 2013-02-12 16:15:46.363 [CBS] ...current state of 'CoreFileServer': p: Staged, a: Staged,
s: UninstallRequested
2272: 2013-02-12 16:15:46.363 [CBS] ...setting state of 'CoreFileServer' to 'InstallRequested'
2272: 2013-02-12 16:15:46.373 [CBS] ...'ServicesForNFS-ServerAndClient' : applicability: Applicable
2272: 2013-02-12 16:15:46.390 [CBS] ...'ClientForNFS-Infrastructure' : applicability: Applicable
2272: 2013-02-12 16:15:46.408 [CBS] ...'NFS-Administration' : applicability: Applicable
2272: 2013-02-12 16:15:46.426 [CBS] ...'ServerForNFS-Infrastructure' : applicability: Applicable
2272: 2013-02-12 16:15:46.435 [CBS] ...'CoreFileServer' : applicability: Applicable
2272: 2013-02-12 16:15:46.493 [CbsUIHandler] Initiate:
2272: 2013-02-12 16:15:46.494 [InstallationProgressPage] Installing...
2272: 2013-02-12 16:15:51.958 [CbsUIHandler] Error: -2147021879 :
2272: 2013-02-12 16:15:51.958 [CbsUIHandler] Terminate:
2272: 2013-02-12 16:15:52.035 [InstallationProgressPage] Verifying installation...
2272: 2013-02-12 16:15:52.049 [CBS] ...done installing 'ServicesForNFS-ServerAndClient
ClientForNFS-Infrastructure NFS-Administration ServerForNFS-Infrastructure CoreFileServer '.
Status: -2147021879 (80070bc9)
2272: 2013-02-12 16:15:52.052 [FileServer] Skipped configuration of 'Services for Network File System' because install operation failed.
2272: 2013-02-12 16:15:52.053 [FileServer] Skipped configuration of 'File Server' because install operation failed.
2272: 2013-02-12 16:15:52.053 [Provider]
[STAT] ---- CBS Session Consolidation -----
[STAT] For
'Services for Network File System',
'File Server'[STAT] installation(s) took '6.2058637' second(s) total.
[STAT] Configuration(s) took '0.0002143' second(s) total.
[STAT] Total time: '6.206078' second(s).
2272: 2013-02-12 16:15:52.053 [Provider] Error (Id=0) Sync Result - Success: False, RebootRequired: True, Id: 105
2272: 2013-02-12 16:15:52.053 [Provider] Error (Id=0) Sync Message - OperationKind: Install, MessageType: Error, MessageCode: -2147021879, Message: <null>, AdditionalMessage: The requested operation failed. A system reboot
is required to roll back changes made
2272: 2013-02-12 16:15:52.053 [Provider] Error (Id=0) Sync Result - Success: False, RebootRequired: True, Id: 255
2272: 2013-02-12 16:15:52.053 [Provider] Error (Id=0) Sync Message - OperationKind: Install, MessageType: Error, MessageCode: -2147021879, Message: <null>, AdditionalMessage: The requested operation failed. A system reboot
is required to roll back changes made
2272: 2013-02-12 16:15:52.054 [InstallationProgressPage] Sync operation completed
2272: 2013-02-12 16:15:52.054 [InstallationProgressPage] Performing post install/uninstall discovery...
2272: 2013-02-12 16:15:52.056 [Provider] C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
2272: 2013-02-12 16:15:52.056 [CBS] IsCacheStillGood: False.
2272: 2013-02-12 16:15:52.526 [CBS] >>>GetUpdateInfo--------------------------------------------------
2272: 2013-02-12 16:15:59.342 [CBS] Error (Id=0) Function: 'ReadUpdateInfo()->Update_GetInstallState' failed:
80070bc9 (-2147021879)
2272: 2013-02-12 16:15:59.342 [CBS] <<<GetUpdateInfo--------------------------------------------------
2272: 2013-02-12 16:15:59.380 [DISCOVERY] hr: -2147021879 -> reboot required.
2272: 2013-02-12 16:15:59.390 [InstallationProgressPage] About to load finish page...
2272: 2013-02-12 16:15:59.390 [InstallationFinishPage] Loading finish page
2272: 2013-02-12 16:15:59.401 [InstallationFinishPage] Finish page loaded
In Windows Event long I can see the following events logged:
Event 3002, Port Map:
Windows(R) failed a request to register RPC Port Mapper on TCP port 111. RPC Port Mapper cannot start.
Network File System (NFS) clients use RPC Port Mapper (also known as Portmap and Rpcbind) to discover NFS protocols on remote servers. Without RPC Port Mapper, Server for NFS
cannot start and NFS clients cannot access files on this server.
Verify that no other software is registered on TCP port 111, then start Server for NFS manually (which will also start RPC Port Mapper).
Event 7000, Service Control Manager:
The Server for NFS Open RPC (ONCRPC) Portmapper service failed to start due to the following error:
A device attached to the system is not functioning.
Event 7001, Service Control Manager:
The Server for NFS Driver service depends on the Server for NFS Open RPC (ONCRPC) Portmapper service which failed to start because of the following error:
A device attached to the system is not functioning.
Event 7001, Service Control Manager:
The Server for NFS service depends on the Server for NFS Driver service which failed to start because of the following error:
The dependency service or group failed to start.
Based on a technet forum I have already checked and made sure there is no other service running on port 111 (command used is netstat -a -b -o).
Dependent Service Status:
During the installation process “Client for NFS” seems to have gone well and the service started successfully. But the “Server for NFS” failed, when checked for the status of the dependent process “portmap” service failed to start with the WIN32_EXIT_CODE
“31 (0x1f)”. Please find below the query result.
C:\Users\CMMAdmin>sc query rpcxdr
SERVICE_NAME: rpcxdr
TYPE : 1 KERNEL_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\Users\CMMAdmin>sc query msnfsflt
SERVICE_NAME: msnfsflt
TYPE : 2 FILE_SYSTEM_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\Users\CMMAdmin>sc query portmap
SERVICE_NAME: portmap
TYPE : 1 KERNEL_DRIVER
STATE : 1 STOPPED
WIN32_EXIT_CODE : 31 (0x1f)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\Users\CMMAdmin>
As the EXIT CODE is 31 ( A device attached to the system is not functioning), I have checked device manager and made sure there is no yellow warning shown against any hardware device. Further I am not sure how to proceed and debug this issue.
Please let me know if you have any suggestion on how debug this issue further.
Thanks
-PoopeshHey,
I had this same problem running MS Server 2008 R2 and server log is as follow:
name : Services for Network File System
state : Changed
rank : 2
sync tech: CBS
ant. : empty
pred. : File Services
provider : FileServerRoleProvider
5676: 2014-01-14 14:08:57.474 [Sync] Calling sync provider of Services for Network File System ...
5676: 2014-01-14 14:08:57.521 [FileServer] Sync:: guest: 'Services for Network File System', guest deleted?: False
5676: 2014-01-14 14:08:57.536 [FileServer] Begin installation of 'Services for Network File System'...
5676: 2014-01-14 14:08:57.536 [FileServer] Install: Guest: 'Services for Network File System', updateElement: 'ServicesForNFS-ServerAndClient;ClientForNFS-Infrastructure;NFS-Administration;ServerForNFS-Infrastructure'
5676: 2014-01-14 14:08:57.536 [FileServer] Installation queued for 'Services for Network File System'.
5676: 2014-01-14 14:08:57.536 [CBS] installing 'ServicesForNFS-ServerAndClient ClientForNFS-Infrastructure NFS-Administration
ServerForNFS-Infrastructure ' ...
5676: 2014-01-14 14:09:00.173 [CBS] ...parents that will be auto-installed: '<none>'
5676: 2014-01-14 14:09:00.173 [CBS] ...default children to turn-off: '<none>'
5676: 2014-01-14 14:09:00.204 [CBS] ...current state of 'ServicesForNFS-ServerAndClient': p: Staged, a: Staged, s: UninstallRequested
5676: 2014-01-14 14:09:00.204 [CBS] ...setting state of 'ServicesForNFS-ServerAndClient' to 'InstallRequested'
5676: 2014-01-14 14:09:00.235 [CBS] ...current state of 'ClientForNFS-Infrastructure': p: Staged, a: Staged, s: UninstallRequested
5676: 2014-01-14 14:09:00.235 [CBS] ...setting state of 'ClientForNFS-Infrastructure' to 'InstallRequested'
5676: 2014-01-14 14:09:00.266 [CBS] ...current state of 'NFS-Administration': p: Staged, a: Staged, s: UninstallRequested
5676: 2014-01-14 14:09:00.266 [CBS] ...setting state of 'NFS-Administration' to 'InstallRequested'
5676: 2014-01-14 14:09:00.282 [CBS] ...current state of 'ServerForNFS-Infrastructure': p: Staged, a: Staged, s: UninstallRequested
5676: 2014-01-14 14:09:00.282 [CBS] ...setting state of 'ServerForNFS-Infrastructure' to 'InstallRequested'
5676: 2014-01-14 14:09:00.313 [CBS] ...'ServicesForNFS-ServerAndClient' : applicability: Applicable
5676: 2014-01-14 14:09:00.360 [CBS] ...'ClientForNFS-Infrastructure' : applicability: Applicable
5676: 2014-01-14 14:09:00.422 [CBS] ...'NFS-Administration' : applicability: Applicable
5676: 2014-01-14 14:09:00.469 [CBS] ...'ServerForNFS-Infrastructure' : applicability: Applicable
5676: 2014-01-14 14:09:01.624 [CbsUIHandler] Initiate:
5676: 2014-01-14 14:09:01.624 [InstallationProgressPage] Installing...
5676: 2014-01-14 14:09:35.117 [CbsUIHandler] Error: -2147021879 :
5676: 2014-01-14 14:09:35.117 [CbsUIHandler] Terminate:
5676: 2014-01-14 14:09:41.170 [InstallationProgressPage] Verifying installation...
5676: 2014-01-14 14:09:41.264 [CBS] ...done installing 'ServicesForNFS-ServerAndClient ClientForNFS-Infrastructure NFS-Administration
ServerForNFS-Infrastructure '. Status: -2147021879 (80070bc9)
5676: 2014-01-14 14:09:41.279 [FileServer] Skipped configuration of 'Services for Network File System' because install operation failed.
5676: 2014-01-14 14:09:41.279 [Provider]
[STAT] ---- CBS Session Consolidation -----
[STAT] For
'Services for Network File System'[STAT] installation(s) took '43.7368586' second(s) total.
[STAT] Configuration(s) took '0.0062843' second(s) total.
[STAT] Total time: '43.7431429' second(s).
5676: 2014-01-14 14:09:41.279 [Provider] Error (Id=0) Sync Result - Success: False, RebootRequired: True, Id: 105
5676: 2014-01-14 14:09:41.279 [Provider] Error (Id=0) Sync Message - OperationKind: Install, MessageType: Error, MessageCode: -2147021879, Message: <null>, AdditionalMessage: The requested operation failed. A system reboot is required to roll back changes
made
5676: 2014-01-14 14:09:41.279 [InstallationProgressPage] Sync operation completed
5676: 2014-01-14 14:09:41.279 [InstallationProgressPage] Performing post install/uninstall discovery...
5676: 2014-01-14 14:09:41.295 [Provider] C:\windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
5676: 2014-01-14 14:09:41.295 [CBS] IsCacheStillGood: False.
5676: 2014-01-14 14:09:43.900 [CBS] >>>GetUpdateInfo--------------------------------------------------
5676: 2014-01-14 14:09:57.394 [CBS] Error (Id=0) Function: 'ReadUpdateInfo()->Update_GetInstallState' failed: 80070bc9 (-2147021879)
5676: 2014-01-14 14:09:57.410 [CBS] <<<GetUpdateInfo--------------------------------------------------
5676: 2014-01-14 14:09:57.488 [DISCOVERY] hr: -2147021879 -> reboot required.
5676: 2014-01-14 14:09:57.613 [InstallationProgressPage] About to load finish page...
5676: 2014-01-14 14:09:57.628 [InstallationFinishPage] Loading finish page
5676: 2014-01-14 14:09:57.644 [InstallationFinishPage] Finish page loaded
My solution was to run netstat -ano to identify what process was running on port TCP/UDP :111, then with the command tasklist I got PID matching with the task name. Once identified I stopped the process, rebooted and installed
the NFS service. On top of that, before installing NFS services I disabled firewall and antivirus. It worked fine for me. I hope this will be usefull for you. By the way, don't forget to enable all process back!
Have a good one!
Maybe you are looking for
-
AMD 64 X2 3800+ and K8N Diamond
Hi, has anybody tried this combination of CPU and MB? On the CPU Support Page of this MB is written, that this CPU is still under testing, but I would like to buy this combination in a short time...does it work fine (with latest BIOS, of course) or i
-
How would I get the Oracle XML Parser to parse an XML string? The example ("DOMSample") only demonstrates how to parse an XML file -- I would like to do something of the form... parser.parse("<test>testing</test>"); On a related note, whilst the PL/S
-
Can I re download an audiobook I purchased?
I have purchased an audiobook from iTunes on an iPad, but it wouldn't sync with my computer. Also there isn't a way to redownload it into iTunes.how can this be done?
-
Problems with Action menu in 3.1.2.00.02
Hi, I wonder if any one has encountered a similar problem am having with the action menu of Interactive reports in version 3.1.2.00.02. The action items of the action menu do not work for a conditional report. If I have the Interactive Report set to
-
I am trying to compare two PDF's and receive A message "wrong type parameter supplied to a pds procedure" one is Acrobat 5.x and the other one is 7.x