Collection Server Initialization Failure

One of my collection servers will not initialize. The WinXP box was
replaced by a VMWare virtual WinXP machine and the ZAM 7.5 software was
installed on the new machine using the same name as the old server. I
installed the Task Server, Collection Server and the Collection client.
All of the services start and there are no errors in the event logs. The
manager shows the Task Server as running but the Collection server as
stopped. When I start the Collection server I get the errors shown
below. This is one of many Collection/Task Servers that I have setup
including some that have been replaced by virtual machines as this one
has been. All other Collection/Task Servers are running without error.
I'm willing to remove it from ZAM and re-install and have tried that
once to no avail. Any help is appreciated.
MSSQL2005
ZAM 7.5 IR13
Management Server Windows 2003
Collection/Task Servers WinXP
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Bucket size: 200
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Process Controller Initialized
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Resetting all Workstations to Disconnected
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Default Option Set (COptset) may have been updated
{67D90F66-44B1-40B4-B99E-47AC4AAC9D61}
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Process Controller Running
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Client cleanup. 0 entries.
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Default Option Set (COptset) may have been updated
{695CA4D0-CF4B-47C2-83B3-07461265CB06}
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Default Option Set (COptset) may have been updated
{56547EAC-3A97-4BFE-8648-CA68C8227574}
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Updating cache file TSUsage32.exe as
..\Cache\EXEDir\Client\Win32\TSUsage32.exe.
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
Filestore checksum failure
Filename: .\Cache\EXEDir\Client\Win32\TSUsage32.exe, Chksum
calculated: 1, errno: 0
Catalog (size: 446464, chksum: 48497451), File (size: 446464, chksum:
48597282)
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
Unable to retrieve file TSUsage32.exe or write to
..\Cache\EXEDir\Client\Win32\TSUsage32.exe
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
Application Object Error at 12/2/2008 10:05:48 AM on BMMSUS1 by BMMSUS1
File Store Validation Failed.
[2.4.1216] This application was unable to access the file due to a
checksum failure. Source filename = TSUsage32.exe.
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Updating cache file tscclient as .\Cache\EXEDir\Client\Linux\tscclient.
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
Filestore checksum failure
Filename: .\Cache\EXEDir\Client\Linux\tscclient, Chksum calculated:
1, errno: 0
Catalog (size: 556853, chksum: 46150589), File (size: 557419, chksum:
46259996)
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
Unable to retrieve file tscclient or write to
..\Cache\EXEDir\Client\Linux\tscclient
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
Application Object Error at 12/2/2008 10:05:48 AM on BMMSUS1 by BMMSUS1
File Store Validation Failed.
[2.4.1216] This application was unable to access the file due to a
checksum failure. Source filename = tscclient.
</EVENT>
<EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
Updating cache file colosx as .\Cache\EXEDir\Client\OSX\colosx.
</EVENT>
<EVENT AT="12/2/2008 10:05:49 AM" SEVERITY="Severe">
Filestore checksum failure
Filename: .\Cache\EXEDir\Client\OSX\colosx, Chksum calculated: 1,
errno: 0
Catalog (size: 1546124, chksum: 114527802), File (size: 1497396,
chksum: 111016250)
</EVENT>
<EVENT AT="12/2/2008 10:05:49 AM" SEVERITY="Severe">
Unable to retrieve file colosx or write to .\Cache\EXEDir\Client\OSX\colosx
</EVENT>
<EVENT AT="12/2/2008 10:05:49 AM" SEVERITY="Severe">
Application Object Error at 12/2/2008 10:05:49 AM on BMMSUS1 by BMMSUS1
File Store Validation Failed.
[2.4.1216] This application was unable to access the file due to a
checksum failure. Source filename = colosx.
</EVENT>
<EVENT AT="12/2/2008 10:05:49 AM" SEVERITY="Info">
Updating cache file UMxlator.exe as
..\Cache\EXEDir\Client\Win32\UMxlator.exe.
</EVENT>
<EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
Filestore checksum failure
Filename: .\Cache\EXEDir\Client\Win32\UMxlator.exe, Chksum
calculated: 1, errno: 0
Catalog (size: 1249280, chksum: 129525058), File (size: 1249280,
chksum: 129500295)
</EVENT>
<EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
Unable to retrieve file UMxlator.exe or write to
..\Cache\EXEDir\Client\Win32\UMxlator.exe
</EVENT>
<EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
Application Object Error at 12/2/2008 10:05:50 AM on BMMSUS1 by BMMSUS1
File Store Validation Failed.
[2.4.1216] This application was unable to access the file due to a
checksum failure. Source filename = UMxlator.exe.
</EVENT>
<EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Info">
Updating cache file siupd as .\Cache\EXEDir\SysinfoUpg\Linux\siupd.
</EVENT>
<EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
Filestore checksum failure
Filename: .\Cache\EXEDir\SysinfoUpg\Linux\siupd, Chksum calculated:
1, errno: 0
Catalog (size: 7776, chksum: 613014), File (size: 7642, chksum: 602893)
</EVENT>
<EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
Unable to retrieve file siupd or write to
..\Cache\EXEDir\SysinfoUpg\Linux\siupd
</EVENT>
<EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
Application Object Error at 12/2/2008 10:05:50 AM on BMMSUS1 by BMMSUS1
File Store Validation Failed.
[2.4.1216] This application was unable to access the file due to a
checksum failure. Source filename = siupd.
</EVENT>
<EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Info">
Updating cache file Colw32.exe as .\Cache\EXEDir\Client\Win32\Colw32.exe.
</EVENT>
<EVENT AT="12/2/2008 10:05:54 AM" SEVERITY="Severe">
Filestore checksum failure
Filename: .\Cache\EXEDir\Client\Win32\Colw32.exe, Chksum calculated:
1, errno: 0
Catalog (size: 2285840, chksum: 230582079), File (size: 2371856,
chksum: 255767264)
</EVENT>
<EVENT AT="12/2/2008 10:05:54 AM" SEVERITY="Severe">
Unable to retrieve file Colw32.exe or write to
..\Cache\EXEDir\Client\Win32\Colw32.exe
</EVENT>
<EVENT AT="12/2/2008 10:05:54 AM" SEVERITY="Severe">
Application Object Error at 12/2/2008 10:05:54 AM on BMMSUS1 by BMMSUS1
File Store Validation Failed.
[2.4.1216] This application was unable to access the file due to a
checksum failure. Source filename = Colw32.exe.
</EVENT>
<EVENT AT="12/2/2008 10:05:55 AM" SEVERITY="Severe">
Collection Server Error at 12/2/2008 10:05:55 AM on BMMSUS1 by BMMSUS1
Collection Server Initialization Failure
[2.6.4] The Collection Server failed to initialize.
Application Object Error at 12/2/2008 10:05:54 AM on BMMSUS1 by BMMSUS1
File Store Validation Failed.
[2.4.1216] This application was unable to access the file due to a
checksum failure. Source filename = Colw32.exe.
</EVENT>
<EVENT AT="12/2/2008 10:05:59 AM" SEVERITY="Info">
The Process Controller has terminated.
</EVENT>
<EVENT AT="12/2/2008 10:06:16 AM" SEVERITY="Info">
*** bmmsus1 *** One-minute Marker ***
</EVENT>

I tried copying the bin files from another server (again) and this time
it worked. I only wish I knew what I did different.
> One of my collection servers will not initialize. The WinXP box was
> replaced by a VMWare virtual WinXP machine and the ZAM 7.5 software was
> installed on the new machine using the same name as the old server. I
> installed the Task Server, Collection Server and the Collection client.
> All of the services start and there are no errors in the event logs. The
> manager shows the Task Server as running but the Collection server as
> stopped. When I start the Collection server I get the errors shown
> below. This is one of many Collection/Task Servers that I have setup
> including some that have been replaced by virtual machines as this one
> has been. All other Collection/Task Servers are running without error.
> I'm willing to remove it from ZAM and re-install and have tried that
> once to no avail. Any help is appreciated.
>
>
> MSSQL2005
> ZAM 7.5 IR13
> Management Server Windows 2003
> Collection/Task Servers WinXP
>
>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Bucket size: 200
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Process Controller Initialized
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Resetting all Workstations to Disconnected
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Default Option Set (COptset) may have been updated
> {67D90F66-44B1-40B4-B99E-47AC4AAC9D61}
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Process Controller Running
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Client cleanup. 0 entries.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Default Option Set (COptset) may have been updated
> {695CA4D0-CF4B-47C2-83B3-07461265CB06}
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Default Option Set (COptset) may have been updated
> {56547EAC-3A97-4BFE-8648-CA68C8227574}
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Updating cache file TSUsage32.exe as
> .\Cache\EXEDir\Client\Win32\TSUsage32.exe.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
> Filestore checksum failure
>
> Filename: .\Cache\EXEDir\Client\Win32\TSUsage32.exe, Chksum
> calculated: 1, errno: 0
>
> Catalog (size: 446464, chksum: 48497451), File (size: 446464, chksum:
> 48597282)
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
> Unable to retrieve file TSUsage32.exe or write to
> .\Cache\EXEDir\Client\Win32\TSUsage32.exe
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
> Application Object Error at 12/2/2008 10:05:48 AM on BMMSUS1 by BMMSUS1
> File Store Validation Failed.
> [2.4.1216] This application was unable to access the file due to a
> checksum failure. Source filename = TSUsage32.exe.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Updating cache file tscclient as .\Cache\EXEDir\Client\Linux\tscclient.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
> Filestore checksum failure
>
> Filename: .\Cache\EXEDir\Client\Linux\tscclient, Chksum calculated: 1,
> errno: 0
>
> Catalog (size: 556853, chksum: 46150589), File (size: 557419, chksum:
> 46259996)
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
> Unable to retrieve file tscclient or write to
> .\Cache\EXEDir\Client\Linux\tscclient
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Severe">
> Application Object Error at 12/2/2008 10:05:48 AM on BMMSUS1 by BMMSUS1
> File Store Validation Failed.
> [2.4.1216] This application was unable to access the file due to a
> checksum failure. Source filename = tscclient.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:48 AM" SEVERITY="Info">
> Updating cache file colosx as .\Cache\EXEDir\Client\OSX\colosx.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:49 AM" SEVERITY="Severe">
> Filestore checksum failure
>
> Filename: .\Cache\EXEDir\Client\OSX\colosx, Chksum calculated: 1,
> errno: 0
>
> Catalog (size: 1546124, chksum: 114527802), File (size: 1497396,
> chksum: 111016250)
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:49 AM" SEVERITY="Severe">
> Unable to retrieve file colosx or write to .\Cache\EXEDir\Client\OSX\colosx
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:49 AM" SEVERITY="Severe">
> Application Object Error at 12/2/2008 10:05:49 AM on BMMSUS1 by BMMSUS1
> File Store Validation Failed.
> [2.4.1216] This application was unable to access the file due to a
> checksum failure. Source filename = colosx.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:49 AM" SEVERITY="Info">
> Updating cache file UMxlator.exe as
> .\Cache\EXEDir\Client\Win32\UMxlator.exe.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
> Filestore checksum failure
>
> Filename: .\Cache\EXEDir\Client\Win32\UMxlator.exe, Chksum calculated:
> 1, errno: 0
>
> Catalog (size: 1249280, chksum: 129525058), File (size: 1249280,
> chksum: 129500295)
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
> Unable to retrieve file UMxlator.exe or write to
> .\Cache\EXEDir\Client\Win32\UMxlator.exe
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
> Application Object Error at 12/2/2008 10:05:50 AM on BMMSUS1 by BMMSUS1
> File Store Validation Failed.
> [2.4.1216] This application was unable to access the file due to a
> checksum failure. Source filename = UMxlator.exe.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Info">
> Updating cache file siupd as .\Cache\EXEDir\SysinfoUpg\Linux\siupd.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
> Filestore checksum failure
>
> Filename: .\Cache\EXEDir\SysinfoUpg\Linux\siupd, Chksum calculated: 1,
> errno: 0
>
> Catalog (size: 7776, chksum: 613014), File (size: 7642, chksum: 602893)
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
> Unable to retrieve file siupd or write to
> .\Cache\EXEDir\SysinfoUpg\Linux\siupd
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Severe">
> Application Object Error at 12/2/2008 10:05:50 AM on BMMSUS1 by BMMSUS1
> File Store Validation Failed.
> [2.4.1216] This application was unable to access the file due to a
> checksum failure. Source filename = siupd.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:50 AM" SEVERITY="Info">
> Updating cache file Colw32.exe as .\Cache\EXEDir\Client\Win32\Colw32.exe.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:54 AM" SEVERITY="Severe">
> Filestore checksum failure
>
> Filename: .\Cache\EXEDir\Client\Win32\Colw32.exe, Chksum calculated:
> 1, errno: 0
>
> Catalog (size: 2285840, chksum: 230582079), File (size: 2371856,
> chksum: 255767264)
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:54 AM" SEVERITY="Severe">
> Unable to retrieve file Colw32.exe or write to
> .\Cache\EXEDir\Client\Win32\Colw32.exe
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:54 AM" SEVERITY="Severe">
> Application Object Error at 12/2/2008 10:05:54 AM on BMMSUS1 by BMMSUS1
> File Store Validation Failed.
> [2.4.1216] This application was unable to access the file due to a
> checksum failure. Source filename = Colw32.exe.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:55 AM" SEVERITY="Severe">
> Collection Server Error at 12/2/2008 10:05:55 AM on BMMSUS1 by BMMSUS1
> Collection Server Initialization Failure
> [2.6.4] The Collection Server failed to initialize.
>
> Application Object Error at 12/2/2008 10:05:54 AM on BMMSUS1 by BMMSUS1
> File Store Validation Failed.
> [2.4.1216] This application was unable to access the file due to a
> checksum failure. Source filename = Colw32.exe.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:05:59 AM" SEVERITY="Info">
> The Process Controller has terminated.
> </EVENT>
>
> <EVENT AT="12/2/2008 10:06:16 AM" SEVERITY="Info">
> *** bmmsus1 *** One-minute Marker ***
> </EVENT>

Similar Messages

  • Data Collection Set 'Server Activity' Failure Waiting on a kernel object(s) failed. Inner Error ------------------ The handle is invalid.

    All of the system data collection sets have been running for 6+ months without any issues, couple of weeks ago the 'Server Activity' collection set failed to restart after a planned maintenance server reboot.
    When attempting to manually start the collection set it indicates "success", but after refreshing the collection set it showing as stopped. Viewing the logs for the Data Collection (Server Activity) I am getting the message:
    Waiting on a kernel object(s) failed. Inner Error ------------------>
    The handle is invalid.
    After some research into this really unhelpful message I came across one posting where this error has been found to occur in SP1. We are running SP2 which include the fix so this shouldn't be the problem (ref http://connect.microsoft.com/SQLServer/feedback/details/585210/sql-server-2008-data-collection-execmasterpackage-timeout).
    To see more detail on the root cause of the error I enabled the additional tracing for data collection (http://blogs.msdn.com/b/sqlagent/archive/2011/07/13/enabling-additional-tracing-for-data-collector.aspx). This provided an exception stack which indicated
    that the issue was thrown to what looks like an existing file, referring to a location (e:\) which doesn't exist in our system.
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::    wmain _IN
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::    Command line: dcexec -c -s 2 -i "S160OLTP\OLTP" -m 0 -e 0x09C1635DD4C4C6478A145D679AFE718F_1_STOP
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::     Application::Init _IN
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::     Console code page (m_codePage): 437
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::      Application::ParseCommandLine _IN
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::      Application::ParseCommandLine _OUT:00000000
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::     Application::Init _OUT:00000000
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::     Application::Main _IN
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::     Started continuous mode collection on thread 12036
    DCEXEC!26d0!2f04!2012/11/28!11:17:25::      StartCachedCollectionWrapper _IN
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::      Waiting for collection to exit or stop event to be signaled
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::       StartCollection _IN
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::       StartCollection(iSetId = 2, iCollectionMode = 0, pwszInstanceName = S160OLTP\OLTP)
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::        CDataCollectorController::ExecuteCollectionSet _IN
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::        SQL Instance Name: OLTP
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::         CDataCollectorController::TryExecuteCollectionSetOnce _IN
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CDataCollectorController::Initialize _IN
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CDataCollectorController::Initialize _OUT:00000000
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CDataCollectorController::PopulateCollectorPackageParameters _IN
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CacheWindow=1, CacheDirectory='I:\MSSQL10.OLTP\MSSQL\dccache'
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CDataCollectorController::PopulateCollectorPackageParameters _OUT:00000000
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CDataCollectorController::PopulateSetPackageParameters _IN
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CollectionSetUID='{49268954-4FD4-4EB6-AA04-CD59D9BB5714}', ExecutionMode=0, IsSystem=-1, LoggingLevel=0, DaysUntilExpiration=14, ExitEventName=''
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CDataCollectorController::PopulateSetPackageParameters _OUT:00000000
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CreateControlEvents _IN
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e        ERROR: Win32 Error: GetLastError=183, retCode=0x4, function CDataCollectorController::CreateControlEvents, line 470, file e:\sql10_katmai_t\sql\mpu\shared\dc\runtime\controller\src\datacollectorcontroller.cpp
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e        ERROR: Failed to create kernel event for collection set: {49268954-4FD4-4EB6-AA04-CD59D9BB5714}. Inner Error ------------------>
    Cannot create a file when that file already exists.
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::          CreateControlEvents _OUT:00000000
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e       ERROR: DC_FAILED: function CDataCollectorController::TryExecuteCollectionSetOnce, line 350, file e:\sql10_katmai_t\sql\mpu\shared\dc\runtime\controller\src\datacollectorcontroller.cpp
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::         CDataCollectorController::TryExecuteCollectionSetOnce _OUT:0x000004
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::        Collection set execution failed, retrying in 5 seconds...
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::        Waiting for exit event or retry timer failed.
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e      ERROR: Win32 Error: GetLastError=6, retCode=0x4, function CDataCollectorController::ExecuteCollectionSet, line 278, file e:\sql10_katmai_t\sql\mpu\shared\dc\runtime\controller\src\datacollectorcontroller.cpp
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e      ERROR: Waiting on a kernel object(s) failed. Inner Error ------------------>
    The handle is invalid.
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::        CDataCollectorController::ExecuteCollectionSet _OUT:0x000004
    DataCollectorController!26d0!2f04!2012/11/28!11:17:25::       StartCollection _OUT:00000000
    DCEXEC!26d0!2f04!2012/11/28!11:17:25::      StartCachedCollectionWrapper _OUT:0x000004
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::     Collection thread returned (00000001)
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::     Waiting for collection thread to exit
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::     Collection thread signaled
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::     Application::Main _OUT
    DCEXEC!26d0!1b88!2012/11/28!11:17:25::    wmain _OUT:0x000004
    I am now stumped as I haven't found anyone else experiencing this issue.
    Any ideas, please help??

    Thanks for the pointer Eileen, problem solved.
    Can't believe I missed it, but after reading the last section on system hangs it occurred to me that I hadn't checked that all dcexec.exe processes were killed when I disable the data collection service.
    For anyone else experiencing this issue I identified the dcexec.exe processes using the following in cmd line:
    TASKLIST /SVC /FI "IMAGENAME EQ DCEXEC.EXE"
    On the default setup of the data collection there should be two dcexec.exe processes constantly running, one for "Server Activity" and another for "Query Statistics". On our server there were five running with the data collection disabled.
    After killing all of the processes and restarting the data collection problem solved!!
    Still need to understand why the processes didn't shut down cleanly when the server was restarted, but at least I know where to look now.

  • Repost: Failure trying to install Collection Server

    Hi Guys and Gals,
    Reposting from another forum in the hope that maybe somebody can point me in the right direction.
    I am rying to Install ZAM 7.5 Collection Server on a new server in our DMZ. This is to replace the existing collection server alread located in our DMZ.
    Have configured Oracle to talk to the Oracle DB on the ZAM Primary Management Server and it all works and TNSPing, etc confirms that there is connectivity.
    However when trying to install the Collection Server and pointing it to my Oracle DB instance (zamdb) ... I get this error message
    "Unknown Class Key - FATAL ! Persistence Layer detected an incompatibility between Objects and Schema!"
    I can't seem to find out what the cause is or how to resolve it. Google has not helped, neither has the Novell KB.
    I have a few suspects
    1) The Oracle instance installed on New Collection Server is 10.2.0.3 whereas the current collection server and ZAM Parent Server is 10.2.0.1. However the the collection server just uses oracle for ODBC since no database is configured/installed on both the original collection server and the new collection server.
    2) The Management Server has been upgraded to "7.50.0074 Interim Release 22". I think the issue here is that the installer that I am using is the from the original ZAM7.5 CD, but that since the primary server has been upgraded, something in the database doesn't match what the installer is looking for, hence the error.
    If I know what to change in the database to allow installation, that would get me on my way, and then I can change it back.
    Anybody have a clue as to what the error message means?
    Thanks in Advance..

    za,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • CMDTUX_CAT:1685: ERROR: Application initialization failure

     

    PeopleTools 8.19.04 requires an upgrade of tuxedo 6.5 patchlev ?? AND
    Jolt, patchlev ?? . There are also some HP patches if you're moving
    from tools 8.16 or below. We have successfully booted our BBLs on HP
    with tools 8.19.04. Exact patch levels are in the release notes. If
    problem continues, you might try PeopleSoft's Customer Connection.
    "Wayne W. Scott" <[email protected]> wrote in message news:<[email protected]>...
    Kevin:
    1) You will get better Tuxedo help in tuxedo.general.
    2) Okay, Tuxedo 6.5 on HP-UX 11; show the output from
    tail $TUXDIR/udataobj/patchlev
    3) Fix the NLS problems with: export NLSPATH=$TUXDIR/locale/C
    { it might be NLS_PATH; I often forget which }
    4) It seems you are using PeopleSoft. The problem might lie in the PeopleSoft to Tuxedo
    interface, whatever it is. I don't know where to direct you for that.
    Wayne Scott
    Kevin Medlin wrote:
    Hi all,
    Kinda new at the tuxedo stuff. Any help is appreciated.
    Attempting to boot ...
    Booting all admin and server processes in /software/pt819/hrms830/appserv/ps819tm1/PSTUXCFG
    INFO: TUXEDO(r) System Release 6.5
    INFO: Serial #: 101998665, Expiration NONE, Maxusers 1000000
    INFO: Licensed to: PeopleSoft
    Booting admin processes ...
    exec BBL -A :
    process id=12485 ... Started.
    Booting server processes ...
    exec PSAPPSRV -s@../psappsrv.lst -s@../psqcksrv.lst -sICQuery -sSqlQuery:SqlRequest
    -- -C psappsrv.cfg -D PT81 -S PSAPPSRV :
    CMDTUX_CAT:1685: ERROR: Application initialization failure
    tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error
    handler
    exec tmshutdown -y
    Shutting down all admin and server processes in /software/pt819/hrms830/appserv/ps819tm1/PSTUXCFG
    Shutting down server processes ...
    tmboot: CMDTUX_CAT:828: NLS:6: Message not found, catalog CMDTUX_CAT, set 1, num
    828
    ==============ERROR!================
    Boot attempt encountered errors!. Check the TUXEDO log for details.
    ==============ERROR!================
    Do you wish to see the error messages in the APPSVR.LOG file? (y/n) [n] :
    Shutting down admin processes ...
    Server Id = 0 Group Id = dbhrt2 Machine = dbhrt2: shutdown succeeded
    1 process stopped.
    y
    PSADMIN.12243 [04/21/03 15:00:57](0) Begin boot attempt on domain ps819tm1
    PSAPPSRV.12486 [04/21/03 15:01:06](0) PeopleTools Release 8.19.04 (HP/UX) starting
    PSAPPSRV.12486 [04/21/03 15:01:09](0) Open file cache UPM : use
    existing content
    ( 0) 0xc72c35ec DumpStack__18PSExceptionHandlerFi + 0xbc [software/pt819/hrms830/bin/libpssys.sl]
    ( 1) 0xc72c2e20 DumpStackEventHandler__18PSExceptionHandlerFPCUs + 0x48 [software/pt819/hrms830/bin/libpssys.sl]
    ( 2) 0xc72c4154 OnEvent__28CPSStackTraceRequestObserverCF8PS_EVENTPCvPv + 0x1c
    [software/pt819/hrms830/bin/libpssys.sl]
    ( 3) 0xc5dca158 Notify__18CPSEventDispatcherF8PS_EVENTPv + 0x60 [software/pt819/hrms830/bin/libpscmn.sl]
    ( 4) 0xc5dba5b8 PSAssert__FPCcT1Ui + 0x88 [software/pt819/hrms830/bin/libpscmn.sl]
    ( 5) 0xc743855c SamIsSrcDB + 0x8c [software/pt819/hrms830/bin/libpssys.sl]
    ( 6) 0xc7498d6c StmSignon + 0x87c [software/pt819/hrms830/bin/libpssys.sl]
    ( 7) 0xc14fcd10 SgnDBSignon__FP11SGN_DBPARMS + 0x88 [software/pt819/hrms830/bin/libpssgn.sl]
    ( 8) 0xc620db5c InitInstance__10CNetServerFiPPUs + 0x434 [software/pt819/hrms830/bin/libpsnetapi.sl]
    ( 9) 0x000595f8 InitInstance__10CAppServerFiPPUs + 0xb0 [software/pt819/hrms830/bin/PSAPPSRV]
    (10) 0x000591a4 tpsvrinit + 0xdc [software/pt819/hrms830/bin/PSAPPSRV]
    (11) 0xc5a09f84 _tmmain + 0x328  [software/pt819/tuxedo65/lib/libtux.sl]
    (12) 0xc59fcc80 _tmstartserver + 0x78  [software/pt819/tuxedo65/lib/libtux.sl]
    (13) 0x00037408 main + 0x44 [software/pt819/hrms830/bin/PSAPPSRV]
    (14) 0xc0143158 _start + 0xc0  [lib/libc.2]
    (15) 0x00036608 $START$ + 0x1a0 [software/pt819/hrms830/bin/PSAPPSRV]
    PSADMIN.12243 [04/21/03 15:01:54](0) End boot attempt on domain ps819tm1
    Do you wish to see the error messages in the TUXLOG.042103 file? (y/n) [n] :y
    150057.dbhrt2!PSADMIN.12243: Begin boot attempt on domain ps819tm1
    150101.dbhrt2!BBL.12485: 04212003: TUXEDO Version 6.5 HP-UX B.11.00 U 9000/898
    1623623321 unlimited-user license.
    150101.dbhrt2!BBL.12485: LIBTUX_CAT:262: INFO: Standard main starting
    150106.dbhrt2!PSAPPSRV.12486: 04212003: TUXEDO Version 6.5 HP-UX B.11.00 U 9000/898
    1623623321 unlimited-user license.
    150106.dbhrt2!PSAPPSRV.12486: LIBTUX_CAT:262: INFO: Standard main starting
    150154.dbhrt2!PSAPPSRV.12486: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
    150154.dbhrt2!tmboot.12481: 04212003: TUXEDO Version 6.5 HP-UX B.11.00 U 9000/898
    1623623321 unlimited-user license.
    150154.dbhrt2!tmboot.12481: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered;
    initiating user error handler
    150154.dbhrt2!tmboot.12481: NLS:6: Message not found, catalog CMDTUX_CAT, set
    1, num 724
    150154.dbhrt2!PSADMIN.12243: End boot attempt on domain ps819tm1

  • : ERROR: Application initialization failure

    The error report for the subect matter is some what vague on how to go about resolving an initialization failure. Can anyone give some pointers on what to check to try and isolate the problem.
    Regards

    Hi Todd,
    Here's a part of my ULOG file you were asking for. While booting Tuxedo all the other servers booted properly except Rating (6 instances) and Counter server gave following WARNING message.
    164949.DCDELSPST!Counter.356542.1.0: 06-09-2007: Tuxedo Version 8.1, 32-bit
    164949.DCDELSPST!Counter.356542.1.0: LIBTUX_CAT:262: INFO: Standard main starting
    164949.DCDELSPST!Counter.356542.1.0: Initializing Update counter Service ....
    164950.DCDELSPST!Counter.356542.1.0: LOGTYPE/S:
    164950.DCDELSPST!Counter.356542.1.0: ... Successfully initialized
    164950.DCDELSPST!Counter.356542.1.0: LIBTUX_CAT:6205: WARN: Server initialization function did not call tx_open() or tpopen() or this call failed
    164950.DCDELSPST!Rating.577820.1.0: 06-09-2007: Tuxedo Version 8.1, 32-bit
    164950.DCDELSPST!Rating.577820.1.0: LIBTUX_CAT:262: INFO: Standard main starting
    164950.DCDELSPST!Rating.577820.1.0: LOG: ERROR OFF, WARNING OFF, INFO OFF, DEBUG OFF
    164950.DCDELSPST!Rating.577820.1.0: LIBTUX_CAT:250: ERROR: tpsvrinit() failed
    164950.DCDELSPST!TMSYSEVT.487536.1.0: LIBTUX_CAT:1478: ERROR: .SysServerInit: Rating, group AMDL_APPS_GR, id 200 server initialization failure

  • Application initialization failure exception

    I am unable to start the JSL/JREPSVR processes.I am getting the following error when i give tmboot command.Also find the ubbConfig file that I am using.
    E:\bea\tuxedo9.1\samples\jolt\ToUpper>tmloadcf -y ubbToupper
    E:\bea\tuxedo9.1\samples\jolt\ToUpper>tmboot -y
    Booting all admin and server processes in E:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig
    INFO: BEA Tuxedo, Version 9.1, 32-bit, Patch Level (none)
    INFO: Serial #: 454493271161-2140437240256, Expiration 2007-02-15, Maxusers 100
    INFO: Licensed to: BEA Evaluation Customer
    Booting admin processes ...
    exec BBL -A :
    process id=2100 ... Started.
    Booting server processes ...
    exec DMADM -A :
    process id=1040 ... Started.
    exec JSL -- -n //GVC3ZA65:3052 -m10 -M50 -x10 :
    CMDTUX_CAT:1685: ERROR: Application initialization failure
    exec JREPSVR -A -- -W -P E:\bea\tuxedo\udataobj\jolt\repository\jrepository :
    CMDTUX_CAT:1685: ERROR: Application initialization failure
    exec WSL -A -e E:\bea\logs\stderr -o E:\bea\logs\stdout -- -n //GVC3ZA65:3051 -m 2 -M 10 -x 10 :
    process id=4040 ... Started.
    3 processes started.
    UBBConfig file
    #     (c) 2003 BEA Systems, Inc. All Rights Reserved.
    #ident     "@(#) samples/atmi/simpapp/ubbsimple     $Revision: 1.5 $"
    #Skeleton UBBCONFIG file for the TUXEDO Simple Application.
    #Replace the <bracketed> items with the appropriate values.
    *RESOURCES
    IPCKEY          54321
    #Example:
    #IPCKEY          123456
    DOMAINID     simpapp
    MASTER          GVC3ZA65
    MAXACCESSERS     20
    MAXSERVERS     10
    MAXSERVICES     10
    MODEL          SHM
    LDBAL          N
    *MACHINES
    DEFAULT:
              APPDIR="E:\bea\tuxedo9.1\bin"
              TUXCONFIG="E:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig"
              TUXDIR="E:\bea\tuxedo9.1"
              TLOGSIZE=100
              MAXWSCLIENTS=10
    #Example:
    #          APPDIR="/home/me/simpapp"
    #          TUXCONFIG="/home/me/simpapp/tuxconfig"
    #          TUXDIR="/usr/tuxedo"
    "GVC3ZA65"      LMID=GVC3ZA65
    #Example:
    #beatux          LMID=simple
    *GROUPS
    DEFAULT: LMID=GVC3ZA65 OPENINFO=NONE
    GROUP1
    LMID=GVC3ZA65     GRPNO=1     OPENINFO=NONE
    DMGROUP GRPNO=200
    GWGROUP2 GRPNO=220
    WSL_GRP GRPNO=800
    JSLGRP GRPNO=95
    JREPGRP GRPNO=94
    *SERVERS
    DEFAULT: GRACE=0 MAXGEN=10 RESTART=Y
    DMADM SRVGRP=DMGROUP SRVID=10
    #GWADM SRVGRP=GWGROUP2 SRVID=20
    #GWTDOMAIN SRVGRP=GWGROUP2 SRVID=30 RQADDR="gwtdom2"
    JSL SRVGRP=JSLGRP SRVID=31 CLOPT= " -- -n //GVC3ZA65:3052 -m10 -M50 -x10"
    JREPSVR SRVGRP=JREPGRP SRVID=98 RESTART=Y GRACE=0 CLOPT="-A -- -W -P E:\bea\tuxedo\udataobj\jolt\repository\jrepository"
    #JREPSVR SRVGRP=JREPGRP SRVID=97 RESTART=Y RQADDR=JREPQ REPLYQ=Y GRACE=0 CLOPT="-A -- -P E:\bea\tuxedo\udataobj\jolt\repository\jrepository"
    #JREPSVR SRVGRP=JREPGRP SRVID=96 RESTART=Y RQADDR=JREPQ REPLYQ=Y GRACE=0 CLOPT="-A -- -P E:\bea\tuxedo\udataobj\jolt\repository\jrepository"
    WSL SRVGRP=WSL_GRP SRVID=10
    CLOPT="-A -e E:\bea\logs\stderr -o E:\bea\logs\stdout -- -n //GVC3ZA65:3051 -m 2 -M 10 -x 10"
    #simpserv     SRVGRP=GROUP1 SRVID=1
    *SERVICES
    TOUPPER

    Ajay,
    Either you have forgotten to execute tmloadcf on your UBBCONFIG file or the
    value of the TUXCONFIG environment variable is set to something different
    than the value specified in the UBBCONFIG file.
    In tmboot, the TUXCONFIG environment variable is set to
    D:\bea\tuxedo9.1\samples\jot\ToUpper\tuxconfig , and tmboot cannot open this
    file.
    Ed
    <Ajay Kumandan> wrote in message news:[email protected]...
    Hi Todd,
    Now Iam able to start the JSL process but JREPSVR process
    is still not starting.I have the following snippet in my
    UBBConfig file.
    JSL SRVGRP=JSLGRP SRVID=31
    CLOPT= "-A -- -n //GVC3ZA03TESTING:3052 -m1 -M1 -x5"
    JREPSVR SRVGRP=JREPGRP SRVID=98 #RESTART=Y GRACE=0
    CLOPT="-A -- -W -P D:\bea\tuxedo\udataobj\jolt\repository\jrepository"
    #JREPSVR SRVGRP=JREPGRP SRVID=97 RESTART=Y RQADDR=JREPQ REPLYQ=Y GRACE=0
    CLOPT="-A -- -P D:\bea\tuxedo\udataobj\jolt\repository\jrepository"
    #JREPSVR SRVGRP=JREPGRP SRVID=96 RESTART=Y RQADDR=JREPQ REPLYQ=Y GRACE=0
    CLOPT="-A -- -P D:\bea\tuxedo\udataobj\jolt\repository\jrepository"
    Please find the ULOG file for reference
    122101.GVC3ZA03TESTING!slisten.exe.6776.7476.-2: 01-31-2007: Tuxedo Version
    9.1, 32-bit
    122101.GVC3ZA03TESTING!slisten.exe.6776.7476.-2: CMDTUX_CAT:4323: INFO:
    Listener Process Started
    125326.GVC3ZA03TESTING!tlisten.9820.6620.-2: 01-31-2007: Tuxedo Version 9.1,
    32-bit
    125326.GVC3ZA03TESTING!tlisten.9820.6620.-2: CMDTUX_CAT:1468: INFO: Listener
    Process Started
    125530.GVC3ZA03TESTING!tmboot.2444.6484.-2: 01-31-2007: Tuxedo Version 9.1,
    32-bit
    125530.GVC3ZA03TESTING!tmboot.2444.6484.-2: LIBTUX_CAT:603: ERROR: TUXCONFIG
    file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig does not exist
    125530.GVC3ZA03TESTING!tmboot.2444.6484.-2: LIBTUX_CAT:588: ERROR: Unable to
    open TUXCONFIG file
    125530.GVC3ZA03TESTING!tmboot.2444.6484.-2: FATAL: internal error:
    CMDTUX_CAT:754: ERROR: error processing configuration file
    125530.GVC3ZA03TESTING!tmboot.2444.6484.-2: FATAL: internal error:
    CMDTUX_CAT:1360: ERROR: configuration file not found
    125549.GVC3ZA03TESTING!tmboot.5388.6568.-2: 01-31-2007: Tuxedo Version 9.1,
    32-bit
    125549.GVC3ZA03TESTING!tmboot.5388.6568.-2: LIBTUX_CAT:603: ERROR: TUXCONFIG
    file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig does not exist
    125549.GVC3ZA03TESTING!tmboot.5388.6568.-2: LIBTUX_CAT:588: ERROR: Unable to
    open TUXCONFIG file
    125549.GVC3ZA03TESTING!tmboot.5388.6568.-2: FATAL: internal error:
    CMDTUX_CAT:754: ERROR: error processing configuration file
    125549.GVC3ZA03TESTING!tmboot.5388.6568.-2: FATAL: internal error:
    CMDTUX_CAT:1360: ERROR: configuration file not found
    131834.GVC3ZA03TESTING!tmboot.9840.5780.-2: 01-31-2007: Tuxedo Version 9.1,
    32-bit
    131834.GVC3ZA03TESTING!tmboot.9840.5780.-2: LIBTUX_CAT:603: ERROR: TUXCONFIG
    file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig does not exist
    131834.GVC3ZA03TESTING!tmboot.9840.5780.-2: LIBTUX_CAT:588: ERROR: Unable to
    open TUXCONFIG file
    131834.GVC3ZA03TESTING!tmboot.9840.5780.-2: FATAL: internal error:
    CMDTUX_CAT:754: ERROR: error processing configuration file
    131834.GVC3ZA03TESTING!tmboot.9840.5780.-2: FATAL: internal error:
    CMDTUX_CAT:1360: ERROR: configuration file not found
    132154.GVC3ZA03TESTING!tmboot.8724.10076.-2: 01-31-2007: Tuxedo Version 9.1,
    32-bit
    132154.GVC3ZA03TESTING!tmboot.8724.10076.-2: LIBTUX_CAT:603: ERROR:
    TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig does not
    exist
    132154.GVC3ZA03TESTING!tmboot.8724.10076.-2: LIBTUX_CAT:588: ERROR: Unable
    to open TUXCONFIG file
    132154.GVC3ZA03TESTING!tmboot.8724.10076.-2: FATAL: internal error:
    CMDTUX_CAT:754: ERROR: error processing configuration file
    132154.GVC3ZA03TESTING!tmboot.8724.10076.-2: FATAL: internal error:
    CMDTUX_CAT:1360: ERROR: configuration file not found
    132234.GVC3ZA03TESTING!tmboot.7108.8460.-2: 01-31-2007: Tuxedo Version 9.1,
    32-bit
    132234.GVC3ZA03TESTING!tmboot.7108.8460.-2: LIBTUX_CAT:603: ERROR: TUXCONFIG
    file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig does not exist
    132234.GVC3ZA03TESTING!tmboot.7108.8460.-2: LIBTUX_CAT:588: ERROR: Unable to
    open TUXCONFIG file
    132234.GVC3ZA03TESTING!tmboot.7108.8460.-2: FATAL: internal error:
    CMDTUX_CAT:754: ERROR: error processing configuration file
    132234.GVC3ZA03TESTING!tmboot.7108.8460.-2: FATAL: internal error:
    CMDTUX_CAT:1360: ERROR: configuration file not found
    132331.GVC3ZA03TESTING!tmboot.6160.2752.-2: 01-31-2007: Tuxedo Version 9.1,
    32-bit
    132331.GVC3ZA03TESTING!tmboot.6160.2752.-2: LIBTUX_CAT:603: ERROR: TUXCONFIG
    file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig does not exist
    132331.GVC3ZA03TESTING!tmboot.6160.2752.-2: LIBTUX_CAT:588: ERROR: Unable to
    open TUXCONFIG file
    132331.GVC3ZA03TESTING!tmboot.6160.2752.-2: FATAL: internal error:
    CMDTUX_CAT:754: ERROR: error processing configuration file
    132331.GVC3ZA03TESTING!tmboot.6160.2752.-2: FATAL: internal error:
    CMDTUX_CAT:1360: ERROR: configuration file not found
    152528.GVC3ZA03TESTING!tlisten.9820.6620.-2: CMDTUX_CAT:4209: INFO: Accepted
    request from //127.0.0.1:4553, seq # 1
    152655.GVC3ZA03TESTING!slisten.exe.6776.7476.-2: CMDTUX_CAT:4209: INFO:
    Accepted request from //10.226.65.102:4554, seq # 1
    153804.GVC3ZA03TESTING!slisten.exe.6776.7476.-2: CMDTUX_CAT:4209: INFO:
    Accepted request from //10.226.65.102:4580, seq # 2
    164453.GVC3ZA03TESTING!slisten.exe.6776.7476.-2: CMDTUX_CAT:4209: INFO:
    Accepted request from //10.226.65.102:4959, seq # 3
    164758.GVC3ZA03TESTING!jsh.4900.7868.-2: 01-31-2007: Tuxedo Version 9.1,
    32-bit
    164758.GVC3ZA03TESTING!jsh.4900.7868.-2: JOLT_CAT:1034: "ERROR: Failed to
    attach to shared memory for listener table, errno = 22"
    164831.GVC3ZA03TESTING!JSH.exe.5084.2480.-2: 01-31-2007: Tuxedo Version 9.1,
    32-bit
    164831.GVC3ZA03TESTING!JSH.exe.5084.2480.-2: JOLT_CAT:1034: "ERROR: Failed
    to attach to shared memory for listener table, errno = 22"
    Thanks and Regards,
    Ajay

  • Initialization failure - qe, caught signal 15

    Please could you help me ?
    The OMQ is not running any more.
    Now when I try to start the group, It has got a error 'signal 15'
    The OS is
    $ cat /etc/redhat-release
    Red Hat Enterprise Linux Server release 5.8 (Tikanga)
    LOG
    ************ dmqgcp (4985) 24-MAR-2014 10:32:33 ************
    gcp, group control process for group 126 is running
    ************ dmqqe (4987) 24-MAR-2014 10:32:33 ************
    qe, queuing engine is running
    ************ dmqgcp (4985) 24-MAR-2014 10:32:33 ************
    ipi, message queue operation failed
    ************ dmqgcp (4985) 24-MAR-2014 10:32:33 ************
    gcp, initialization failure
    ************ dmqqe (4987) 24-MAR-2014 10:32:33 ************
    qe, caught signal 15
    ************ dmqqe (4987) 24-MAR-2014 10:32:33 ************
    qe, queuing engine is exiting
    ************ dmqgcp (4985) 24-MAR-2014 10:32:33 ************
    gcp, group control process for group 126 is exiting
    TRACE
    Start DMQ Processes - start procedura data: (Mon Mar 24 10:32:33 BRT 2014) nodo: snelnxa113.internal.timbrasil.com.br
    %STARTUP-I-STARTING, dmqgcp -b 21 -g 126 -f /BECbmq/dmqdir/group/init/GROUP_126.init -n GROUP_126 -l /BECbmq/dmqdir/group/log/GROUP_126.log
    IPI 04985:IPI-initializing
    IPI 04985:IPI-using bus id 21,  group id 126
    IPI 04985:IPI-IPIattach_resources
    IPI 04985:IPI-attaching ipc queues
    IPI 04985:IPI-IPI_engine_write
    IPI 04985:IPI-number of bytes to write, 288 (120)
    IPI 04985:IPI-IPI_engine_write status
    IPI 04985:IPI-IPI_engine_read
    IPI 04985:IPI-number of bytes read, 288 (120)
    IPI 04985:IPI-IPI_engine_read status
    IPI 04985:QE -error status in response to process connect, -256 (FFFFFF00)
    IPI 04985:IPI-initialization failure, -43 (FFFFFFD5)

    Solved itself after kernel upgrade.

  • Error -32810 occurred at The FieldPoint server initialization failed. Possible causes: 1. Missing or corrupt configuration file; 2. Failed to create callbacks. : FP Open.vi

    I have two cFP-2120 RT controller. They both have NI-Serial RT2.5.6, DataSocket for LV RT4.2, NI-VISA 3.6, FP Drivers 5.1.0, FP VI Manager 3.1.0 LV RT 7.1.1 installed. But one same vi can run on one controller but not another.
    the error message got when it runs on another controller is "Error -32810 occurred at  The FieldPoint server initialization failed. Possible causes: 1. Missing or corrupt configuration file; 2. Failed to create callbacks. : FP Open.vi"
    I wonder by what it is caused?
    Thanks

    Hi Matthew,
    As mentioned previously, this KnowledgeBase article may be of some help. Also, if your code is being run on an embedded controller and then a network controller (not embedded), you will need to run the program differently. On the embedded controller, you should deploy your VI in a Project Explorer or programmatically (as described here.) However, you do not need to deploy the program to a network controller, but simply run the VI.
    I would also suggest creating a new .IAK file. Do you still see the same error? Also, double-check that the software installed on the controller matches the software installed on the host PC. If you have any file paths associated with one FieldPoint controller, ensure that you are changing them to match the second controller.
    Please keep us posted on your troubleshooting steps. Have a great day!
    Amanda Howard
    Americas Services and Support Recruiting Manager
    National Instruments

  • DBUA errors out after collecting server information

    Hi,
    We are in the process of upgrading Oracle Database from 9i to 11g on AIX 6.1. After installing the Oracle Software 11g (11.2.0.1) we try to run the DBUA but after showing the screen collecting server information a blank page appears (with no error code) after which the DBUA stops.
    Please any hints or any comments.
    Thanks.

    There are a few oracle notes which may help :
    DBUA Fails With a Screen Showing 'Null' [ID 1285052.1]
    Complete Checklist for Manual Upgrades to 11gR2 [ID 837570.1]
    11.2.0.1 Catupgrd.sql Hangs While Running Procedure POPULATE_DBID_AUDIT [ID 1062993.1]
    Best Regards
    mseberg
    Edited by: mseberg on Aug 10, 2011 8:02 AM

  • AS2 adapter failure: Initialization failure

    Hi experts,
    We had a message in RWB with this error:
    Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure), SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure)
    Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure), SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure)
    Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure), SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure): javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelper (initialization failure), SEEBURGER AS2: AS2 Adapter failure # com.seeburger.dt.security.smime.SMIMEHelp
    There weren't any errors from sxmb_moni, tried checking the com channels and they seem to be working fine.  Any help would be appreciated, thanks in advance.
    Regards,
    Donnie

    Hi Doonie
    Please check your system cache
    Please go through this blog
    Seeburger AS2 Adapter No binding found for: AS2, http://seeburger.com/xi
    Thanks
    Abhishek
    **Reward points if helpful**

  • SQL Server Setup failure.SQL Server Setup has encountered the following error: Method not found: 'Boolean Microsoft.SqlServer.Configuration.MsiExtension.MsiExtensionMetadata.get_IsSlipstreamOrPatch()'.. ----------

    Hi Team,
    Earlier i had SQL Server 2008 R2 on my Machine. For one work around i unistall SQL Server 2008 R2 and Trying to install SQL Server 2008 but i am not able to install with below error:
    TITLE: SQL Server Setup failure.
    SQL Server Setup has encountered the following error:
    Method not found: 'Boolean Microsoft.SqlServer.Configuration.MsiExtension.MsiExtensionMetadata.get_IsSlipstreamOrPatch()'..
    Thanks

    Hi Lydia,
    i have followed the above step and i am able to proceed further but while installation i am getting the below error consistently.
    TITLE: Microsoft SQL Server 2008 Setup
    The following error has occurred:
    Locating the SQL Server Browser service component failed with Windows Installer return code '2'. The component ID: '{2E86FD41-C179-456E-8E6A-5157ED427228}'.
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0x8510C01B%25400x31BA4472%25401222%254052007
    BUTTONS:
    &Retry
    Cancel
    2: 
    TITLE: Microsoft SQL Server 2008 Setup
    The following error has occurred:
    SQL Server Browser configuration for feature 'SQL_Browser_Redist_SqlBrowser_Cpu32' was cancelled by user after a previous installation failure. The last attempted step: Retrieving full path to the SQL Server Browser service executable using Windows Installer
    API for the SQL Server Browser component with ID '{2E86FD41-C179-456E-8E6A-5157ED427228}'..
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0x8510C01B%25400x31BA4472%25401222%254052007
    BUTTONS:
    OK
    After ignoring these step..installation getting complete but ..at the end i am not able to connect to server.
    Could you please help me on this.
    Thanks,
    Sumit

  • ZAM 7. Collection Server unable to be started in ZAM Manager

    Hey all,
    Having problems getting my Domain Collection Server running in our ZAM Enterprise environment.
    Domain server has been rebuilt and by itself appears to be working fine.
    I have it communicating back to the central ZAM server and both my "Collection Server" and "Task Server" services are up and running.
    However when I log into the ZAM Manager and look for the status of the 2 services, the "Collection Server" status is "stopped" and the "Task Servers" status is "Started"
    When I try and start the "Collection Server" nothing happens, the status stays steady as "Stopped". It doesn't appear to even try to start.
    From my domain server, if i restart the "Collection Server" service, i see the status in the ZAM Manager Console change from "Stopped" to "Unavailable" then back to "Stopped" again.
    Same process on the "Task Server" service results in the ZAM Manager status changing from "Started" to "Unavailable" back to "Started" again.
    Does anyone have any ideas as to where i should start to troubleshoot this?
    Server was working a year back when i first configured it, I left the company for ~1 year and have returned to the server in this broken state. No one knows what happened. I have since rebuilt the server and am still getting the same issues.
    I have confirmed with the Central IT Team that other Domain "Collection Servers" are functioning correctly.

    Check the accounts being used to run the collection server service and make sure they have admin rights on the collection server.

  • SQL Server Setup Failure 0x84B10001 (SQL 2012 SP2 and SQL 2014 Standard)

    I'm having a problem with SQL Server Setup. I had SQL Server 2012 R2 SP1 installed, and the SP2 installer would fail.
    I decided to just get SQL Server 2014. The setup (and system configuration checker) for that fails with the same error.
    SQL Server Setup failure
    SQL Server Setup has encountered the following error:
    '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    Error code 0x84B10001
    I found this and other posts about similar problems that point at MSDE being the cause.
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/bc9f4949-1b45-427c-aa2b-d2222488a13e/problems-installing-sql-server-2012error-code-0x84b10001?forum=sqlexpress
    I definitely had MSDE installed, but I went through the steps to manually remove it and rebooted with no luck.
    /* Don Reynolds */

    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.SqlBrowserExtension.sqlBrowserStopServicePrivateConfig.xsd' loaded
    into datastore path '/Datastore/ProductSettings/SqlBrowserStopService/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObjectDefault.xml' validated with schema 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPublicConfigObject.xsd' loaded into datastore path '/Datastore/ProductSettings/Sku/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObjectDefault.xml' validated with schema 'Microsoft.SqlServer.Configuration.SetupExtension.SkuPrivateConfigObject.xsd' loaded into datastore path '/Datastore/ProductSettings/Sku/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.Repl_ConfigExtension.ReplPrivateSettings.xsd' loaded into datastore path
    '/Datastore/ProductSettings/Repl/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPublicDefaultSettings.xsd' loaded into datastore
    path '/Datastore/ProductSettings/SqlRSSHP/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSSHPExtension.SqlRSSHPConfigPrivateDefaultSettings.xsd' loaded into
    datastore path '/Datastore/ProductSettings/SqlRSSHP/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPublicDefaultSettings.xsd' loaded into datastore path
    '/Datastore/ProductSettings/SqlRS/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSConfigPrivateDefaultSettings.xsd' loaded into datastore path
    '/Datastore/ProductSettings/SqlRS/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.RSExtension.SqlRSDBConfigPrivateDefaultSettings.xsd' loaded into datastore
    path '/Datastore/ProductSettings/SqlRS/DBPrivate'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPublicSettings.xsd'
    loaded into datastore path '/Datastore/ProductSettings/ManagementTools/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsPrivateSettings.xsd'
    loaded into datastore path '/Datastore/ProductSettings/ManagementTools/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPublicSettings.xsd'
    loaded into datastore path '/Datastore/ProductSettings/ManagementToolsAdvanced/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.ManagementToolsExtension.ManagementToolsAdvancedPrivateSettings.xsd'
    loaded into datastore path '/Datastore/ProductSettings/ManagementToolsAdvanced/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ControllerPrivateSettings.xsd' loaded
    into datastore path '/Datastore/ProductSettings/DReplayController/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateDefaultSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.DistributedReplayExtension.ClientPrivateSettings.xsd' loaded into
    datastore path '/Datastore/ProductSettings/DReplayClient/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterDisk/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterDiskPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterDisk/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterGroup/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterGroupPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterGroup/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterIPAddresses/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterIPAddressPublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterIPAddresses/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/FailOverClusterName/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.FailoverInstanceNamePublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/FailoverClusterName/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePrivateConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterNode/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xml' validated with schema 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodePublicConfig.xsd' loaded into datastore path '/Datastore/ProductSettings/ClusterNode/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xml' validated with schema 'Microsoft.SqlServer.Configuration.SlpExtension.SQLServerSCPPrivateSettings.xsd' loaded into datastore path '/Datastore/ProductSettings/SQLServerSCP/Private'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.Cluster.ClusterNodesStatusPublicConfig.xml' loaded into datastore path '/Datastore/ProductSettings/ClusterNodesStatus/Public'
    (01) 2014-07-02 10:52:57 Slp: Reading schema resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd'
    (01) 2014-07-02 10:52:57 Slp: Reading XML resource 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml'
    (01) 2014-07-02 10:52:57 Slp: Document 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettingsDefaults.xml' validated with schema 'Microsoft.SqlServer.Configuration.ASExtension.ASSPIInputSettings.xsd' loaded into datastore path '/Datastore/ProductSettings/ASSIP/Public'
    (01) 2014-07-02 10:52:57 Slp: Completed Action: LoadPackageDatastoreObjects, returned True
    (01) 2014-07-02 10:52:57 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:57 Slp: Running Action: InitializeInputSettingStore
    (01) 2014-07-02 10:52:57 Slp: Completed Action: InitializeInputSettingStore, returned True
    (01) 2014-07-02 10:52:57 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:57 Slp: Running Action: InitializeRoleService
    (01) 2014-07-02 10:52:57 Slp: Loading role: SPI_AS_NewFarm
    (01) 2014-07-02 10:52:58 Slp: Loading role: SPI_AS_ExistingFarm
    (01) 2014-07-02 10:52:58 Slp: Loading role: AllFeatures_WithDefaults
    (01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRoleService, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerCommandLineArguments
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: WORKFLOW
    (01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: TIMESTAMP
    (01) 2014-07-02 10:52:58 Slp: Value specified: 20140702_105236
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: LOGMARKER
    (01) 2014-07-02 10:52:58 Slp: Value specified:
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: MEDIASOURCE
    (01) 2014-07-02 10:52:58 Slp: Value specified: R:\
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: INSTALLMEDIAPATH
    (01) 2014-07-02 10:52:58 Slp: Value specified: R:\x64\setup\
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: ENU
    (01) 2014-07-02 10:52:58 Slp: Value specified: True
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: MEDIALAYOUT
    (01) 2014-07-02 10:52:58 Slp: Value specified: Full
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: ACTION
    (01) 2014-07-02 10:52:58 Slp: Value specified: RUNRULES
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: RULES
    (01) 2014-07-02 10:52:58 Slp: Value specified: SCCCheckRules
    (01) 2014-07-02 10:52:58 Slp: New setting source: CommandLine; previous setting source: Default
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerCommandLineArguments, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ProcessMediaChainerConfigFileArguments
    (01) 2014-07-02 10:52:58 Slp: Procssing media configuration file R:\x64\setup\..\DefaultSetup.ini.
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Setting: PID
    (01) 2014-07-02 10:52:58 Slp: New setting source: ConfigFile; previous setting source: NotSpecified
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessMediaChainerConfigFileArguments, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ProcessChainerConfigFileArguments
    (01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessChainerConfigFileArguments, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ProcessSlipstreamParameters
    (01) 2014-07-02 10:52:58 Slp: Completed Action: ProcessSlipstreamParameters, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Skipping Action: SetRoleAndUIModeForExpressMedia
    (01) 2014-07-02 10:52:58 Slp: Action is being skipped due to the following restrictions:
    (01) 2014-07-02 10:52:58 Slp: Condition "IsMediaExpress" did not pass as it returned false and true was expected.
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: InitializeRetryHandler
    (01) 2014-07-02 10:52:58 Slp: Completed Action: InitializeRetryHandler, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ExecuteBootstrapProcessInputSettings
    (01) 2014-07-02 10:52:58 Slp: Workflow to execute: 'BOOTSTRAPPROCESSINPUTSETTINGS'
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: StartSqmSession
    (01) 2014-07-02 10:52:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    (01) 2014-07-02 10:52:58 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
    (01) 2014-07-02 10:52:58 Slp: Sco: Attempting to get registry value CustomerFeedback
    (01) 2014-07-02 10:52:58 Slp: SQM Service: Sqm does not have active session.
    (01) 2014-07-02 10:52:58 Slp: SQM is opted-out by command line parameter /SQMREPORTING or registry key setting, SQM session is closed
    (01) 2014-07-02 10:52:58 Slp: Completed Action: StartSqmSession, returned True
    (01) 2014-07-02 10:52:58 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:58 Slp: Running Action: ValidateChainerSetting
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Compute new PID
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Read lcid 1033 from CultureInfo
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:58 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateChainerSetting, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureCommandLineArguments
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureCommandLineArguments, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: ProcessMediaFeatureConfigFileArguments
    (01) 2014-07-02 10:52:59 Slp: Procssing media configuration file R:\x64\setup\..\DefaultSetup.ini.
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessMediaFeatureConfigFileArguments, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: ProcessFeatureConfigFileArguments
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ProcessFeatureConfigFileArguments, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: ValidateSettingsAgainstScenario
    (01) 2014-07-02 10:52:59 Slp: Scenario: RunRules
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ValidateSettingsAgainstScenario, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: FinalCalculateSettings
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid is normalizing input pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid
    (01) 2014-07-02 10:52:59 Slp: -- PidInfoProvider : Use cached PID
    (01) 2014-07-02 10:52:59 Slp: Completed Action: FinalCalculateSettings, returned True
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapProcessInputSettings, returned True
    (01) 2014-07-02 10:52:59 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True
    (01) 2014-07-02 10:52:59 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:52:59 Slp: Running Action: RunRemoteDiscoveryAction
    (01) 2014-07-02 10:52:59 Slp: Running discovery on local machine
    (01) 2014-07-02 10:53:03 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction" threw an exception during execution.
    (01) 2014-07-02 10:53:03 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747. ---> Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException:
    '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747. ---> System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.Throw(Exception e)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseAttributes()
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseElement()
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlTextReaderImpl.ParseElementContent()
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
    (01) 2014-07-02 10:53:03 Slp:    at System.Xml.XmlDocument.Load(XmlReader reader)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:    --- End of inner exception stack trace ---
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2014-07-02 10:53:03 Slp:    --- End of inner exception stack trace ---
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    (01) 2014-07-02 10:53:03 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    (01) 2014-07-02 10:53:03 Slp: Received request to add the following file to Watson reporting: c:\temp\tmpFEEB.tmp
    (01) 2014-07-02 10:53:03 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2014-07-02 10:53:03 Slp: Inner exceptions are being indented
    (01) 2014-07-02 10:53:03 Slp:
    (01) 2014-07-02 10:53:03 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
    (01) 2014-07-02 10:53:03 Slp:     Message:
    (01) 2014-07-02 10:53:03 Slp:         '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    (01) 2014-07-02 10:53:03 Slp:     HResult : 0x84b10001
    (01) 2014-07-02 10:53:03 Slp:         FacilityCode : 1201 (4b1)
    (01) 2014-07-02 10:53:03 Slp:         ErrorCode : 1 (0001)
    (01) 2014-07-02 10:53:03 Slp:     Stack:
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(XmlDocument doc, XmlSchema schema, String namespacePrefix, String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
    (01) 2014-07-02 10:53:03 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2014-07-02 10:53:03 Slp:     Inner exception type: System.Xml.XmlException
    (01) 2014-07-02 10:53:03 Slp:         Message:
    (01) 2014-07-02 10:53:03 Slp:                 '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    (01) 2014-07-02 10:53:03 Slp:         HResult : 0x80131940
    (01) 2014-07-02 10:53:03 Slp:         Stack:
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.Throw(Exception e)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, BufferBuilder internalSubsetBuilder, Int32&
    charCount, EntityType& entityType)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseNumericCharRef(Boolean expand, BufferBuilder internalSubsetBuilder, EntityType& entityType)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseAttributes()
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseElement()
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlTextReaderImpl.ParseElementContent()
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
    (01) 2014-07-02 10:53:03 Slp:                 at System.Xml.XmlDocument.Load(XmlReader reader)
    (01) 2014-07-02 10:53:03 Slp:                 at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument(String xml, XmlSchema schema, String namespacePrefix,
    String namespaceUri, String rootPath)
    (01) 2014-07-02 10:53:08 Slp: Watson Bucket 2
     Original Parameter Values
    (01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server
    2014@RTM@
    (01) 2014-07-02 10:53:08 Slp: Parameter 1 : Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.LoadXmlDocument
    (01) 2014-07-02 10:53:08 Slp: Parameter 2 : System.Xml.XmlTextReaderImpl.Throw
    (01) 2014-07-02 10:53:08 Slp: Parameter 3 :
    Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException@1201@1
    (01) 2014-07-02 10:53:08 Slp: Parameter 4 :
    System.Xml.XmlException@-2146232000
    (01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
    (01) 2014-07-02 10:53:08 Slp:
     Final Parameter Values
    (01) 2014-07-02 10:53:08 Slp: Parameter 0 : SQL Server
    2014@RTM@
    (01) 2014-07-02 10:53:08 Slp: Parameter 1 : 0xDBE3EAAC
    (01) 2014-07-02 10:53:08 Slp: Parameter 2 : 0x066FCAFD
    (01) 2014-07-02 10:53:08 Slp: Parameter 3 :
    0xDF039760@1201@1
    (01) 2014-07-02 10:53:08 Slp: Parameter 4 : 0x5539C151
    (01) 2014-07-02 10:53:08 Slp: Parameter 5 : RunRemoteDiscoveryAction
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    (01) 2014-07-02 10:53:09 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140702_105236\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    (01) 2014-07-02 10:53:10 Slp: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 231747.
    (01) 2014-07-02 10:53:10 Slp: Watson bucket for exception based failure has been created
    (01) 2014-07-02 10:53:10 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    (01) 2014-07-02 10:53:10 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\120
    (01) 2014-07-02 10:53:10 Slp: Sco: Attempting to get registry value EnableErrorReporting
    (01) 2014-07-02 10:53:10 Slp: WER: Successfully read app consent from registry Software\Microsoft\Microsoft SQL Server\120\EnableErrorReporting=.
    (01) 2014-07-02 10:53:10 Slp: WER: Application level consent value '' was mapped to consent status 'WerConsentNotAsked'
    (01) 2014-07-02 10:53:12 Slp: WER: Result of the submission:: 'WerReportCancelled'
    (01) 2014-07-02 10:53:12 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
    (01) 2014-07-02 10:53:12 Slp:
    (01) 2014-07-02 10:53:12 Slp: ----------------------------------------------------------------------
    (01) 2014-07-02 10:53:12 Slp:
    (01) 2014-07-02 10:53:12 Slp: Error result: -2068774911
    (01) 2014-07-02 10:53:12 Slp: Result facility code: 1201
    (01) 2014-07-02 10:53:12 Slp: Result error code: 1
    (01) 2014-07-02 10:53:12 Slp: SQM Service: Sqm does not have active session.
    /* Don Reynolds */

  • Fileopen Initialization Failure(2)

    I receently updated both Acrobat 8 standard and Adobe Reader 9 up to their latest versions.  Whenever I open a PDF with either product I get the following message
    Fileopen Initialization Failure(2) you will not be able to open protected documents.  I am an admin on my system.  Anyone have an idea what is going on?  I searched the forums and did not find anything related to this issues.  Everything worked fine before patching.  OS is windows XP SP3  - no microsoft silverlight installed ( I found silverlight could casue much weirdness with Acrobat)

    Somehow a version of the fileopen api that was 5 years old was installed in reader directory and the acrobat standard dir.  All I did was path the programs and wham error started.  I went to the fileopen site and the promptly solved my issue.
    Here is their solution
    If  you aren’t concerned about opening documents using the plug-in you can remove it  by finding and deleting all instances of fOpen32.api; as I mentioned, that  plug-in was discontinued a long time ago (and our installer only dispenses the  current one).
    Good job Bernd point me in the right direction
    Thanks

  • License server general failure

    One workstation using the SAP B1 client generates a "license server general failure" message each time a user attempts to login to SAP B1, this is then followed by the dialogue box requesting the license server name and port number; I have the correct details in there.
    I have checked access the server from that workstation via port 30000 and I can successfully connect via that port; used Telnet ito the server. I still cant find the reason why this workstation cannot connect to the SAP server.
    Does anyone have an idea of how to fix this.
    Best Regards
    Albert.

    Hi Albatto,
    Have you tried to reinstall that client (both client app and diapi)?? also, clear the SBO temp files in the %temp% directory.
    You may also like to try to check the server Control Panel > Services to try to activate the sqlbrowser service. Then try to connect with that client once again.
    Hope it helps!
    Warmest Regards,
    Chinho

Maybe you are looking for