LCM tool generates error "There is no VMS app object present in CMS"

Hello,
I have an issue with the new LCM tool with XI 3.1.
I am able to logon successfully to the Version Management application as I am an administrator but my colleagues are not. At first I thought this was a security issue but my colleagues have all rights assigned for the LCM application. Initially the users are able to login, and the issue happens only after Version Management is selected from the drop down box. The full text of the error is:
java.lang.IllegalStateException: There is no VMS app object present in CMS.
Any help will be appreciated.
Thanks!
Jason

Hello Jason,
I'm assuming you gave your other users rights to the LCM in CMC->Applications.
I don't see the VMS (it holds information concerning Subversion and how the LCM connects to it) there, to affect rights over that application. Administrators appear to have access rights.
I'd recommend opening a SAP Incident to get clarification concerning rights to the VMS.
Sincerely,
Ted Ueda

Similar Messages

Sharepoint Provider hosted app installation error - There is no Workflow App Part registered

Hello,
I am getting below error when i run my share point app(Provider hosted) from visual studio 2013.It has a list workflow.
Error 1
Error occurred in deployment step 'Install app for SharePoint': There is no Workflow App Part registered.
0 0
SharePointApp
Thanks
Sobers

Hi,
According to the error message, your environment might not have the deployment group for the workflow registered.
You can register the deployment group using PowerShell with the code provided by Andrew in the link below and do the test again:
http://www.andrewconnell.com/blog/Workflow-Improvements-Changes-SP2013-March-PU-and-RTM-Developer-Tools#XgQAmUFIZm8a5cjm.99
Feel free to reply with the test result if the issue still exists.
Best regards
Patrick Liang
TechNet Community Support

SSIS 2008 package conversion to SSIS 2012 using SQL Data Tools generating warning There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWra

I am seeing the following warning is a SSIS C# script and receive a SSIS abort when I attempt to run the package.
The SSIS log indicates the package is failing at about this same step in the process.
I have also included the file SSQLDUMPER_ERRORLOG.log that SSIS generates when it aborts below.
My SSIS package has been set to 64-bit and I only have 64-bit SQL Server 2012 installed on the box.
I migrated the package using the latest version of Data Tools that came out around mid July 2014.
I edited all connection manager strings to point to 64-bit SQL Server and I run using the following command
I edited the run string to point to the new 64 bit DTExec and attempted to run.
C:\Program Files\Microsoft SQL Server\110\DTS\Binn\DTExec.exe" /Rep V /F PkgMigration.dtsx .........................
A significant amount of work does occur as reflected by the log steps prior to DTEXEC aborting but the log does just quit in mid sentence so not sure if it might have actually got a bit further.
Any help on understanding what is happening here would be most appreciated.
Warning               1              There was a mismatch between the processor
architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWrap, Version=11.0.0.0, Culture=Neutral, PublicKeyToken=89845dcd8080cc91", "x86". This mismatch may
cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a
processor architecture that matches the targeted processor architecture of your project.                C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
1605       5                sc_5756696d96034309a51afe69fed2eb44
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 6100
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00A8B770
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 6100
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00A8B770
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0007.mdmp
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(1CBC:1808) 08/14/14 10:36:47, ACTION,                DTExec.exe, Watson Invoke: No
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 10124
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0012B770
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 10124
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0012B770
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0008.mdmp
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(2724:2488) 08/14/14 10:43:09, ACTION,                DTExec.exe, Watson Invoke: No
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8716
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 0072B770
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8716
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0072B770
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0009.mdmp
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(2240:89C) 08/14/14 10:51:56, ACTION,                DTExec.exe, Watson Invoke: No
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8856
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 009AB770
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8856
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x009AB770
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0010.mdmp
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(7B8:1E68) 08/14/14 11:01:36, ACTION,                DTExec.exe, Watson Invoke: No
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 1292
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00BFB770
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 1292
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00BFB770
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0011.mdmp
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(229C:1CD8) 08/14/14 11:45:45, ACTION,                DTExec.exe, Watson Invoke: No
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 4220
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0019B770
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 4220
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0019B770
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0012.mdmp
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(2520:2624) 08/14/14 12:05:47, ACTION,                DTExec.exe, Watson Invoke: No
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 8408
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00000000003ECC18
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8408
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000003ECC18
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0001.mdmp
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(1B5C:20C0) 08/18/14 14:21:50, ACTION,                DTExec.exe, Watson Invoke: No

Hi GaryAMiller,
It seesm this is a know ssue. Please take a look at the following simialr issue at Microsoft Connect site:
MSB3270: Mismatch between the processor architecture:
https://connect.microsoft.com/VisualStudio/feedback/details/804933/msb3270-mismatch-between-the-processor-architecture-fakes-framework
If this issue still persists, I would suggest
opening a case with Microsoft Customer Support Services (CSS)(http://support.microsoft.com), so that a dedicated Support Professional can assist you in a more efficient manner.
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

Have published iweb site for five years with no problems and just opened a new site and get - 404: Page not found This error is generated when there was no web page with the name you specified at the web site.-is the problem with iweb or with hosting? T

I am sorry if thie is republished-My first time doing this and I am not sure what goes where and where to hear feedback.
Have published iweb site for five years with no problems and just opened a new site and get -
404: Page not found
This error is generated when there was no web page with the name you specified at the web site.-
Troubleshooting suggestions:
Ensure the page you are linking to exists in the correct folder.
Check your file name for case sensitivity . Index.htm is not the same as index.htm!
Temporarily disable any rewrite rules by renaming your .htaccess file if it exists
is the problem with
iweb or with hosting?
One Apple tech started to fix Iweb and had to end session and the next said problem with hosting at Network Solutions as it published
to local folder. NWS has checked sttting a few times-
Any help would be extremely appreciated as trying to fix this for about five weeks
Thanks VG
<Email Edited by Host>

It's a really bad idea to post your email address - it's an invitation to spam - and I've asked the Hosts to remove it. (Even though I've now noticed you mis-spelled it! - anyway, never post your address in a forum.)
You have a site here: http://virginiagordon.com/www.virginiagordon.com/WELCOME.html
If that's not the page you are having trouble with, what is that page's URL?

Bonjour keeps generating error event 100. It's there 128 times in a week! What does it mean?

Bonjour keeps generating error event 100 in windows 8.1 event viewer. It's there 128 times in a week! What does it mean?

Hey Michael,
That error could be cause by a conflict with the firewall on your computer. Take a look at the articles below to go over some troubleshooting as well as verifying that Bonjour was properly installed on your computer.
iTunes for Windows: Bonjour alert due to firewall, security, or proxy software
http://support.apple.com/en-us/HT203392
How to tell if Bonjour for Windows successfully installed
http://support.apple.com/en-us/HT201776
Take care,
-Norm G.

During receipt validation; the first step ie, adding the files generated by asn1c tool causes errors.. especially with the

During receipt validation; the first step ie, adding the files generated by asn1c tool causes errors.. especially with the #include statements
--No such directory or file..
Why this is happening??

I am adding one more thing..
Do we need to mention any linkage or frameworks or such while we are adding a .c file to
Cocoa Mac OS Project

O/R mapping tool generates bad descriptors for CMP2.0

The O/R tool has many problems with EJB-CMP 2.0.
It generates bad ejb-jar.xml (misses the <cmr-field-type> tag, has the same relationship field included in both the <entity> tag and the <relationships> tag).
The worst part is that is generates bad TopLink descriptors!
I have numerous indirect 1-1 bean-pojo (plain old java object). When I have the 'tool' generate the ejb-jar.xml and deployment xml it generates all these relationships incorrectly.
The O/R 'tool' forces you to use transparent indirection for CMP 2.0 relationships; transparent indirection does not allow you to specify 'use method accessing'. Fine. But when I go to deploy the compiled jar, I get ALL sorts of errors complaining that:
EXCEPTION [TOPLINK-1] (TopLink (WLS CMP) - 9.0.3 (Build 423)): oracle.toplink.exceptions.DescriptorException
EXCEPTION DESCRIPTION: The attribute [addressToDesc] is not declared as type ValueHolderInterface, but its mapping uses indirection.
MAPPING: oracle.toplink.mappings.OneToOneMapping[addressToDesc]
DESCRIPTOR: Descriptor(...
ARGH!! What the heck do I need to do to get this 'tool' to work? It won't LET me use valueholder in EJB-CMP2.0, but then it complains when when I don't!?!?!
Frustrated,
Andrew

(from toplink support)
Andrew,
Hi there. I've performed some research regarding
your question, and it appears that having an
"automatic" 1:1 indirect relationship between an EJB
2.0 Entity Bean and a dependent Java object is not
currently supported by TopLink. Examining the
documentation, this non-support unfortunately isn't
documented. I have entered a feature request on your
behalf so that we might be able to support it in a
future major version of TopLink.
However, there are a couple of alternatives which
you can use:
1) We do support non-indirect 1:1 relationships
between an EJB 2.0 Entity Bean and a dependent Java
object. You could disable indirection, and maybe
make the relationship a batch read relationship so
that your performance will not be degraded.
2) You can write a concrete getter and setter, and
provide an instance variable on the entity bean for
your dependent object of type ValueHolderInterface.
Provide the private getters and setters for set and
get -Holder. Map this normally using TopLink, and
make sure Indirection is specified in the Mapping
Workbench.
IMPORTANT: TopLink will handle the normal
persistence management for this relationship,
however you will need to handle the merging back of
this object yourself (you had to do this in EJB 1.1
in TopLink as well). Luckily there are good docs on
this, and it's covered in detail - look at the
TopLink for WebLogic documentation : Runtime
Considerations > Managing dependent objects.
Personally, I would implement solution 1) with batch
reading on the attribute, because the dependent
object shouldn't be that "big" (otherwise it would
be an entity bean). This is an easier solution,
however you should investigate 2) fully yourself.

Java.exe has generated errors and will be closed by windows

We are running win2000, with jre 1.4 and getting the following message at a particular point in our program:
<b>"java.exe has generated errors and will be closed by windows. You will need to restart the program. An error log is being created."</b>
I have 2 questions:
1) does anyone know what would cause this?
2) does anyone know where this log file is generated to?
many thanks - there are a few duke dollars in it.

We are getting same error with jdk1.6,
we can get drwtsn32.log file for user home/documents folder by running with following option. -XX:+ShowMessageBoxOnError
We got following log message:
Application exception occurred:
App: (pid=2288)
When: 2/5/2008 @ 18:20:44.700
Exception number: c0000005 (access violation)
----> System Information <----
Computer Name: MAX-20
User Name: Suresh.A
Number of Processors: 1
Processor Type: x86 Family 15 Model 2 Stepping 9
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 4
Current Type: Uniprocessor Free
Registered Organization: maxem
Registered Owner: max-20
has anybody found any solution / tools to identify this kind of issue?
Thanks
Nimalan

BusinessObjects Enterprise Lifecycle Manager (LCM) Tool - Feedback?

Lifecycle Manager Feedback Requested
Do you use the Life-Cycle Management (LCM) tool introduced with BusinessObjects Enterprise XI 3.1?
We're seeking feedback!
Any new features or enhancements you'd like to see in the tool, please go here:
[http://lcm.uservoice.com/]
Log on, add your ideas, and vote on the ideas already there!
Sincerely,
Ted Ueda

Hi
I am currently testing the BO LCM 3.1 and while it appears very easy to use especially for promotion, the Version Control Manager seems to be lacking in controls and a clear promotion path from dev to test to uat to prod.
We have set up 2 identical environments for UAT and PROD.
And using the Version Control part of LCM creating version control for a universe.
Logged into VM in UAT
We have selected a universe
Added it to VM
Made a change to the universe in Designer
Exported it
Then Checked it in
Can now see 2 versions in the history and the VMS Version. All good
I then click on swap system and log into PROD
The VM history is also there in PROD
I have a number of concerns and questions and can't seem to find the solution to them anywhere.
1. VM seems to be lacking a controlled process from all the environments. Basically we want to deploy following this path;
Dev - Test - UAT - PROD
There does not seem to be any controls or security which would stop you from GET VERSION from the DEV environment and putting that straight into PROD. Obviously we would not want that to happen.
We would only want to GET VERSION from UAT
Similarly for UAT We would only want to GET VERSION from TEST
And for TEST We would only want to GET VERSION from DEV.
Granted, we currently only have 2 identical environments.
But Is there controls that would stop you when in PROD from getting versions from any other system other than UAT?
Also is there any reason why no promotion is required when using VM.
This seems to negate the Promotion Function of the LCM
Any advise would be greatly appreciated with this.
Many thanks
Eilish

When installing itunes 10 uding windows xp I get the following error: "There is a problem with this Windows Installerpackage. A program run as part of the setup did not finish as expected. Contact your sipport personnel or package vendor." - any ideas?

When downloading itunes 10 in windows xp, I get the following error "There is a problem with this Windoes Installer package. Aprogram run as part of the setup did not finish as expected. Contact your support personnel or package vendor." - any ideas on how to proceed?

using MSICUU2.exe didn't help me. But, the new replacement app did:
http://support.microsoft.com/mats/Program_Install_and_Uninstall
I fixed my problem like this:
Here's the deal -
1. can you install itunes via the APPLE SOFTWARE updater?
I couldn't so I downloaded ITUNES and tried to install it that way.   Hence I got the same error hang as you. Nothing worked, (Multiple attempts at uninstall reinstall, stopping of Services, Reg cleaners etc..)
2. If answer is NO to #1 you must fixe the APPLE SOFTWARE UPDATE Program.
OK so I couldn't find a Download for this.   But: if you have WINRAR, open the ITUNES.EXE and extract the APPLESOFTWAREUPDATE.MSI file. Execute the APPLESOFTWAREUPDATE.MSI separately.   And you will not be able to install it and have a similar issue as per your Itunes install.   This of course leads you to believe that the Itunes.exe install is also installing all of these components including the applesoftwareupdate silently.   It must BOMB at that portion of the install and you are done.
3. Your goal now is to get the applesoftwareupdate installed.   How do you do this. Well - here is what I did.
a. downloaded and RUN a PC Installer FIX it tool from Microsoft. This is a replacement for the older MSI fixer they used to use.
http://support.microsoft.com/mats/Program_Install_and_Uninstall
b. It will list programs to attempt to fix.
choose AppleSoftwareUpdate.msi
c. Once it is done, then reinstall apple program updater using
AppleSoftwareUpdate.msi
Finally it should install since the Microsoft tool appraently fixed corrupted installation files in your registry for this application.
(Please note: that I also disabled any apple related services such as BONJOUR or IPOD DEvice RUN: services.msc to get there - although this man not be necesarry.)
Hence Launch this APPLE UPDATE SOFTWARE (Click the ICON in your Start menu) it should list ITUNES
select ITUNES from here and it will update.
KEY HERE is to ONLY UPDATE APPLE Stuff via the APPLE SOFTWARE UPDATE program. If that program is not working fix it. Then Bingo.
I am sorry to see folks having this problem for weeks.
APPLE,   Spread the word. PC's can get corruption in the registry on your product should the update be stopped or computer shut off during an update. etc...   Please improve your software updater program to check for invalid registry upon launching the app. This will prevent people thinking it is an APPLE issue. It appears to be a problem on your PC's registry settings for the APPLE Software update.
Bruno Ricci

NImax.exe has generated errors. You must restart the program, a log file is being created.

NImax.exe has generated errors. You must restart the program, a log file is
being created.
This error occurs just after bootup, no programs started except windows..
Running Windows 2000 latest version on a brand new computer.
(pent 4 3.0 ghz 500MB ram).
Can anyone help me with this problem? Happened after install Labview 7.0
express. Installed twice and same problem occured with both installs.
Labview 7.0 is the only thing installed right now. Also selected "Visual
Basic Support" install from driver cd's.
One other thing I just noticed. System info reports 2 processors and I
think I only have one.
TIA

Happy update.
After ignoring this problem for awhile and installing some NI DAQ boards,
this problem is not happening anymore.
Would urge NI to investigate further though. Messed me up for a couple of
days, and still don't know why it happened.
Much thanks to those who helped.
JJ
"JJF" wrote in message
news:qB6Hb.48702$VB2.90660@attbi_s51...
> One other point, I found out this is a message generated by drwtsn32. Can
> get rid of the error by unchecking "show visual feedback on errors" box,
but
> don't like that fix. Still need help.
>
> Thanks,
>
> JJ
>
> "JJF" wrote in message
> news:%JRGb.138921$8y1.419649@attbi_s52...
> > Hi Nirmal and all,
> >
> > Happy Holidays to you too, and thanks for the reply.
> >
> > Making progress. Did all the uninstalling and registry editing as you
> > suggested. Also, updated Win2K at Microsoft.com as suggested.
> > Re-installed with default settings of LV express 7.0. Now I only get
> the
> > error when I exit NImax.
> >
> > Also, my p2p home network is not that hot. Have it set up as a
workgroup.
> > Sometimes when I boot up I have file access between the two computers
and
> > sometimes windows explorer can't find the workgroup network path
(between
> > the two computers). Both computers can always access the internet
though.
> > Using a 4 port Linksys cable/dsl router on a cable modem. Using XP
home
> > edition on base computer (the one set up for the isp) and Win2K on the
> other
> > computer.
> >
> > Also, any idea where this log file is going? Thought it was part of the
> > event viewer but the errors in the event viewer don't seem to correspond
> to
> > the NImax.exe logging event now. There is a file in
> > "winnt\sytem32\config\software.log" that seems to change at about the
same
> > time but I can't access the file because it is in use by the system.
> >
> > Using NImax ver 3.02.3005. Do you know if I can download "NI
measurement
> > and automation explorer" and/or the driver cd's from NI.com? Maybe I
have
> a
> > flaky disk or something. I have a feeling it may also have to do with
the
> > "on again/off again" network neighborhood connection problem.
> >
> >
> > Thanks again,
> >
> > JJ
> >
> >
> >
> > "Nirmal Sharma" wrote in message
> > news:506500000005000000AE470100-1068850981000@exchange.ni.com...
> > > Hi,
> > > Happy cristmas & new year for you & ur brand new pc...
> > >
> > > How are you uninstalling & then installing LV in your pc ?
> > >
> > > I suggest to remove complete LV (Remove All option) from your
> > > computer. Once uninstallation is completed, go to windows registry -
> > > by windows start -> run -> regedit -> Enter
> > >
> > > Goto HKEY_LOCAL_MACHINE-> SOFTWARE -> National Instruments - Delete
> > > this folder (National Instruments folder)
> > >
> > > Remove any other foloder/file related to NI's software. Be very
> > > cautious while deleting files from windows registry bcoz wrong file
> > > deletion may hang your whole system.
> > >
> > > Restart your computer..hope it should bootup without any errors.
> > >
> > > Now as answered by Alexander, update windows.
> > >
> > > After updating, bootup your system. If it boots up without any error
> > > message, install LV with the typical (default installation).
> > >
> > > Hope this helps. Your feedbacks are welcome.
> > >
> > > Best Regards,
> > > Nirmal Sharma
> > > India
> >
> >
>
>

SQL Developer Tool Throws error on "/"

I am executing a script which is creating a view using sql developer. The script at the end has a "/" but before the / there is a blank line on top. and another view does not have a blank line but has a few spaces before "/" both the cases the sql developer throws compilation error.
there are other parts of the code which does have lot of balnk lines above eg in procedure & trgger (not views) and they compile perfect.
When i run the same script in sql plus or command line sql plus both have no issues. Its only the tool which is behaving like this.
Is this a known issue?

Example 1:
CREATE OR REPLACE VIEW x AS
SELECT abc from A where (abc=3) AND (xyz,6)
plz note two blank likes above /
Example 2:
CREATE OR REPLACE VIEW x AS
SELECT abc from A where (abc=3) AND (xyz,6)
plz note few spaces before the /
error says command not ended properly.
this works in sql plus

Generate error list with object detail

Dear All,
I have two way (multimaster ) Replication but due to some reason it generated many errors during replicate data so to resolve errors, I want to generate error list (Report) with object details instead viewing them one by one. please guide
Thanks

What do you mean with generate error list (Report) with object details ?
You can get all the errors from DEFERROR view.
There are columns DEFERRED_TRAN_ID and CALLNO.
You can join this columns with DEFCALL (DEFERRED_TRAN_ID and CALLNO).
Joining this two views will provide information about the objects and transaction type involved in the call.
DEFCALL.PACKAGENAME contains the reference to the table_name.
DEFCALL.PROCNAME contains information about the transaction type.
Example:
select e.deferred_tran_id,
       e.callno,
       e.origin_tran_db,
       c.packagename,
       c.procname
from deferror e, defcall c
where e.deferred_tran_id=c.deferred_tran_id
and e.callno=c.callno(below are the links to the 10gR2 docs containing information about DEFERROR and DEFCALL views. If your database is different version, than search http://tahiti.oracle.com for version specific documentation)
DEFERROR
http://download.oracle.com/docs/cd/B19306_01/server.102/b14227/rardeftranviews.htm#sthref2599
DEFCALL
http://download.oracle.com/docs/cd/B19306_01/server.102/b14227/rardeftranviews.htm#sthref2595
Cheers!
Message was edited by:
tekicora

LCM filesystem import error?

Hi,
I have exported the Planning application into a file system and the same file system again imported into same application in same environment as part of restoring process using shared servcies.
Here everything was successfully imported except few groups eventhough imported remaining groups.
I was getting the error as "*ERROR - error /Security/Access Permissions/Groups/GROUPNAME - The root element is required in a well-formed document*"
I couldnt gooogle it out. Please suggest any inputs to solve this issue.
I was on 11.1.1.3.
Thanks,

completely clueless about the issue^^^Totally my way of viewing all kinds of issues. :)
Change the filesystem.artifact.path=<epm_oracle_instance>/import_export to something like filesystem.artifact.path=C:\Hyperion\Oracle\ Migration and you need to store your backup at this location.^^^That is a super cool bit of information that I had zero knowledge of. I will definitely keep that one in my list of things to do at my next client as form folders and form names can blow past the length limit so easily.
I reread the OP's post, and I wonder (and again, just speculation) that is something in the group name that didn't play nice in XML. What I'm getting at is something akin to the known issue (maybe fixed now?) of parentheses in form names that blow LCM up. Maybe there's something in the name of the group, some special character or characters that doesn't translate well? It seems odd that most groups were okay but others failed. Maybe the SS group doesn't exist on the target to begin with? I don't believe that a Planning migration will create the target groups automatically.
Regards,
Cameron Lackpour

Trace Stack Error - Multiple step operation generated errors

When importing a mapping table into Financial Data Management, I received an error code 2147217887 multiple-step operation generated errors. Check each status value. I was exporting a mapping table from our development application into our production application, so I am not sure what caused this error message. Any ideas would be greatly appreciated. Thank you.

I solved this problem.
Oracle Provider for OLE DB 9.x is supporting Unicode.
But I didn't handle Unicode (DBTYPE_WSTR).
I added Unicode handling code in my source, then there was no error.

LCM tool generates error "There is no VMS app object present in CMS"

Similar Messages

Maybe you are looking for