Patch-ftf-11.2.3-11.5.2013.zip
I downloaded this patch this evening. One of the jar files in the
install instructions is SCR-5.1.jar, but the jar file contained in the
zip file is SCR-5.0.jar . Is this simply a mistake in the install
instructions?
Brad Johnson
Brad,
oh - you are right... I apologise. That's entirely my fault: I created
the 11.2.3 and 11.2.4 patches at the same time, and my search and
replace missed that It's SCR-5.0.jar for 11.2.3, SCR-5.1.jar for
11.2.4.
Shaun Pond
Similar Messages
-
Sharepoint infopath 2013 mouseover not work on ipad browser
I have a SharePoint list with custom info-path forms. On these forms there are some fields which have required validation and when user mouse over on that field then a popup "Cannot be blank" shown on above the field. That is working fine but when
i open site in IPad safari browser then first time have to tapped two time , first tape show "Cannot be blank" popup and then other tape allow to enter text or open drop down. That behavior is only first time interacting with control and after that
working is right .
Any one please help that how can i change that behavior for info-path forms on IPad safari browser.
Please and i will be great thankful to youHi Umair,
Thanks for posting your issue, Kindly browse the below mentioned URL to know more about your issue and fixed on that.
http://yalla.itgroove.net/2014/03/list-issues-bugs-patched-service-pack-1-sp1-office-sharepoint-2013/
I hope this is helpful to you, mark it as Helpful.
If this works, Please mark it as Answered.
Regards,
Dharmendra Singh (MCPD-EA | MCTS)
Blog : http://sharepoint-community.net/profile/DharmendraSingh -
Exchange 2013 mail flow problem
Hello!
We have problem, could not send mails via Exchange 2013 server.
Symptoms:
-no messages in message queue
-if sending mail to this domain, the message seems sent at Sender.
-if sending mail from this domain, the messages are in the mailboxes' DRAFT folder
Here are some SMTP logs:
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,10,192.168.3.2:26408,192.168.3.2:2525,<,250-STARTTLS,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,11,192.168.3.2:26408,192.168.3.2:2525,<,250-AUTH NTLM,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,12,192.168.3.2:26408,192.168.3.2:2525,<,250-8BITMIME,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,13,192.168.3.2:26408,192.168.3.2:2525,<,250-BINARYMIME,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,14,192.168.3.2:26408,192.168.3.2:2525,<,250 CHUNKING,
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,15,192.168.3.2:26408,192.168.3.2:2525,*,,"EHLO options between current server and proxy target do not match : Xrdst, . Critical
non matching options : Xrdst, . Failing over."
2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,16,192.168.3.2:26408,192.168.3.2:2525,>,QUIT,
Software Enviroment:
-Windows Server 2012 Server Standard
-Exchange Server 2013
-fully patched system (includes the brand new Exchange 2013 CU1), the error was realized before this update.
Regards.
molniHi
Can you run ipconfig/flushdns or create hosts file recorder?
Terence Yu
TechNet Community Support -
SQL 2005 Patch installation fail
Hi all
I am having error on installing KB2716429... currently the SQL server is build no. 9.0.5057
here following is the error
11/30/2013 09:46:45.484 ================================================================================
11/30/2013 09:46:45.484 Hotfix package launched
11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:45.500 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:45.500 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:45.515 Local Computer:
11/30/2013 09:46:45.515 Target Details: SV53704
11/30/2013 09:46:45.515 commonfilesdir = C:\Program Files\Common Files
11/30/2013 09:46:45.515 lcidsupportdir = e:\6ce33de16cc8ba67b3e41388bb\1033
11/30/2013 09:46:45.515 programfilesdir = C:\Program Files
11/30/2013 09:46:45.515 programfilesdir_wow = C:\Program Files
11/30/2013 09:46:45.515 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:45.515 supportdirlocal = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:45.515 windir = C:\WINDOWS
11/30/2013 09:46:45.515 winsysdir = C:\WINDOWS\system32
11/30/2013 09:46:45.515 winsysdir_wow = C:\WINDOWS\SysWOW64
11/30/2013 09:46:45.515
11/30/2013 09:46:45.531 Enumerating applicable products for this patch
11/30/2013 09:46:45.531 Found SQL 2005 product definition
11/30/2013 09:46:45.531 Warning: Product HotFixSQL is missing LCID value
11/30/2013 09:46:46.953 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:46.969 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:46.969 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:46.969 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
11/30/2013 09:46:46.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:46.984 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:46.984 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:46.984 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:46.984 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Command-line instance name check completed during the install process
11/30/2013 09:46:46.984 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:47.000 Baseline build check completed during the install process
11/30/2013 09:46:47.000 Found OLAP Server 2005 product definition
11/30/2013 09:46:47.000 Warning: Product HotFixAS is missing LCID value
11/30/2013 09:46:48.453 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
11/30/2013 09:46:48.453 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:48.453 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
11/30/2013 09:46:48.453 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:48.469 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:48.469 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:48.469 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.469 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.469 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.484 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.484 Command-line instance name check completed during the install process
11/30/2013 09:46:48.484 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:48.484 Baseline build check completed during the install process
11/30/2013 09:46:48.484 Found Notification Services 2005 product definition
11/30/2013 09:46:48.484 Warning: Product HotFixNS is missing LCID value
11/30/2013 09:46:50.015 Enumeration: Determining QFE level for product instance
11/30/2013 09:46:50.047 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
11/30/2013 09:46:50.062 Enumeration: Found following QFE level for product instance : 5057
11/30/2013 09:46:50.062 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:50.062 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
11/30/2013 09:46:50.062 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:50.062 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:50.078 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:50.078 Product discovery completed during the install process for NS
11/30/2013 09:46:50.078 SP Level check completed during the install process for NS
11/30/2013 09:46:50.078 Product language check completed during the install process for NS
11/30/2013 09:46:50.078 Product version check completed during the install process for NS
11/30/2013 09:46:50.078 Baseline build check completed during the installation process for NS
11/30/2013 09:46:50.078 Baseline build check completed during the install process
11/30/2013 09:46:50.078 Found Report Server 2005 product definition
11/30/2013 09:46:50.109 Warning: Product HotFixRS is missing LCID value
11/30/2013 09:46:51.687 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
11/30/2013 09:46:51.703 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:51.703 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
11/30/2013 09:46:51.703 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:51.703 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:51.703 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:51.703 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.719 Command-line instance name check completed during the install process
11/30/2013 09:46:51.750 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:51.750 Baseline build check completed during the install process
11/30/2013 09:46:51.765 Found DTS 2005 product definition
11/30/2013 09:46:51.765 Warning: Product HotFixDTS is missing LCID value
11/30/2013 09:46:53.359 Enumeration: Determining QFE level for product instance
11/30/2013 09:46:53.375 Enumeration: Found following QFE level for product instance : 5057
11/30/2013 09:46:53.375 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:53.375 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:53.375 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:53.375 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:53.375 Product discovery completed during the install process for Integration Services
11/30/2013 09:46:53.375 SP Level check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Product language check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Product version check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Baseline build check completed during the installation process for Integration Services
11/30/2013 09:46:53.375 Baseline build check completed during the install process
11/30/2013 09:46:53.390 Found SQL 2005 Tools product definition
11/30/2013 09:46:53.390 Warning: Product HotFixTools is missing LCID value
11/30/2013 09:46:54.953 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:54.969 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:54.969 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:54.969 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:54.969 Product discovery completed during the install process for SQL Tools
11/30/2013 09:46:54.969 SP Level check completed during the install process for SQL Tools
11/30/2013 09:46:54.969 Product language check completed during the install process for SQL Tools
11/30/2013 09:46:54.984 Product version check completed during the install process for SQL Tools
11/30/2013 09:46:54.984 Baseline build check completed during the installation process for SQL Tools
11/30/2013 09:46:54.984 Baseline build check completed during the install process
11/30/2013 09:46:55.031 Product Enumeration Results:
11/30/2013 09:46:55.031 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL.inf
11/30/2013 09:46:55.031 arpfolder = SQL9_KB2716429_ENU
11/30/2013 09:46:55.031 associatedhotfixbuild = 5320
11/30/2013 09:46:55.031 baselinebuild = 5000
11/30/2013 09:46:55.031 baselinebuildmax = 5069
11/30/2013 09:46:55.031 build = 5069
11/30/2013 09:46:55.031 description = SQL Server Database Services 2005
11/30/2013 09:46:55.031 details = Patch for SQL Server Database Services 2005
11/30/2013 09:46:55.031 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.031 kbarticle = KB2716429
11/30/2013 09:46:55.031 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.031 legalproductname = SQL Server Database Services 2005
11/30/2013 09:46:55.031 machinetype = x86
11/30/2013 09:46:55.031 package = HotFixSQL
11/30/2013 09:46:55.031 packagetype = GDR
11/30/2013 09:46:55.031 productname = SQL9
11/30/2013 09:46:55.047 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.047 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.047 splevel = 4
11/30/2013 09:46:55.047 sqlutility = sqlcmd.exe
11/30/2013 09:46:55.047 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.047 version = 9
11/30/2013 09:46:55.047
11/30/2013 09:46:55.047 File Group Details: MSP
11/30/2013 09:46:55.047 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.047 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.047 File Details: sqlrun_sql.msp
11/30/2013 09:46:55.047
11/30/2013 09:46:55.047 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.047 agentservicename = SQLSERVERAGENT
11/30/2013 09:46:55.047 associatedhotfixbuild = 5292
11/30/2013 09:46:55.047 clustername =
11/30/2013 09:46:55.047 default = TRUE
11/30/2013 09:46:55.047 ftsservicename = MSFTESQL
11/30/2013 09:46:55.047 fullversion = 2005.090.5057.00
11/30/2013 09:46:55.047 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.1
11/30/2013 09:46:55.047 id = MSSQL.1
11/30/2013 09:46:55.062 installsqldatadir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
11/30/2013 09:46:55.062 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
11/30/2013 09:46:55.062 lcid = 1033
11/30/2013 09:46:55.062 name = MSSQLSERVER
11/30/2013 09:46:55.062 productcode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
11/30/2013 09:46:55.062 qfelevel = 5057
11/30/2013 09:46:55.062 servicename = MSSQLServer
11/30/2013 09:46:55.062 sku = STANDARD
11/30/2013 09:46:55.062 sp = 4
11/30/2013 09:46:55.094 type = SQL Server Standalone Product
11/30/2013 09:46:55.094 vermajbld = 5000
11/30/2013 09:46:55.094 version = 9
11/30/2013 09:46:55.109
11/30/2013 09:46:55.125 Product Enumeration Results:
11/30/2013 09:46:55.140 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS.inf
11/30/2013 09:46:55.140 arpfolder = OLAP9_KB2716429_ENU
11/30/2013 09:46:55.140 associatedhotfixbuild = 5320
11/30/2013 09:46:55.140 baselinebuild = 5000
11/30/2013 09:46:55.140 baselinebuildmax = 5069
11/30/2013 09:46:55.140 build = 5069
11/30/2013 09:46:55.140 description = SQL Server Analysis Services 2005
11/30/2013 09:46:55.140 details = Patch for Analysis Services 2005
11/30/2013 09:46:55.140 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.140 kbarticle = KB2716429
11/30/2013 09:46:55.140 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.140 legalproductname = SQL Server Analysis Services 2005
11/30/2013 09:46:55.156 machinetype = x86
11/30/2013 09:46:55.156 package = HotFixAS
11/30/2013 09:46:55.156 packagetype = GDR
11/30/2013 09:46:55.156 productname = OLAP9
11/30/2013 09:46:55.156 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.156 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.156 splevel = 4
11/30/2013 09:46:55.156 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.156 validateauthentication = true
11/30/2013 09:46:55.156 version = 9
11/30/2013 09:46:55.156
11/30/2013 09:46:55.156 File Group Details: MSP
11/30/2013 09:46:55.156 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.156 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.172 File Details: sqlrun_as.msp
11/30/2013 09:46:55.172
11/30/2013 09:46:55.172 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.172 associatedhotfixbuild = 1520
11/30/2013 09:46:55.172 clustername =
11/30/2013 09:46:55.187 default = TRUE
11/30/2013 09:46:55.203 fullversion = 2005.090.5057.00
11/30/2013 09:46:55.219 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.2
11/30/2013 09:46:55.219 id = MSSQL.2
11/30/2013 09:46:55.219 installsqldatadir = C:\Program Files\Microsoft SQL Server\
11/30/2013 09:46:55.234 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\
11/30/2013 09:46:55.250 lcid = 1033
11/30/2013 09:46:55.265 name = MSSQLSERVER
11/30/2013 09:46:55.297 olapservicename = MSSQLServerOLAPService
11/30/2013 09:46:55.297 productcode = {8ABF8FEB-ABB0-40DC-9945-85AF36EF30A9}
11/30/2013 09:46:55.297 qfelevel = 5057
11/30/2013 09:46:55.297 servicename = MSSQLServerOLAPService
11/30/2013 09:46:55.297 sku = STANDARD
11/30/2013 09:46:55.297 sp = 4
11/30/2013 09:46:55.297 type = Olap Standalone Product
11/30/2013 09:46:55.297 vermajbld = 5000
11/30/2013 09:46:55.297 version = 9
11/30/2013 09:46:55.297
11/30/2013 09:46:55.297 Product Enumeration Results:
11/30/2013 09:46:55.297 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS.inf
11/30/2013 09:46:55.297 arpfolder = NS9_KB2716429_ENU
11/30/2013 09:46:55.297 associatedhotfixbuild = 5320
11/30/2013 09:46:55.297 baselinebuild = 5000
11/30/2013 09:46:55.297 baselinebuildmax = 5069
11/30/2013 09:46:55.297 build = 5069
11/30/2013 09:46:55.297 description = SQL Server Notification Services 2005
11/30/2013 09:46:55.297 details = Patch for SQL Server Notification Services 2005
11/30/2013 09:46:55.297 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.312 kbarticle = KB2716429
11/30/2013 09:46:55.312 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.312 legalproductname = SQL Server Notification Services 2005 instances
11/30/2013 09:46:55.312 machinetype = x86
11/30/2013 09:46:55.312 package = HotFixNS
11/30/2013 09:46:55.312 packagetype = GDR
11/30/2013 09:46:55.312 productname = NS9
11/30/2013 09:46:55.312 recommendinstall = 1
11/30/2013 09:46:55.312 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.312 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.312 splevel = 4
11/30/2013 09:46:55.312 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.312 validateauthentication = true
11/30/2013 09:46:55.312 version = 9
11/30/2013 09:46:55.312
11/30/2013 09:46:55.312 File Group Details: MSP
11/30/2013 09:46:55.312 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.312 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.312 File Details: sqlrun_ns.msp
11/30/2013 09:46:55.312
11/30/2013 09:46:55.312 Instance Details: NS
11/30/2013 09:46:55.312 associatedhotfixbuild = 5292
11/30/2013 09:46:55.328 clustername =
11/30/2013 09:46:55.328 fullversion = 9.00.5057.00
11/30/2013 09:46:55.328 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\NS
11/30/2013 09:46:55.328 id =
11/30/2013 09:46:55.328 installsqldatadir =
11/30/2013 09:46:55.328 installsqldir = C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\
11/30/2013 09:46:55.328 lcid = 1033
11/30/2013 09:46:55.328 name =
11/30/2013 09:46:55.375 productcode = {37E9AD9F-3217-4229-B5A5-7A0C82364C6C}
11/30/2013 09:46:55.390 qfelevel = 5057
11/30/2013 09:46:55.406 sku = STANDARD
11/30/2013 09:46:55.406 sp = 4
11/30/2013 09:46:55.406 type = Tools Only
11/30/2013 09:46:55.406 vermajbld = 5000
11/30/2013 09:46:55.422 version = 9
11/30/2013 09:46:55.422
11/30/2013 09:46:55.422 Product Enumeration Results:
11/30/2013 09:46:55.422 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS.inf
11/30/2013 09:46:55.422 arpfolder = RS9_KB2716429_ENU
11/30/2013 09:46:55.422 associatedhotfixbuild = 5320
11/30/2013 09:46:55.422 baselinebuild = 5000
11/30/2013 09:46:55.422 baselinebuildmax = 5069
11/30/2013 09:46:55.422 build = 5069
11/30/2013 09:46:55.453 description = SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 details = Patch for SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.453 kbarticle = KB2716429
11/30/2013 09:46:55.453 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.453 legalproductname = SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 machinetype = x86
11/30/2013 09:46:55.453 package = HotFixRS
11/30/2013 09:46:55.453 packagetype = GDR
11/30/2013 09:46:55.453 productname = RS9
11/30/2013 09:46:55.469 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.469 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.469 splevel = 4
11/30/2013 09:46:55.469 sqlutility = sqlcmd.exe
11/30/2013 09:46:55.469 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.469 validateauthentication = true
11/30/2013 09:46:55.469 version = 9
11/30/2013 09:46:55.469
11/30/2013 09:46:55.469 File Group Details: MSP
11/30/2013 09:46:55.469 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.469 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.469 File Details: sqlrun_rs.msp
11/30/2013 09:46:55.469
11/30/2013 09:46:55.469 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.469 associatedhotfixbuild = 5292
11/30/2013 09:46:55.469 clustername =
11/30/2013 09:46:55.469 default = TRUE
11/30/2013 09:46:55.469 fullversion = 9.00.5057.00
11/30/2013 09:46:55.469 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.3
11/30/2013 09:46:55.469 id = MSSQL.3
11/30/2013 09:46:55.469 installsqldatadir =
11/30/2013 09:46:55.469 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\
11/30/2013 09:46:55.484 lcid = 1033
11/30/2013 09:46:55.484 name = MSSQLSERVER
11/30/2013 09:46:55.484 productcode = {E930E839-998E-42F9-97E2-71FC960DB1B7}
11/30/2013 09:46:55.484 qfelevel = 5057
11/30/2013 09:46:55.484 rsservicename = ReportServer
11/30/2013 09:46:55.484 servicename =
11/30/2013 09:46:55.484 sku = STANDARD
11/30/2013 09:46:55.484 sp = 4
11/30/2013 09:46:55.484 type = Report Server Standalone Product
11/30/2013 09:46:55.484 vermajbld = 5000
11/30/2013 09:46:55.484 version = 9
11/30/2013 09:46:55.484
11/30/2013 09:46:55.484 Product Enumeration Results:
11/30/2013 09:46:55.484 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS.inf
11/30/2013 09:46:55.500 arpfolder = DTS9_KB2716429_ENU
11/30/2013 09:46:55.625 associatedhotfixbuild = 5320
11/30/2013 09:46:55.625 baselinebuild = 5000
11/30/2013 09:46:55.625 baselinebuildmax = 5069
11/30/2013 09:46:55.625 build = 5069
11/30/2013 09:46:55.625 description = SQL Server Integration Services 2005
11/30/2013 09:46:55.625 details = Patch for SQL Server Integration Services 2005
11/30/2013 09:46:55.625 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.625 kbarticle = KB2716429
11/30/2013 09:46:55.625 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.625 legalproductname = SQL Server Integration Services 2005
11/30/2013 09:46:55.625 machinetype = x86
11/30/2013 09:46:55.640 package = HotFixDTS
11/30/2013 09:46:55.640 packagetype = GDR
11/30/2013 09:46:55.640 productname = DTS9
11/30/2013 09:46:55.640 recommendinstall = 1
11/30/2013 09:46:55.640 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.640 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.640 splevel = 4
11/30/2013 09:46:55.640 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.640 version = 9
11/30/2013 09:46:55.640
11/30/2013 09:46:55.640 File Group Details: MSP
11/30/2013 09:46:55.640 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.640 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.640 File Details: sqlrun_dts.msp
11/30/2013 09:46:55.640
11/30/2013 09:46:55.640 Instance Details: Integration Services
11/30/2013 09:46:55.640 associatedhotfixbuild = 5292
11/30/2013 09:46:55.640 clustername =
11/30/2013 09:46:55.640 dtsservicename = MsDtsServer
11/30/2013 09:46:55.640 fullversion = 9.00.5057.00
11/30/2013 09:46:55.656 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\DTS
11/30/2013 09:46:55.656 id =
11/30/2013 09:46:55.656 installsqldatadir =
11/30/2013 09:46:55.656 installsqldir = C:\Program Files\Microsoft SQL Server\90\DTS\
11/30/2013 09:46:55.656 lcid = 1033
11/30/2013 09:46:55.656 name =
11/30/2013 09:46:55.656 productcode = {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
11/30/2013 09:46:55.656 qfelevel = 5057
11/30/2013 09:46:55.656 servicename = MsDtsServer
11/30/2013 09:46:55.656 sku = STANDARD
11/30/2013 09:46:55.656 sp = 4
11/30/2013 09:46:55.656 type = Tools Only
11/30/2013 09:46:55.656 vermajbld = 5000
11/30/2013 09:46:55.656 version = 9
11/30/2013 09:46:55.656
11/30/2013 09:46:55.656 Product Enumeration Results:
11/30/2013 09:46:55.672 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools.inf
11/30/2013 09:46:55.672 arpfolder = SQLTools9_KB2716429_ENU
11/30/2013 09:46:55.672 associatedhotfixbuild = 5320
11/30/2013 09:46:55.672 baselinebuild = 5000
11/30/2013 09:46:55.672 baselinebuildmax = 5069
11/30/2013 09:46:55.672 build = 5069
11/30/2013 09:46:55.672 description = SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 details = Patch for SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.672 kbarticle = KB2716429
11/30/2013 09:46:55.672 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.672 legalproductname = SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 machinetype = x86
11/30/2013 09:46:55.672 package = HotFixTools
11/30/2013 09:46:55.672 packagetype = GDR
11/30/2013 09:46:55.672 productname = SQLTools9
11/30/2013 09:46:55.672 recommendinstall = 1
11/30/2013 09:46:55.672 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.672 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.672 splevel = 4
11/30/2013 09:46:55.672 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.687 version = 9
11/30/2013 09:46:55.687
11/30/2013 09:46:55.687 File Group Details: MSP
11/30/2013 09:46:55.687 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.687 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.687 File Details: sqlrun_tools.msp
11/30/2013 09:46:55.687
11/30/2013 09:46:55.687 Instance Details: SQL Tools
11/30/2013 09:46:55.687 associatedhotfixbuild = 5292
11/30/2013 09:46:55.687 clustername =
11/30/2013 09:46:55.687 fullversion = 9.4.5057
11/30/2013 09:46:55.687 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\Tools
11/30/2013 09:46:55.687 id =
11/30/2013 09:46:55.687 installsqldatadir =
11/30/2013 09:46:55.687 installsqldir = C:\Program Files\Microsoft SQL Server\90\Tools\
11/30/2013 09:46:55.687 lcid = 1033
11/30/2013 09:46:55.687 name =
11/30/2013 09:46:55.687 productcode = {1DD463C0-A50A-4394-B7E4-5895C02F9E0D}
11/30/2013 09:46:55.687 qfelevel = 5057
11/30/2013 09:46:55.687 sku = STANDARD
11/30/2013 09:46:55.687 sp = 4
11/30/2013 09:46:55.687 type = Tools Only
11/30/2013 09:46:55.703 vermajbld = 5000
11/30/2013 09:46:55.703 version = 9
11/30/2013 09:46:55.703
11/30/2013 09:47:00.781 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
11/30/2013 09:47:00.781 Registry: Cannot read registry key value "PendingFileRenameOperations", error 0
11/30/2013 09:47:00.812 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.719 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.734 Locked file: Checking for locked files
11/30/2013 09:47:04.328 Attempting to pause the 32 bit ngen queue
11/30/2013 09:47:04.968 Installing product: SQL9
11/30/2013 09:47:05.781 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:05.781 Installing instance: MSSQLSERVER
11/30/2013 09:47:05.812 Installing target: SV53704
11/30/2013 09:47:05.828 Installing file: sqlrun_sql.msp
11/30/2013 09:47:05.828 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2716429_sqlrun_sql.msp.log
11/30/2013 09:47:05.828 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:05.828 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:06.203 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:06.203 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:06.203 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:06.218 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL\Files\sqlrun_sql.msp
11/30/2013 09:47:06.218 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:06.218 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:06.640 Watson: Param1 = Unknown
11/30/2013 09:47:06.640 Watson: Param2 = 0x66e
11/30/2013 09:47:06.640 Watson: Param3 = Unknown
11/30/2013 09:47:06.640 Watson: Param4 = 0x66e
11/30/2013 09:47:06.656 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:06.656 Watson: Param6 = Unknown
11/30/2013 09:47:06.656 Watson: Param7 = SQL9
11/30/2013 09:47:06.656 Watson: Param8 = @
11/30/2013 09:47:06.656 Watson: Param9 = x86
11/30/2013 09:47:06.656 Watson: Param10 = 5069
11/30/2013 09:47:06.656 Installed product: SQL9
11/30/2013 09:47:06.656 Installing product: OLAP9
11/30/2013 09:47:07.468 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:07.484 Installing instance: MSSQLSERVER
11/30/2013 09:47:07.484 Installing target: SV53704
11/30/2013 09:47:07.500 Installing file: sqlrun_as.msp
11/30/2013 09:47:07.500 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB2716429_sqlrun_as.msp.log
11/30/2013 09:47:07.515 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:07.515 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:07.640 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:07.640 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:07.640 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:07.656 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS\Files\sqlrun_as.msp
11/30/2013 09:47:07.656 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:07.656 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:08.078 Watson: Param1 = Unknown
11/30/2013 09:47:08.078 Watson: Param2 = 0x66e
11/30/2013 09:47:08.078 Watson: Param3 = Unknown
11/30/2013 09:47:08.078 Watson: Param4 = 0x66e
11/30/2013 09:47:08.078 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:08.078 Watson: Param6 = Unknown
11/30/2013 09:47:08.078 Watson: Param7 = OLAP9
11/30/2013 09:47:08.078 Watson: Param8 = @
11/30/2013 09:47:08.078 Watson: Param9 = x86
11/30/2013 09:47:08.078 Watson: Param10 = 5069
11/30/2013 09:47:08.078 Installed product: OLAP9
11/30/2013 09:47:08.078 Installing product: RS9
11/30/2013 09:47:08.875 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:08.875 Installing instance: MSSQLSERVER
11/30/2013 09:47:08.890 Installing target: SV53704
11/30/2013 09:47:08.890 Installing file: sqlrun_rs.msp
11/30/2013 09:47:08.890 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\RS9_Hotfix_KB2716429_sqlrun_rs.msp.log
11/30/2013 09:47:08.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:08.890 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:09.015 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:09.015 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:09.015 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:09.031 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS\Files\sqlrun_rs.msp
11/30/2013 09:47:09.047 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:09.047 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:09.593 Watson: Param1 = Unknown
11/30/2013 09:47:09.593 Watson: Param2 = 0x66e
11/30/2013 09:47:09.593 Watson: Param3 = Unknown
11/30/2013 09:47:09.609 Watson: Param4 = 0x66e
11/30/2013 09:47:09.609 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:09.609 Watson: Param6 = Unknown
11/30/2013 09:47:09.609 Watson: Param7 = RS9
11/30/2013 09:47:09.609 Watson: Param8 = @
11/30/2013 09:47:09.609 Watson: Param9 = x86
11/30/2013 09:47:09.609 Watson: Param10 = 5069
11/30/2013 09:47:09.625 Installed product: RS9
11/30/2013 09:47:09.625 Installing product: NS9
11/30/2013 09:47:10.406 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:10.406 Installing instance: NS
11/30/2013 09:47:10.422 Installing target: SV53704
11/30/2013 09:47:10.422 Installing file: sqlrun_ns.msp
11/30/2013 09:47:10.422 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\NS9_Hotfix_KB2716429_sqlrun_ns.msp.log
11/30/2013 09:47:10.422 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:10.422 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:10.531 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:10.531 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:10.531 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:10.547 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS\Files\sqlrun_ns.msp
11/30/2013 09:47:10.547 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:10.547 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:10.890 Watson: Param1 = Unknown
11/30/2013 09:47:10.890 Watson: Param2 = 0x66e
11/30/2013 09:47:10.890 Watson: Param3 = Unknown
11/30/2013 09:47:10.890 Watson: Param4 = 0x66e
11/30/2013 09:47:10.890 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:10.890 Watson: Param6 = Unknown
11/30/2013 09:47:10.890 Watson: Param7 = NS9
11/30/2013 09:47:10.890 Watson: Param8 = @
11/30/2013 09:47:10.890 Watson: Param9 = x86
11/30/2013 09:47:10.890 Watson: Param10 = 5069
11/30/2013 09:47:10.890 Installed product: NS9
11/30/2013 09:47:10.890 Installing product: DTS9
11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:11.703 Installing instance: Integration Services
11/30/2013 09:47:11.703 Installing target: SV53704
11/30/2013 09:47:11.703 Installing file: sqlrun_dts.msp
11/30/2013 09:47:11.703 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log
11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:11.718 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:11.890 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:11.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:11.906 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:11.906 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS\Files\sqlrun_dts.msp
11/30/2013 09:47:11.922 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:11.922 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:12.328 Watson: Param1 = Unknown
11/30/2013 09:47:12.328 Watson: Param2 = 0x66e
11/30/2013 09:47:12.328 Watson: Param3 = Unknown
11/30/2013 09:47:12.328 Watson: Param4 = 0x66e
11/30/2013 09:47:12.328 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:12.328 Watson: Param6 = Unknown
11/30/2013 09:47:12.328 Watson: Param7 = DTS9
11/30/2013 09:47:12.328 Watson: Param8 = @
11/30/2013 09:47:12.328 Watson: Param9 = x86
11/30/2013 09:47:12.328 Watson: Param10 = 5069
11/30/2013 09:47:12.343 Installed product: DTS9
11/30/2013 09:47:12.343 Installing product: SQLTools9
11/30/2013 09:47:13.125 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:13.140 Installing instance: SQL Tools
11/30/2013 09:47:13.140 Installing target: SV53704
11/30/2013 09:47:13.156 Installing file: sqlrun_tools.msp
11/30/2013 09:47:13.172 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB2716429_sqlrun_tools.msp.log
11/30/2013 09:47:13.172 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:13.172 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:13.484 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:13.484 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:13.484 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:13.500 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools\Files\sqlrun_tools.msp
11/30/2013 09:47:13.500 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:13.500 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:13.828 Watson: Param1 = Unknown
11/30/2013 09:47:13.828 Watson: Param2 = 0x66e
11/30/2013 09:47:13.843 Watson: Param3 = Unknown
11/30/2013 09:47:13.843 Watson: Param4 = 0x66e
11/30/2013 09:47:13.843 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:13.843 Watson: Param6 = Unknown
11/30/2013 09:47:13.843 Watson: Param7 = SQLTools9
11/30/2013 09:47:13.843 Watson: Param8 = @
11/30/2013 09:47:13.843 Watson: Param9 = x86
11/30/2013 09:47:13.843 Watson: Param10 = 5069
11/30/2013 09:47:13.843 Installed product: SQLTools9
11/30/2013 09:47:13.843 Hotfix package completed
11/30/2013 09:47:13.859 Attempting to continue the 32 bit ngen queueHi ~ any idea on this case ? here is the one MSP installation log:
=== Verbose logging started: 11/30/2013 21:28:15 Build type: SHIP UNICODE 4.05.6001.00 Calling process: e:\de60d5388bc787220900e629b152c9\hotfix.exe ===
MSI (c) (D4:28) [21:28:15:681]: Resetting cached policy values
MSI (c) (D4:28) [21:28:15:681]: Machine policy value 'Debug' is 0
MSI (c) (D4:28) [21:28:15:681]: ******* RunEngine:
******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
******* Action:
******* CommandLine: **********
MSI (c) (D4:28) [21:28:15:681]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (D4:28) [21:28:15:681]: Grabbed execution mutex.
MSI (c) (D4:28) [21:28:15:697]: Cloaking enabled.
MSI (c) (D4:28) [21:28:15:697]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (D4:28) [21:28:15:697]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A8:C0) [21:28:15:697]: Running installation inside multi-package transaction {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
MSI (s) (A8:C0) [21:28:15:697]: Grabbed execution mutex.
MSI (s) (A8:04) [21:28:15:697]: Resetting cached policy values
MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'Debug' is 0
MSI (s) (A8:04) [21:28:15:697]: ******* RunEngine:
******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
******* Action:
******* CommandLine: **********
MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (A8:04) [21:28:15:931]: End dialog not enabled
MSI (s) (A8:04) [21:28:15:931]: Original package ==> C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:04) [21:28:15:931]: Package we're running from ==> C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: looking for appcompat database entry with ProductCode '{EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}'.
MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (A8:04) [21:28:15:994]: Opening existing patch 'C:\WINDOWS\Installer\e9ff36e.msp'.
MSI (s) (A8:04) [21:28:16:010]: Opening existing patch 'C:\WINDOWS\Installer\239697ae.msp'.
MSI (s) (A8:04) [21:28:16:056]: File will have security applied from OpCode.
MSI (s) (A8:04) [21:28:16:056]: Original patch ==> e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
MSI (s) (A8:04) [21:28:16:056]: Patch we're running from ==> C:\WINDOWS\Installer\1f80a9f.msp
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp' against software restriction policy
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not digitally signed
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (A8:04) [21:28:16:072]: SequencePatches starts. Product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, Product version: 9.00.1399.06, Upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}, Product language 1033
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: verifying the applicability of QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp against product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, product version: 9.00.1399.06, product language
1033 and upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}
MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not applicable.
MSI (s) (A8:04) [21:28:16:072]: SequencePatches returns success.
MSI (s) (A8:04) [21:28:16:072]: Final Patch Application Order:
MSI (s) (A8:04) [21:28:16:072]: Other Patches:
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C} - e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
MSI (s) (A8:04) [21:28:16:072]: Superseded: {5E9ADA2D-3132-42CF-8628-D2ADA0F335EE} -
MSI (s) (A8:04) [21:28:16:072]: Superseded: {32BCE9F2-8686-487A-80A9-A401C0F7DCBD} -
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {D23D25E7-0AB4-41EE-81B5-F0CF34D1BA2B} -
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {CF321155-04AA-4CF8-BB9A-DA3144835E3E} -
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisablePatch' is 0
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (A8:04) [21:28:16:072]: Disallowing uninstallation of patch {CF321155-04AA-4CF8-BB9A-DA3144835E3E} because the patch is marked as not uninstallable
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'Service Pack 4 for SQL Server Integration Services 2005 ENU (KB2463332)' could not be removed. Error code 1646. Additional information is available in the log
file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: Service Pack 4 for SQL Server Integration Services 2005 ENU
(KB2463332). Removal success or error status: 0.
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update '{4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}' could not be installed. Error code 1646. Additional information is available in the log file C:\Program Files\Microsoft
SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}. Installation success
or error status: 1646.
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120)' could not be removed. Error code 1646. Additional information is available in the log file C:\Program
Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120).
Removal success or error status: 1646.
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 1708
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services -- Installation failed.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Installation success or error status: 1646.
MSI (s) (A8:04) [21:28:16:088]: Attempting to delete file C:\WINDOWS\Installer\1f80a9f.msp
MSI (s) (A8:04) [21:28:16:088]: MainEngineThread is returning 1646
MSI (s) (A8:C0) [21:28:16:088]: No System Restore sequence number for this installation.
Uninstallation of the patch package is not supported.
C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:C0) [21:28:16:088]: User policy value 'DisableRollback' is 0
MSI (s) (A8:C0) [21:28:16:088]: Machine policy value 'DisableRollback' is 0
MSI (s) (A8:C0) [21:28:16:088]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (A8:C0) [21:28:16:088]: Restoring environment variables
MSI (c) (D4:28) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (D4:28) [21:28:16:088]: MainEngineThread is returning 1646
=== Verbose logging stopped: 11/30/2013 21:28:16 === -
Help with cisco ISE 1.1.2.145 patch-3 to ISE 1.2.0.899-2-85601 upgrade procedure
Need help from ISE experts/gurus in this forum.
Due to a nasty bug in Cisco ISE (bug ID CSCue38827 ISE Adclient daemon not initializing on leave/join), this bug will make the ISE stopping working completely and a reboot is required (very nice bug from cisco) . This leaves me no choice but to upgrade to version 1.2.0.899-2-85601.
Scenario:
- 4 nodes in the environment running ISE version 1.1.2.145 patch 3
- node 1 is Primary Admin and Secondary Monitoring - hostname is node1
- node 2 is Secondary Admin and Primary Monitoring - hostname is node2
- node 3 is Policy service node - hostname is node3
- node 4 is Policy service node - hostname is node4
Objective: Upgrade the ISE environment to ISE version 1.2 with patch version 1.2.0.899-2-85601.
My understand is that I have to upgrade the existing environment from ISE version 1.1.2.145 patch 3
to ISE version 1.1.2.145 patch 10 (patch 10 was released on 10/04/2013) before I can proceed with
upgrading to ISE version 1.2 and patch it with 1.2.0.899-2-85601.
Can I patch my exsiting environment from 1.1.2 patch 3 to patch 10 prior to upgrading to version 1.2.0.899-2-85601?
I look at Cisco website and patch 10 was released on 10/04/2013 while version 1.2 was released back in 07/05/2013.
I am trying to get a definite answer from Cisco TAC but it seems like they don't know either.
Question #1: How do I proceed with upgrading the current ISE environment from 1.1.2.145 patch 3 to 1.1.2.145 patch 10?
Propose solution:
step #1: make ISE node1 to be both Primary Admin and Primary monitoring. ISE node2 is now Secondary Admin and Secondary Monitoring.
Then go ahead and apply ISE version 1.1.2.145 patch 10 to ISE node2 via the GUI,
step #2: Once ISE node2 patch 10 is completed, make node2 Primary Admin and Primary Monitoring. At this point, apply ISE 1.1.2.145 patch 10
to ISE node1 via the GUI,
step #3: Once ISE node1 patch 10 is completed, make node1 Primary Admin and Secondary Monitoring and node2 Secondary Admin and Primary Monitoring,
step #4: apply ISE 1.1.2.145 patch 10 to ISE Policy Service node3. Once that is completed, verify that node2 is working and accepting traffics,
step #5: apply ISE 1.1.2.145 patch 10 to ISE Policy Service node4. Once that is completed, verify that node2 is working and accepting traffics,
Question #2: How do I proceed with upgrading the current ISE environment from 1.1.2.145 patch 10 to ISE version 1.2 with patch version 1.2.0.899-2-85601?
Propose solution:
step #1: Make ISE node1 the Primary Admin and Primary monitoring. At this point ISE node2 will become Secondary Admin and Secondary Monitoring
step #2: Perform upgrade on the ISE node2 via the command line "application upgrade <app-bundle> <repository>". Once ISE node2 upgrade is completed, it will
form a new ISE 1.2 cluster independent of the old cluster,
step #3: Perform upgrade on the ISE Policy Service node3 via the command line "application upgrade <app-bundle> <repository>". After the upgrade the ISE
Policy Service Node3 will automatically joins the ISE node2 which is already in version 1.2
step #4: Perform upgrade on the ISE Policy Service node4 via the command line "application upgrade <app-bundle> <repository>". After the upgrade the ISE
Policy Service Node4 will automatically joins the ISE node2 which is already in version 1.2
step #5: At this point the only node remaining in the 1.1.2.145 patch 10 is the ISE node1 Primary Admin and Primary Monitoring
step #6: Check and see if there are any more PSN's registered in ISE node1 (there should not be any)
step #7: Perform the upgrade on the ISE node1 from command line "application upgrade <app-bundle> <repository>"
step #8: Once upgrade on ISE node1 is complete, ISE node1 will automatically join the new ISE 1.2 cluster,
step #9: Make ISE node1 Primary Admin and Secondary and ISE node2 Secondary Admin and Primary Monitoring,
Question #3: How do I proceed with upgrading the current ISE environment from 1.2 patch0 to 1.2.0.899-2-85601?
Propose solution:
step #1: make ISE node1 to be both Primary Admin and Primary monitoring. ISE node2 is now Secondary Admin and Secondary Monitoring.
Then go ahead and apply ISE 1.2.0.899-2-85601 to ISE node2 via the GUI,
step #2: Once ISE node2 1.2.0.899-2-85601 is completed, make node2 Primary Admin and Primary Monitoring. At this point, apply 1.2.0.899-2-85601
to ISE node1 via the GUI,
step #3: Once ISE node1 patch 10 is completed, make node1 Primary Admin and Secondary Monitoring and node2 Secondary Admin and Primary Monitoring,
step #4: apply ISE 1.2.0.899-2-85601 to ISE Policy Service node3. Once that is completed, verify that node2 is working and accepting traffics,
step #5: apply ISE 1.2.0.899-2-85601 to ISE Policy Service node4. Once that is completed, verify that node2 is working and accepting traffics,
does these steps make sense to you?
Thanks in advance.David,
A few answers to your questions -
Question 1: My recommendation is to follow vivek's blog since most fixes and upgrade steps are provided there - I would recommend installing the patch that was release prior to the 1.2 release date since the directions to "install the latest patch" would put you at the version of when the ISE 1.2 was released
https://supportforums.cisco.com/community/netpro/security/aaa/blog/2013/07/19/upgrading-to-identity-services-engine-ise-12
You do not have the ability to install ISE patch through the GUI on any of the "non-primary" nodes (you can use the cli commmand to achieve this), the current patching process was designed so you can install the patch on the primary admin node and it will then roll the patches out to the entire deployment (one node at at time). I painfully verified this by watching the services on each node and when a node was up and operational the next node would start the patching process. First the admin nodes then the PSNs.
Every ISE upgrade that I have attempted as not been flawless and I can assure you that I have done an upgrade on 1.1.2 patch 3 and this worked fine, however I used the following process. You will need the service account information that is used to join your ISE to AD.
I picked the secondary admin/monitoring node and made it a standalone node by deregistering (much like the old procedure) in your case this will be node2.
I backed up the certificates from the UI and the database from the CLI (pick the local disk or ftp-your choice).
I reset the database and ran the upgrade script (since I did not have access to the vsphere console or at the location of the non UCS hardware [for a 1.1.4 upgrade]).
Once the upgrade was completed I then restored the 1.1.x database, ISE 1.2 now has the ability to detect the version of the database that is restored and will perform the migration for you.
Once the restore finished, I then restored the certificate and picked one of the PSNs
backup the cert,
Had the AD join user account handy
reset-db,
and run the upgrade script.
Once that is done I then restore the cert
Join the PSN to the new deployment
Join both nodes to AD through primary admin node
Monitor for a few days (seperate consoles to make sure everything runs smooth)
If anything doesnt look or feel right, you can shut down the 1.2 PSN and force everything through the existing 1.1.2 setup and perform some investigation, if it all goes smooth you can then follow the above step for the other two nodes, starting with the last PSN and the the last admin node.
Thanks and I hope that helps,
Tarik Admani
*Please rate helpful posts* -
BizTalk 2013 - BAMAlerts service crash
Hi,
I am deploying BizTalk into a new clean Production environment. My topology is the following:
- 2 SQL Server machines (clustered)
- 2 BizTalk application servers (with BTS runtime)
- 1 BAM server
I have everything deployed and working well except for the BAMAlerts service crashing a minute after it starts on the BAM server.
The software installed on the BAM server is:
Windows 2008 R2 x64
SQL Server 2012 SP1 x64 with the following features:
Reporting Services (Native)
SQL Server Data Tools
Client Tools Connectivity
Integration Services
Management Tools – Basic
Management Tools – Complete
SQL Server 2012 SP1 Cumulative Update 9
BizTalk Server 2013 x64 with the following features:
Portal Components
Business Activity Monitoring
Administrative Tools and Monitoring
Additional Software
Enterprise Single Sign-On Administration Module
Enterprise Single Sign-On Master Secret Server
BAM Alert Provider for SQL Notification Services
BAM Client
BAM-Eventing
Office Excel 2013 (x86)
Once the BizTalk binaries are installed I installed Windows Update suggested patches including the update for BizTalk Server 2013 (KB2830546).
I then went on and configured the relevant features. Configuration worked well but the BAMAlerts service crashes 1 minute after starting with the following error:
Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "". ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection
to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I verified the following:
A database mail profile was created on the SQL Server instance and it works (I can use it to send emails)
Using the BAMAlerts service account I am able to connect to the SQL Server instance using Named Pipes or TCP/IP, call BizTalkMgmtDb.dbo.adm_Group_GetBAMServerAndDBName or query tables
I installed SQL Server 2005 Notification Services x64 in order to see if it helps but no success.
I installed BizTalk 2013 Cumulative Update 2 but it did no help either.
The worse part is that I hit the same issue when setting up our UAT environment, tried a number of things and ended up with a setup that works but I am not able to reproduce that success in Prod...
Following is the full error message:
Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "". ---> System.Data.SqlClient.SqlException:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteQuery(String cmdText, CommandType cmdType, Transaction transaction)
--- End of inner exception stack trace ---
at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteQuery(String cmdText, CommandType cmdType, Transaction transaction)
at Microsoft.BizTalk.Bam.AlertHost.AlertHost.Run()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Thanks
EmmanuelKnown issue, you need BizTalk Server 2013 CU1:
http://support.microsoft.com/kb/2838133/en-us
(See hotfix 2832137)
Morten la Cour -
Patching 11.1.1.6.2: Opatch Failed error code 39
Hi everyone,
i am just patching OBI EE 11.1.1.6.0 to 11.1.1.6.2.
While applying opatch for the paricular patches i got an error with this patch: *14228505*
The logfile says:
[21.01.2013 11:59:29] OPatch invoked as follows: 'apply '
[21.01.2013 11:59:29] Oracle Home : c:\oracle\middleware\Oracle_BI1
Zentrales Bestandsverzeichnis: C:\Program Files\Oracle\Inventory
von : n/a
OPatch-Version : 11.1.0.9.0
OUI-Version : 11.1.0.9.0
OUI-Speicherort : c:\oracle\middleware\Oracle_BI1\oui
Speicherort von Log-Datei : c:\oracle\middleware\Oracle_BI1\cfgtoollogs\opatch\14228505_Jan_21_2013_11_59_28\apply2013-01-21_11-59-27AM_1.log
[21.01.2013 11:59:29] Patch history file: c:\oracle\middleware\Oracle_BI1\cfgtoollogs\opatch\opatch_history.txt
[21.01.2013 11:59:29] OPatch detects the Middleware Home as "C:\oracle\middleware"
[21.01.2013 11:59:33] Starting ApplySession on Mon Jan 21 11:59:33 CET 2013
[21.01.2013 11:59:33] OPatch will do the following:
[Oracle Home discovery] : Configure and Validate Oracle Home info.
[Prerequisite for apply] : Invoke prerequisites to see if patch can be applied.
[Patch conflict detection for apply patch] : Check if any conflict with already installed patches in Oracle Home.
[21.01.2013 11:59:33] --------------------- Oracle Home discovery ---------------------
[21.01.2013 11:59:33] ApplySession Interim-Patch '14228505' wird für OH 'c:\oracle\middleware\Oracle_BI1' angewendet
[21.01.2013 11:59:33] Starting to apply patch to local system at Mon Jan 21 11:59:33 CET 2013
[21.01.2013 11:59:36] Start the Apply initScript at Mon Jan 21 11:59:36 CET 2013
[21.01.2013 11:59:36] Finish the Apply initScript at Mon Jan 21 11:59:36 CET 2013
[21.01.2013 11:59:36] --------------------- Prerequisite for apply ---------------------
[21.01.2013 11:59:36] Running prerequisite checks...
[21.01.2013 11:59:36] Patch "14228505" is ignored as it is not a "Fusion Applications patch".
[21.01.2013 11:59:36] Check if patch "14228505" is a no-op patch.
[21.01.2013 11:59:36] None of the selected patches are no-op. patches..
[21.01.2013 11:59:38] Space Needed : 4221147894
[21.01.2013 11:59:38] Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
The details are:
Patch ( 14228505 ) is not applicable on current platform.
Platform ID needed is : 912
Platform IDs supported by patch are: 233
[21.01.2013 11:59:42] [ Error during Prerequisite for apply phase ] Detail: OUI-67074:OPatch während Prüfung auf Voraussetzungen nicht erfolgreich: Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
[21.01.2013 11:59:42] System intakt, OPatch versucht nicht, das System zurückzuschreiben
[21.01.2013 11:59:42] Finishing ApplySession at Mon Jan 21 11:59:42 CET 2013
[21.01.2013 11:59:42] Total time spent waiting for user-input is 0 seconds. Finish at Mon Jan 21 11:59:42 CET 2013
[21.01.2013 11:59:42] Stack-Beschreibung: oracle.opatch.PrereqFailedException: Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed.
[21.01.2013 11:59:42] StackTrace: oracle.opatch.OPatchSessionHelper.runApplyPrereqs(OPatchSessionHelper.java:5939)
[21.01.2013 11:59:42] StackTrace: oracle.opatch.ApplySession.processLocal(ApplySession.java:3780)
[21.01.2013 11:59:42] StackTrace: oracle.opatch.ApplySession.process(ApplySession.java:5824)
[21.01.2013 11:59:42] StackTrace: oracle.opatch.OPatchSession.main(OPatchSession.java:1871)
[21.01.2013 11:59:42] StackTrace: oracle.opatch.OPatch.main(OPatch.java:573)
CMD says:
Recommended actions: This patch requires some components to be installed in the home. Either the Oracle Home doesn't have the components or this patch is not suitable for this Oracle Home.
What i commandedbefore:
set ORACLE_HOME=D:\Oracle\Middleware\Oracle_BI1
set PATH=%ORACLE_HOME%\bin;%PATH%
set JAVA_HOME=%ORACLE_HOME%\jdk
set PATH=%JAVA_HOME%\bin;%PATH%
set PATH=%ORACLE_HOME%\OPatch;%PATH%
The following patches already succeeded: 14226980, 13960955 and 14226993.
Does anyone of you has an idea? It's really important!
Thank you,
AlexI ran into this problem and this is how I solved it. I had OEM Grid Control installed with the database and OMS on the same server. opatch always worked when using the database Oracle Home. Our company moved the database to another system, so I tried using the OMS Oracle Home and got the error. The OMS Oracle Home is a 10.1.0.5 version. I believe I installed the 10.2 Opatch in the directory with a unzip -o option.
I started clean. I renamed the old OPatch and reinstalled the 6880880 patch for the required version. OMS requires the 10.2 version. The problem went away. It had nothing to do with the Java version -
Can LabView 2013 be used to develop blocks for Lego LabView Education EV3?
I would like to interface some custom sensors to the Lego EV3 brick. Can LabView 2013 be used to build Blocks for Lego LabView EV3 software?
Please note Mac OSX users using LabView 2013 Student Edition -- you CAN use the new EV3 modules but you must install f1 patch first.
I installed NI LabVIEW 2013 LEGO MINDSTORMS NXT Module f1 Patch.
Then
NI LabVIEW 2013 Module for LEGO MINDSTORMS f2 Patch
Now I can program for LEGO EV3, download to EV3 and it works all from the LV 2013 Student Edition (UK).
Dr. Michael Vallance
Future University, Japan.
Homepage http://www.mvallance.net
International Virtual Environments Research Group (iVERG) http://www.iverg.com -
Hello Sir,
As per readme for Patch 9179588, I am trying to merge patch (9179588:R12.AD.B) with 9477107:R12.AD.B and R12.AD.B.1
(patch 7461070). When I run admrgpch without -admode option, admrgpch completes successfully.
However, when I just add -admode option in same command, getting error that "invalid option -s". Please see below details and suggest since there is Note: This merge should be a full merge using -admode.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drix10:/fmstop/patches/R1211AD/merge>ls -lrt
total 13992
-rw-r--r-- 1 appltest dba 7035668 Aug 03 10:59 p7461070_R12_AIX64-5L.zip
-rw-r--r-- 1 appltest dba 79016 Aug 04 03:48 p9179588_R12.AD.B_R12_GENERIC.zip
-rw-r--r-- 1 appltest dba 38579 Aug 04 05:22 p9477107_R12.AD.B_R12_GENERIC.zip
-rw-r--r-- 1 appltest dba 94 Aug 04 13:27 manifest.txt
drix10:/fmstop/patches/R1211AD/merge>cat manifest.txt
p7461070_R12_AIX64-5L.zip
p9179588_R12.AD.B_R12_GENERIC.zip
p9477107_R12.AD.B_R12_GENERIC.zip
drix10:/fmstop/patches/R1211AD/merge>
drix10:/fmstop/patches/R1211AD/merge>admrgpch -admode -s /fmstop/patches/R1211AD/merge -d /fmstop/patches/R1211AD/merge -merge_name merged_R12AD11 -manifest manifest.txt
Error: Invalid option: -s
usage: admrgpch -help
admrgpch <source_directory> <destination_directory>
admrgpch -s <source_directory> -d <destination_directory>
[-verbose <level>] [-merge_name <pattern>]
[-manifest <filename>] [-logfile <filename>]
where
* -help Print help message.
* -verbose <level> Can be one of: { 0(SILENT),
1(QUIET), 2(VERBOSE) or 3(LOUD) }
Default - 1(QUIET).
* -merge_name <pattern> The name of the merged patch (max 24 characters).
Default - "merged".
* -s <source_directory> Path of source directory where all patches to be
merged have been unzipped.
* -d <destination_directory> Path of destination directory where the merged
patch will be created.
* -manifest <filename> Full pathname of a file containing the list of
patch zip files to be merged.
* -logfile <filename> Admrgpch log file name.
Default:"<CWD>/admrgpch.log".
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Without option -admode :
drix10:/fmstop/patches/R1211AD/merge>admrgpch -s /fmstop/patches/R1211AD/merge -d /fmstop/patches/R1211AD/merge -merge_name merged_R12AD11 -manifest manifest.txt
unzipping p7461070_R12_AIX64-5L.zip..
unzipping p9179588_R12.AD.B_R12_GENERIC.zip..
unzipping p9477107_R12.AD.B_R12_GENERIC.zip..
Executing the merge of the patch drivers
-- Processing patch: /fmstop/patches/R1211AD/merge/7461070
-- Done processing patch: /fmstop/patches/R1211AD/merge/7461070
-- Processing patch: /fmstop/patches/R1211AD/merge/9179588
-- Done processing patch: /fmstop/patches/R1211AD/merge/9179588
-- Processing patch: /fmstop/patches/R1211AD/merge/9477107
-- Done processing patch: /fmstop/patches/R1211AD/merge/9477107
Copying files...
5% complete. Copied 44 files of 876...
10% complete. Copied 88 files of 876...
15% complete. Copied 132 files of 876...
20% complete. Copied 176 files of 876...
25% complete. Copied 219 files of 876...
30% complete. Copied 263 files of 876...
35% complete. Copied 307 files of 876...
40% complete. Copied 351 files of 876...
45% complete. Copied 395 files of 876...
50% complete. Copied 438 files of 876...
55% complete. Copied 482 files of 876...
60% complete. Copied 526 files of 876...
65% complete. Copied 570 files of 876...
70% complete. Copied 614 files of 876...
75% complete. Copied 657 files of 876...
80% complete. Copied 701 files of 876...
85% complete. Copied 745 files of 876...
90% complete. Copied 789 files of 876...
95% complete. Copied 833 files of 876...
100% complete. Copied 876 files of 876...
Character-set converting files...
3 unified drivers merged.
Patch merge completed successfully
Please check the log file at ./admrgpch.log.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I am executing admrgpch after sourcing 11i environment and version for admrgpch is :
drix10:/fmstop/fmstest/fmstestappl/ad/11.5.0/bin>adident Header admerge.pl
admerge.pl:
$Header admerge.pl 115.22 2008/09/18 12:12:08 nissubra noship $Hi Srini,
Thanks a lot !
Actually, I tried that one as well by running admrgpch from newly installed R12 code tree and I got below error.
drix10:/fmstop/r12apps/apps/apps_st/appl/ad/12.0.0/bin>ls -rlt admrgpch
-rwxr-xr-x 1 appltest dba 14293576 Mar 30 2009 admrgpch
drix10:/fmstop/r12apps/apps/apps_st/appl/ad/12.0.0/bin>admrgpch -s /fmstop/patches/R1211AD/merge -d /fmstop/patches/R1211AD/merge -merge_name merged_R12AD11 -manifest manifest.txt -admode
exec(): 0509-036 Cannot load program ./admrgpch because of the following errors:
0509-150 Dependent module libnnz10.so could not be loaded.
0509-022 Cannot load module libnnz10.so.
0509-026 System error: A file or directory in the path name does not exist.
Then I sourced R12 environment file and ran same command. Its completed successfully.
drix10:/fmstop/patches/R1211AD/merge>admrgpch -s /fmstop/patches/R1211AD/merge -d /fmstop/patches/R1211AD/merge -merge_name merged_R12AD11 -manifest manifest.txt -admode
unzipping p7461070_R12_AIX64-5L.zip..
unzipping p9179588_R12.AD.B_R12_GENERIC.zip..
unzipping p9477107_R12.AD.B_R12_GENERIC.zip..
Executing the merge of the patch drivers
-- Processing patch: /fmstop/patches/R1211AD/merge/7461070
-- Processing file: /fmstop/patches/R1211AD/merge/7461070/u7461070.drv
-- Done processing file: /fmstop/patches/R1211AD/merge/7461070/u7461070.drv
-- Done processing patch: /fmstop/patches/R1211AD/merge/7461070
-- Processing patch: /fmstop/patches/R1211AD/merge/9179588
-- Processing file: /fmstop/patches/R1211AD/merge/9179588/u9179588.drv
-- Done processing file: /fmstop/patches/R1211AD/merge/9179588/u9179588.drv
-- Done processing patch: /fmstop/patches/R1211AD/merge/9179588
-- Processing patch: /fmstop/patches/R1211AD/merge/9477107
-- Processing file: /fmstop/patches/R1211AD/merge/9477107/u9477107.drv
-- Done processing file: /fmstop/patches/R1211AD/merge/9477107/u9477107.drv
-- Done processing patch: /fmstop/patches/R1211AD/merge/9477107
Copying files...
5% complete. Copied 45 files of 883...
10% complete. Copied 89 files of 883...
15% complete. Copied 133 files of 883...
20% complete. Copied 177 files of 883...
25% complete. Copied 221 files of 883...
30% complete. Copied 265 files of 883...
35% complete. Copied 310 files of 883...
40% complete. Copied 354 files of 883...
45% complete. Copied 398 files of 883...
50% complete. Copied 442 files of 883...
55% complete. Copied 486 files of 883...
60% complete. Copied 530 files of 883...
65% complete. Copied 574 files of 883...
70% complete. Copied 619 files of 883...
75% complete. Copied 663 files of 883...
80% complete. Copied 707 files of 883...
85% complete. Copied 751 files of 883...
90% complete. Copied 795 files of 883...
95% complete. Copied 839 files of 883...
100% complete. Copied 883 files of 883...
Character-set converting files...
3 unified drivers merged.
Patch merge completed successfully
Please check the log file at ./admrgpch.log. -
How do I enforce "Show My Picture" instead of "Hide My Picture" in Lync Server 2013?
I was scouring TechNet and the web for a script that could perform the same task as one that I previously used for Lync 2010.
In Lync 2010, we had already used Lync policy to enforce that only the Active Directory photo could be used. One thing that we couldn't set via policy however was the ability to complete remove the "Hide My Picture" option in Lync 2010 client.
This left users with the ability to freely switch between showing the Corporate photo or no photo. I did eventually find and make use of script that constantly checked for this setting switch, then switched all users back to the desired "Show My Picture"
setting. I don't recall who wrote it, but it's easy to find on technet. As we started to move more and more users to our Lync 2013 enterprise pool, I noted that even though the script was running, the setting seemed to be changeable. A closer look revealed
that the script didn't function correctly against SQL for our 2013 pool.
I took the concept and applied it to Lync Server 2013 after studying the differences in Userdata. In Lync 2013, because UserData is in .zip, you need to convert it to 2010 format XML to use logic intended for Lync 2010. My script will extract 2013 data,
convert it to 2010, query for users who are set to "Hide My Picture" and then export any guilty users to an edited2010 XML. The script then converts this to 2013 Format .zip, and uploads the data for these users only. I chose to use Update-CSUserData
insted of Import-CSUserData as this avoids having to restart my Front End. I then use a scheduled task on my Front End server which runs this script every hour.
Please note: You can use this script, but I guarantee nothing about it's functionality, and I am not responsible for how you positively/negatively use it. You should always test things in a Lab Environment. Furthermore, this script was run on a relatively
smaller Enterprise system in which we are by default set to "Show My Picture" and already assigned as part of our user policy the ForceADPhoto attribute. This means that running the script is less intensive on my FE than say on a FE with 10,000 users
where none of the users were set to "Show My Picture". Please keep this in mind when planning to execute against your FE. You may want to edit my script and insert the -UserFilter or -WhatIf in the Export-CsUserData UpDate-CsUserData.
Anyways, I hope this solves the similar issue for many of you Lync 2013 administrators. Please feel free to share my work with others if it does, and also give this post some good feedback and/or mark my post as the answer to your problem.
Alas, here's the script (save it as a .ps1 , i.e. ForceShowMyPicture.ps1)
#Lync 2013 ForceShowMyPicture - Compiled by Octavio A. Serpa (Octavio-Admin on TechNet)
# Import Lync Module
Import-Module “C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1"
###Variables To Set
#This variable is a folder where files will be temporarily written
$folderPath = “C:\Lync2013Scripts\Export”
#This is the FQDN of the pool in which the users you want to target reside
$poolFQDN = “<lyncpool.domain.local>”
###Done
#Message Out
Write-Host -ForegroundColor YELLOW “CHECKING THAT TEMP EXPORT FOLDER PATH EXISTS"
If (-not (Test-Path "$folderPath" -pathType container))
"ERROR: Your Export Directory doesn't exist!"
Exit
Write-Host -ForegroundColor Green “TEMP EXPORT FOLDER DOES EXIST"
Write-Host -ForegroundColor YELLOW “PRE-CLEANING OLD EXPORT/IMPORT FILES"
If (Test-Path "$folderPath\Lync2013UserData.zip") { Remove-Item "$folderPath\Lync2013UserData.zip" }
If (Test-Path "$folderPath\Lync2010UserData.xml") { Remove-Item "$folderPath\Lync2010UserData.xml" }
If (Test-Path "$folderPath\Lync2010EditedUserData.xml") { Remove-Item "$folderPath\Lync2010EditedUserData.xml" }
If (Test-Path "$folderPath\Lync2013EditedUserData.zip") { Remove-Item "$folderPath\Lync2013EditedUserData.zip" }
Write-Host -ForegroundColor Green “PRE-CLEANING COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “EXPORTING LYNC 2013 POOL USER DATA”
Export-CsUserData -PoolFqdn $poolFQDN -FileName $folderPath\Lync2013UserData.zip
Write-Host -ForegroundColor Green “EXPORT COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “CONVERTING LYNC 2013 USER DATA TO 2010 FORMAT”
Convert-CsUserData -InputFile "$folderPath\Lync2013UserData.Zip" -OutputFile "$folderPath\Lync2010UserData.xml" -TargetVersion Lync2010
Write-Host -ForegroundColor Green “CONVERSION COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “CHECKING THAT FORMAT CONVERSION WAS SUCCESSFUL AND .XML EXISTS”
If (-not (Test-Path "$folderPath\Lync2010UserData.xml" -pathType leaf))
"ERROR: Verify that $folderPath is writable!"
Exit
Write-Host -ForegroundColor Green “CONVERSION COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “LOADING XML”
$d = [xml] (Get-Content "$folderPath\Lync2010UserData.xml")
Write-Host -ForegroundColor Green “XML LOADING COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “CORRECTING AD PHOTO SETTING”
$changes = 0
$lastProcessedUser = $null
foreach ($hr in $d.HomedResources.HomedResource)
$found = 0
foreach ($c in $hr.Containers.Container)
foreach ($p in $c.Publication)
If ($p.CategoryName -eq 'contactCard' -and $p.InstanceNum -eq 6 -and $p.Data.contactCard.displayADPhoto -eq 'false')
If ($hr.UserAtHost -ne $lastProcessedUser)
"$($hr.UserAtHost) reset"
$lastProcessedUser = $hr.UserAtHost
$p.Data.contactCard.displayADPhoto = 'true'
$p.Version = (([int] $p.Version) + 1).ToString()
$p.PrevPubTime = $p.LastPubTime
$p.LastPubTime = (Get-Date -Format s).ToString()
$found = 1
$changes++
If ($found -eq 0) { [Void]$d.HomedResources.RemoveChild($hr) }
Write-Host -ForegroundColor Green “AD PHOTO SETTING CORRECTIONS COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “Changes: $changes"
If ($changes -ne 0)
#Message Out
Write-Host -ForegroundColor YELLOW “RE-SAVING XML”
$d.Save("$folderPath\Lync2010EditedUserData.xml")
#Message Out
Write-Host -ForegroundColor YELLOW “CONVERTING LYNC 2010 .XML BACK TO 2013 .ZIP FORMAT"
Convert-CsUserData -InputFile "$folderPath\Lync2010EditedUserData.xml" -OutputFile "$folderPath\Lync2013EditedUserData.zip" -TargetVersion Current
#Message Out
Write-Host -ForegroundColor Green “CONVERSION BACK TO 2013 .ZIP FORMAT SUCCESSFUL"
#Message Out
Write-Host -ForegroundColor YELLOW “IMPORTING LYNC 2013 POOL DATA FOR CORRECTED USERS”
Update-CsUserData -FileName $folderPath\Lync2013EditedUserData.zip -Confirm:$false -Verbose
Write-Host -ForegroundColor Green “IMPORT COMPLETED SUCCESSFULLY"
Write-Host -ForegroundColor YELLOW “STARTING POST-IMPORT-CLEANUP OF EXPORT/IMPORT FILES"
If (Test-Path "$folderPath\Lync2013UserData.zip") { Remove-Item "$folderPath\Lync2013UserData.zip" }
If (Test-Path "$folderPath\Lync2010UserData.xml") { Remove-Item "$folderPath\Lync2010UserData.xml" }
If (Test-Path "$folderPath\Lync2010EditedUserData.xml") { Remove-Item "$folderPath\Lync2010EditedUserData.xml" }
If (Test-Path "$folderPath\Lync2013EditedUserData.zip") { Remove-Item "$folderPath\Lync2013EditedUserData.zip" }
Write-Host -ForegroundColor Green “POST-IMPORT-CLEANUP COMPLETED"
#Message Out
Write-Host -ForegroundColor Green “AD PHOTO SETTING SUCCESSFULLY UPDATED"When I try to run this I get the follow error. Any thoughts?
Update-CsUserData : Unable to cast COM object of type 'System.__ComObject' to interface type
'Microsoft.Rtc.Interop.User.ICsUserManagement'. This operation failed because the QueryInterface call on
the COM component for the interface with IID '{D5ADD966-BDC3-4A8F-BFE8-6A59A9F74CB2}' failed due to the
following error: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
At C:\Lync2013Scripts\ForceDisplayPhoto.ps1:113 char:1
+ Update-CsUserData -FileName $folderPath\Lync2013EditedUserData.zip -Confirm:$fal ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: ([email protected]:String) [Update-CsUserData], Invalid
CastException
+ FullyQualifiedErrorId : Microsoft.Rtc.Management.AD.Cmdlets.ImportOcsUserDataCmdlet -
FTPing .zip CPU patch files...
Hi
I have downloaded a .zip file for Oracle CPU Patch and wants to move it to UINX server. After connecting the UNIX server, beofre I say "put <filename>"...do I have to say "binary"?
Your answer will be highly appreciated.
Thanks & Regards
Ahmed.Hello,
Besides the previous answer, generally (if you click on the patch detail) you have the size of the zip file in bytes.
For instance:
Size 1.1G (1123325074 bytes) So, once you have sent the zip file on the Unix server, you can check if it's size is correct.
Hope this help.
Best regards,
Jean-Valentin -
Hi, could anyone please convert these four files from 5.1 to 2013?
Thanks in advance
Solved!
Go to Solution.
Attachments:
lv 5.1 to 2013.zip 90 KBMass compiled in 8.2.1, which you can open with 2013.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
lv 5.1 to 2013.zip 71 KB -
Sol9 12/03 OS full install + 9_Recommended patch problem
Installing Sol9 12/03 on a SunFire 280r then installing the most recent 9_Recommended cluster (04/01/2004), this is the output during installation of 9_Recommended;
Installing 113718-02...
Installation of 113718-02 failed. Return code 35.
Installing 113574-03...
Installation of 113574-03 failed. Return code 35.
Looking over SunSolve I see these packages have been withdrawn and backed out to a previous revisions.
Sol9 12/03 OS installs;
113718-03
113574-07
9_Recommended from 04/01/2004 tries to installl;
113718-02
113574-03
SunSolve shows as current;
113718-02
113574-03
Here is the uname -a;
# uname -a
SunOS hostname 5.9 Generic_112233-11 sun4u sparc SUNW,Sun-Fire-280R
How can I backout or down version an OS installed package ?Unjar your files and you might see the premissions are not set for the post or pre scripts. I am not sure if this is a feature or there for protection in forcing one to install the patches by had , if you down load the zip version the perm are probable set.
-
Hi friends,
As a part of BIAPPS-ODI configuration, @ the step of Applying FMW patches biappshiphome patches is getting failed like in the final patching report im getting error like
----------START OF PATCHING REPORT------------------
* BIAPPSSHIPHOME Patching Report ..........
Patch Failed: fsclite_rel7mlr2_16424872.zip
Patch Failed: BISHIPHOME_11_1_1_7_0_GENERIC_130409_1210_16492220.zip
Patch Failed: atglite_rel7mlr5A_database_16239380.zip
Patch Failed: atglite_rel7mlr5_16480022.zip
Patch Failed: fsmlitedb_rel7mlr2_16424869.zip
Patch Failed: fsmlite_rel7mlr2_16424870.zip
Patch Failed: BISERVER_11_1_1_7_0_WINDOWS_X64_130326_2045_4_16583998.zip
Patch Failed: BIFNDN_11_1_1_7_0_WINDOWS_X64_130322_1000_5_16462147.zip
Since only the above BIAPPSSHIPHOME patches is failing, but the remaining oracle common patching, ODI patching got succeeded. Im getting issue only with the above BIAPPSSHIPHOME patches.
When i tried to view the log file im getting the error like
Oracle Interim Patch Installer version 11.1.0.9.9
Copyright (c) 2012, Oracle Corporation. All rights reserved.
Oracle Home : C:\Middleware\Oracle_BI1
Central Inventory : C:\Program Files\Oracle\Inventory
from : n/a
OPatch version : 11.1.0.9.9
OUI version : 11.1.0.9.0
Log file location : C:\Middleware\Oracle_BI1\cfgtoollogs\opatch\opatch2013-10-06_10-40-30AM_1.log
OPatch detects the Middleware Home as "C:\Middleware"
Log file location: C:\Middleware\Oracle_BI1\cfgtoollogs\opatch\opatch2013-10-06_10-40-30AM_1.log\
OPatch failed with error code = 73
What could be the issue for the above problem and how it can be solved.
Thanks
Regards,
SaroHi guys,
The issue is been resolved, once after renaming the file patch_locked which is located in the path
C:\Middleware\Oracle_BI1\.patch_storage
Finally I got those biappshiphome patches applied successfully
----------START OF PATCHING REPORT------------------
* BIAPPSSHIPHOME Patching Report ..........
Patch Succeded: fsclite_rel7mlr2_16424872.zip
Patch Succeded: BISHIPHOME_11_1_1_7_0_GENERIC_130409_1210_16492220.zip
Patch Succeded: atglite_rel7mlr5A_database_16239380.zip
Patch Succeded: atglite_rel7mlr5_16480022.zip
Patch Succeded: fsmlitedb_rel7mlr2_16424869.zip
Patch Succeded: fsmlite_rel7mlr2_16424870.zip
Patch Succeded: BISERVER_11_1_1_7_0_WINDOWS_X64_130326_2045_4_16583998.zip
Patch Succeded: BIFNDN_11_1_1_7_0_WINDOWS_X64_130322_1000_5_16462147.zip
* Oracle Common Patching Report ..........
Patch skipped since its already applied: p16433147_111170_Generic.zip
Patch skipped since its already applied: p16080773_111170_Generic.zip
Patch skipped since its already applied: Webservices_Patch-3-PS6RC3_bug-1648778
.zip
Patch skipped since its already applied: p16433036_111170_Generic.zip
Patch skipped since its already applied: JDEVADF_REL7MLR10-RT_16525527.zip
Patch skipped since its already applied: WebCenter_BP1REL7RC3_16311963.zip
Patch skipped since its already applied: fmw_diagnostics_14757820_2.zip
Patch skipped since its already applied: SOACOMMON_REL7B8_16438735.zip
* SOA Patching Report ..........
Not applying SOA Patches since SOA Home (SOA_HOME) value is not specified
* ODI Patching Report ..........
Patch skipped since its already applied: p16629917_111170_Generic.zip
* Weblogic Patching Report ..........
----------END OF PATCHING REPORT------------------
This final patching report log file is also located at: C:\patches\final_patchig_report.log
Regards,
Saro -
Hi friends,
I am working on Note: 802875.1
Particularly:
Apply patch 6400501 (conditional)
If you are on a UNIX/Linux platform, apply the 10.1.0.5 version of patch 6400501 to the iAS 10.1.2 Applications tier Oracle home.
Note: For Linux x86-64 environments, download the Linux 32-bit version of the patch as the Applications tier Oracle home is 32-bit. I download the patch (11.1.0.6.0) and read the README instruction. What is says is:
# Bugs Fixed by this patch:
# 6400501 - APPSST11G;1203;NOT ABLE TO COMPILE FORMS LIBRARRY WITH 11G DB
# Patch Installation Instructions:
# To apply the patch, unzip the PSE container file:
# % unzip p6400501_11106_LINUX.zip
# Set your current directory to the directory where the patch
# is located:
# % cd <patch directory>
# Ensure that the directory containing the opatch script appears in
# your $PATH; then enter the following command:
# % opatch apply
# Patch Special Instructions:
# Make sure all instances running under the ORACLE_HOME being patched
# are cleanly shutdown before installing this patch. Also ensure that
# the tool used to terminate the instance(s) has exited cleanly.
# Please relink the proc precompiler if it is installed on your system.
# cd $ORACLE_HOME/precomp/lib
# make -f ins_precomp.mk proc
# If the Oracle inventory is not setup correctly this utility will
# fail. To check accessibility to the inventory you can use the
# command
# % opatch lsinventory
# If you have any problems installing this PSE or are not sure
# about inventory setup please call Oracle support.The patch seems to be a database patch, and why is the instruction above said:
If you are on a UNIX/Linux platform, apply the 10.1.0.5 version of patch 6400501 to the iAS 10.1.2 Applications tier Oracle home. Why application teir?
Sooo confusing.
Thanks a lot,
Ms KHi,
How can I run the opatch without touching the setup of the Oracle Applications?
I believe Oracle Apps is already pre-set and Im afriad to alter the existing setup as i might mess it up.
[appldev@apps2 OPatch]$ ./opatch lsinventory
Oracle Interim Patch Installer version 1.0.0.0.58
Copyright (c) 2007 Oracle Corporation. All Rights Reserved..
We recommend you refer to the OPatch documentation under
OPatch/docs for usage reference. We also recommend using
the latest OPatch version. For the latest OPatch version
and other support related issues, please refer to document
293369.1 which is viewable from metalink.oracle.com
Cannot open the file: /etc/oraInst.loc
Please use -invPtrLoc option and specify the correct file for OPatch to look for central inventory.
ERROR: OPatch failed because of Inventory problem.How do I setup opatch please....
Thanks
Maybe you are looking for
-
How to create a PDF form with multiple approvals?
Hello , I am trying to add approvals to a pdf I created . I am trying to add approvals such that once the form is filled up by the user and emailed to the concerned person (admin) , they approve the form , this action inturn sends the pdf to the next
-
How can I download FaceTime on iPhone ?
Want to use my iPhone 4 for FaceTime . How to download this application ? Thanks
-
i have a list, part of which are figures put in manually, others that are the result of a calculation. To sort that column, what I normally did in Excel was to export as txt file, then reimport, and then do the recalculation. What's the way to do it
-
UCS F port trunking and reserved VSAN confusion
We have an existing UCS infrastructre where all the FI's FC ports are connected to the MDS9513 as one to one connection ( no port channel or trunking) and the FI is working as "end host mode" . We are planning to move some crtical production applica
-
Question about Toshiba Bluetooth stack V.4
Hi We have a Fujitsu Siemens P7120 Laptop which requires the Toshiba Bluetooth stack located at http://aps.toshiba-tro.de/Bluetooth/pages/download.php When we install this in silent mode, the installation takes place however the Bluetooth does not in