Mismatch between the MD04 and VL10 tcodes.
Hello Gurus,
There is a Mismatch between the MD04 and VL10 tcodes. We can see an entry in the VL10 transaction which we couldn't find in the MD04. Please note that there is no dschedule line for that date in the LU aggrement. Kindly advice.
can be an error in in the delivery index.
run SDRQCR21 report?
And see if the record appears in MD04 or vanishes from VL10
Similar Messages
-
I have a SSRS installation, I have deployed my connections to, but they fail with title message. The drivers and ODBC on the box are setup and work fine with 32 bit ODBC conn manager.
When I run or configure my connections on the site, via the browser, I get errors connecting.
I tried to find which app pool http://server/ReportServer application used, but I am not finding that, so my first ?
How do I find in IIS what app pool SSRS application is using?
I have 2008 server, running SQL 2012 V.S. 2010 and I think I need to enable my app pool to use 32 bit, but cannot figure out which one it uses? I see default set to 32 bit = true, which I thought would be it.
Can I set my SSRS project to use x86, platform? Like I did with SSIS?
If so, how? SSRS and SQL 2012 somewhat new for me. Thanks
Developer MS Reporting ServicesHi DCady,
To manage a data source that connects to a 32-bit driver under 64-bit platform, we use C:\Windows\SysWOW64\odbcad32.exe. To manage a data source that connects to a 64-bit driver, we use C:\Windows\System32\odbcad32.exe.
Generally, if we use the 64-bit odbcad32.exe (C:\Windows\System32\odbcad32.exe) to configure or remove a DSN that connects to a 32-bit driver, for example, Driver do Microsoft Access (*.mdb), we will receive the following error message:
The specified DSN contains an architecture mismatch between the Driver and Application
To resolve this error, we need to use the 32-bit odbcad32.exe (C:\Windows\SysWOW64\odbacad32.exe) to configure or remove the DSN.
Besides, please make sure there are no DSN using the same name in both 64-bit and 32-bit ODBC Data Source Administrator.
Reference:
Managing Data Sources
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support -
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: NoHi 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 -
I’m facing a problem while implementing an application on azure I have a dll that is of x86 architecture and is referred
in my application. It is the core or base of my application. When I run that application locally it runs fine but when I try to publish that application to Azure from Visual studio 13. It shows an error that the dll and its dependencies are missing.
And it giving an error like :
Warning 1 There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "RsiDotNetDll",
"x86". This mismatch may cause runtime failuresHi Suresh,
Thanks for your posting!
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Best Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
There is a compatibility range mismatch between the Web server and database
HI,
Taken backup form production environment through TSM backup utility and restore same db on UAT environment by TSM Utility, after restore got below issue, past i had done many time but working fine this time
it’s not working. Production environment have SP2010 and sql server 2008 ,UAT have same thing also.
Server Error in '/' Application.
There is a
compatibility range mismatch between the Web server and database "Portal_Contain", and connections to the data have been blocked to due to this incompatibility. This can
happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and
build level to return to compatibility range.
Description: An unhandled exception occurred during the execution of the current
web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.SharePoint.Upgrade.SPUpgradeCompatibilityException:
There is a compatibility range mismatch between the Web server and database "Portal_Contain", and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within
the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the database must be upgraded to the same version and build level to return to compatibility range.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack
trace below.
Stack Trace:
[SPUpgradeCompatibilityException: There is a compatibility range mismatch between the Web server and database "Portal_Contain", and connections to the data have been
blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been upgraded to a higher level than the web server. The Web server and the
database must be upgraded to the same version and build level to return to compatibility range.]
Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.ValidateBackwardsCompatibility() +542
Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request) +63
Microsoft.SharePoint.SPWeb.InitializeSPRequest() +258
Microsoft.SharePoint.WebControls.SPControl.EnsureSPWebRequest(SPWeb web) +365
Microsoft.SharePoint.WebControls.SPControl.SPWebEnsureSPControl(HttpContext context) +520
Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.GetContextWeb(HttpContext context) +27
Microsoft.SharePoint.ApplicationRuntime.SPRequestModule.PostResolveRequestCacheHandler(Object oSender, EventArgs ea) +918
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +171
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| TwitterHi Bhavik,
UAT Portal_Contain DB version given below:
Version ID
Version
id
00000000-0000-0000-0000-000000000000
12.0.0.4518
1
00000000-0000-0000-0000-000000000000
12.0.0.6219
3
00000000-0000-0000-0000-000000000000
12.0.0.6327
4
00000000-0000-0000-0000-000000000000
12.0.0.6421
5
00000000-0000-0000-0000-000000000000
12.0.0.6510
6
00000000-0000-0000-0000-000000000000
12.0.0.6514
7
00000000-0000-0000-0000-000000000000
14.0.6123.5006
9
1A707EF5-45B2-4235-9327-021E5F9B8BB0
4.1.6.0
8
6333368D-85F0-4EF5-8241-5252B12B2E50
4.1.18.0
2
Production Version given below:
00000000-0000-0000-0000-000000000000
12.0.0.4518
00000000-0000-0000-0000-000000000000
12.0.0.6219
00000000-0000-0000-0000-000000000000
12.0.0.6327
00000000-0000-0000-0000-000000000000
12.0.0.6421
00000000-0000-0000-0000-000000000000
12.0.0.6510
00000000-0000-0000-0000-000000000000
12.0.0.6514
00000000-0000-0000-0000-000000000000
14.0.6123.5006
1A707EF5-45B2-4235-9327-021E5F9B8BB0
4.1.6.0
6333368D-85F0-4EF5-8241-5252B12B2E50
4.1.18.0
I have matched both are the exact same.
Run the below command on App server:
Upgrade-SPContentDatabase
cmdlet Upgrade-SPContentDatabase at command pipeline position 1
Supply values for the following parameters:
Identity: Portal_Contain
Confirm
Are you sure you want to perform this action?
Performing operation "Upgrade-SPContentDatabase" on Target "Portal_Contain".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is "Y"):y
WARNING: Database [SPContentDatabase Name=Portal_Contain] cannot be upgraded.
Kindly suggest
Hasan Jamal Siddiqui(MCTS,MCPD,ITIL@V3),Sharepoint and EPM Consultant,TCS
|
| Twitter -
There is a mismatch between order type and GL accountu201D.
Hello
Can any one help me to know why I am getting this error message.
Here I am giving the steps carried out.
Step1. Using transaction code: FB60 I have posted a vendor invoice to a Machinery account GL account against a internal order.
Step2. A down payment using transaction code FBA7. using a special indicator M to a bank account.
Step3. When I am trying to clear the open item (by selecting above both documents) for the vendor using transaction F-44 system is giving an error message u201CThere is a mismatch between order type and GL accountu201D. System is prompting to correct the down payment entry, where I dint use any Cost centre, internal order.
Checked the Internal order profile, AUC settlement profile etc and no able to find an error message.
Can any one explain me why this error is coming and what need to be check in order to rectify it.
Regards
RS.Hi It looks that the field status of the Order Type and GL Account field status is being mistmatching with each other. You can check the field status group given on GL Account and the fields status in Order Type.
-
Mismatch between the patch version
Version 2.18, next step, next issue. Got through the 'Do Setup' step on "9-Apply DBA CUP and related patches" with a bug workaround that was provided. Now went to the next step of 'Do Execute' and it is failing with the message below. I've done some inital searching and haven't found an answer. There was one note on MOS about a very similar issue but it was resolved in 2.16. Posting here whild I spend more time researching and trying to figure out the reason. I also reviewed my notes from when I did this upgrade manually and these mereged patches were not applied in preinstall mode as the message is saying has to be done. Any help would be appreicated. Thanks!.
patchit12.sh - is exiting with no actions. ie. Patch patchfile_ad17089s not applied.
There is a mismatch between the patch version specified and the release
version obtained from your Applications environment. In order to apply
Release 12 patches to previous Applications versions, the patch must be
applied in preinstall mode.This can be done by passing the appropriate
value to the preinstall parameter of eof_patch12.sh.
INFO: Not starting patch alert monitor, to start: Login Engineer, User Admin, Update Profile
Version in scripts/COMMON
# $Header: patchit12.sh 1.32 2009/09/15 16:00:00 vpickard $
Edited by: user649511 on Mar 2, 2011 2:24 PMYou can change following in patchit12.sh under ./eof/scripts/COMMON. Please change it back before executing any other steps.
From
Check_Release()
#Check if the releasenr is OK
if [ "${preinstall}" = "y" ];then
RELEASE=12
echo
echo "patchit12.sh is installing: $patch in preinstall=y mode."
else
REL=`Get_Release`
RELEASE=`echo $REL | awk '{print substr($1,1,2)}'`
echo
echo "Found release REL=$REL from fnd_product_groups."
fi
to
Check_Release()
#Check if the releasenr is OK
if [ "${preinstall}" = "y" ];then
RELEASE=12
echo
echo "patchit12.sh is installing: $patch in preinstall=y mode."
else
REL=`Get_Release`
#RELEASE=`echo $REL | awk '{print substr($1,1,2)}'`
RELEASE=12
echo
echo "Found release REL=$REL from fnd_product_groups."
fi -
We have a web role where we have hosted a WCF service.
We are facing the below exception intermittently on consuming the service.
Security processor was unable to find a security header in the message. This might be because the message is an unsecured fault or because there is a binding mismatch between the communicating parties. This
can occur if the service is configured for security and the client is not using security.
This is intermittent. Few calls fail , and the subsequent calls succeed without making any changes.
Please help in overcoming this abnormal behavior.
Thanks in advance !!
Best Regards ,
EswarHi Eswar,
As the error message mentioned, it may be a mismatch between the configuration on the client and the server.Try putting all your configuration in a binding configuration and then use the same binding configuration on the server and client. Since this issue
is more related with WCF, I suggest you move to WCF forum, it is appropriate and more experts will assist you.
Best Regards,
Jambor
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Microsoft Fakes MSB3270: There was a mismatch between the processor architecture
Hi,
I´m using Microsoft fakes in my test project and it shows this annoying message:
warning MSB3270: There was a mismatch between the processor architecture of
the project being built "MSIL" and the processor architecture of the reference
"ThirdPartyDll, Version=xxx, Culture=neutral, processorArchitectu
re=x86", "x86". This mismatch may cause runtime failures. Please consider chang
ing the targeted processor architecture of your project through the Configurati
on Manager so as to align the processor architectures between your project and
references, or take a dependency on references with a processor architecture th
at matches the targeted processor architecture of your project.
The fake has been created from a Project which references Microsoft.VisualStudio.Coverage.Analysis which has been compiled in x64 (I´ve had problems too with this assembly becuase I´m using it in a custom activity for a build definition, you can see
this post regarding that
http://social.msdn.microsoft.com/Forums/en-US/tfsprocess/thread/d4896ad3-aba1-4c36-8570-dcc55c41df95/).
I can use the following tag to hide the warnings during the project compilation but it doesn´t work for fakes:
<PropertyGroup>
<ResolveAssemblyWarnOrErrorOnTargetArchitectureMismatch>None</ResolveAssemblyWarnOrErrorOnTargetArchitectureMismatch>
</PropertyGroup>
https://connect.microsoft.com/VisualStudio/feedback/details/728995/new-vs2010-project-compiler-warning-since-installing-dotnet4-5-vs2011-beta
So, any ideas about how to solve this?
RegardsHi Chirstian,
Although the link is quite old I´m working with the update 1 of VS2012.
You can reproduce the warning very easily.
1. - Create a new class library project.
2. - Add a reference to Microsoft.VisualStudio.Coverage.Analysis.dll (not the one located in Program Files x86\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies) from your Build Server (located in your build machine -> Program Files\Microsoft
Team Foundation Server 11.0\Application Tier\TFSJobAgent\plugins. I ´ve put this assembly in my Versión Control path to custom assemblies).
3. - Compile the project. You´ll get the warning MSB3270 for the class library. You can solve this warning creating the following property group for the library project:
<propertyGroup>
<ResolveAssemblyWarnOrErrorOnTargetArchitectureMismatch>
None
</ResolveAssemblyWarnOrErrorOnTargetArchitectureMismatch>
</propertyGroup>
With this tag, the warning will disappear.
4. - Create a new Test Project. Add a reference to the same Coverage assembly as you did previously and you´ll get the same warning. Put the tag to solve it.
5. - In the test Project, add a reference to the class library project created previously. After that, add fakes assembly for this assembly. Right now, if you compile the Project you should get the warning.
Microsoft.QualityTools.Testing.Fakes.targets (62,5) : Warning MSB3270: There was a mismatch between the processor architecture...
I´m afraid I can´t send you a sample project. You can ask me whatever you want if you need help to reproduce it though.
Regards. -
PdfA1b - Subject Mismatch between Document Info and XMP metadata
As far as I can tell, when generating PdfA-1b files I am completely compliant with the spec. Yet when I try to preflight verify my output I get the following error: "Subject mismatch between Document Info and XMP metadata".
Here is my Document Info:
/Title (Title)
/Author (Author)
/Subject (Subject)
/Keywords (Key Words)
/Creator (Creator)
/Producer (Producer)
/CreationDate (D:00010101000000)
/ModDate (D:00010101000000)
Here is my XMP Stream:
Key Words
Producer
Title
Subject
Author
Creator
0001-01-01T00:00:00.0011111
0001-01-01T00:00:00.0022222
1
B
Am I missing something?
Subject
vs
/Subject (Subject)
It seems like it should be fine.
-RickYou have a disconnect with regard to how Document Info fields are to be mapped to XMP Dublin Core (dc) data fields:
- Document Info Subject -> dc:description
[nobody claims this is intuitive, but it is indeed specified reasonably well]]
The following is not required in your case, but for your info I include it anyway:
- Document Info Keywords -> dc:subject
Your best source for this is the actual PDF/A-1 standard (ISO 19005-1, can be purchased form www.iso.org).
A very good companion for such type of topics are the TechNotes from the PDF/A Competence Center (see www.pdfa.org), downloadable free of charge.
HTH.
Olaf Drümmer -
Architecture mismatch between ODBC driver and application
Hi,
I have Windows 2008 server R2 OS which is 64 bit OS. I have created an SQL Server ODBC connections for my CMC database. I am trying to install Crystal Reports Server 2008 V1 SP3 but I am getting this "architecture mismatch between ODBC driver and application" error while choosing the ODBC datasource for CMS.
I thought CRS 2008 version would easly be installed on Windows 2008 server as it mentioned on the installation guide.
How do I resolve this issue?Moved to BOE Admin forum.
CRS 2008 is a 32 bit app so all attachments, Printers, DB clients, etc. must all be 32 bit or support 32 bit applications.
Use the 32 ODBC administrator in \windows\syswow64 folder.
Thank you
Don -
Communication between the computer and the disc drive failed
The disc can’t be burned because because communication between the computer and the disc drive failed (error code 0x80020022). This computer has been out of the box for less than a month and this has been a growing problem.
My problem was FIXED at the apple store..... there was something wrong in the system preferences and the genius deleted something that recreated it's self. Surely enough we we're able to burn a 600 mb dmg of nothing onto a few test disks. For anyone having this issue...it's NOT The media, it's some configuration issue within the computer's preferences. I'm telling you all to take your machine to the nearest apple store and have them fix it, if your machine is still under warranty the fix is free. There was no hardware issue, so the optical drive was not replaced.
-
Tethering via USB between the Z10 and a laptop or PC & and few Comments About the Playbook Tethering
Tethering via USB between the Z10 and a laptop or PC can be a bit tricky.
On the Z10 do the following:
On the Z10 go to the Settings.
Go to Network Connections.
Go to Internet Tethering.
Select USB.
Turn on Tethering.
On the computer run the Blackberry Link software for the Z10:
Once the software starts, connect the Z10 via the USB cable to the PC.
Open the browser.
You should now be able to cruise the net, and do emails.
With the Playbook, the Bluetooth tethering does not yet work. This may be an OS or communications issue.
The best way to tether the Playbook for full speed and functions is using the WiFi option. Simply turn on the WiFi hot spot option and follow the instructions. The Playbook WiFi must also be properly set up. The Z10 USB and Bluetooth tethering mode must be turned off when using the WiFi mode. You can leave the base Bluetooth active on the Z10. There is a lot of available information about using the WiFi hot spot from the Z10. The process is very similar to the past models of Blackberry phones.
If you use the Bridge mode to tether, the Playbook email client software does not work very well. The browser will work fairly well, but slower with the Bridge mode. With WiFi the Playbook can brows at very high speed. With Bluetooth it is restricted to about 1.5 to 2.5 mb/sec. Take care that the WiFi mode burns through battery time very fast on both the Playbook and the Z10. Using the Bridge mode uses less power consumption than WiFi.
To use the Bridge mode, make sure the Playbook and the Z10 are first Bluetooth mated. Also the Bridge mode has to be set up between the devices. You will have to first install the Bridge software in to the phone for this to work.
I did extensive testing between the Z10 and the Playbook. They function well together as far as Internet and email are concerned, in consideration of using either tether or Bridge, depending on what you want to do.
From what I understand the Bridge mode uses some compression. It will not be as fast as using WiFi or Bluetooth tethering. The data cost using the Bridge mode is probably a bit lower because of the compression.
As far as the Bridge phone options are concerned, these features are not yet available. From what I read in a number of articles there are going to soon be some updates coming out to fix this. The Bridge options are a big part of the tablet application with the Blackberry phone. This was the big original application point of this tablet, otherwise any generic tablet would do the job.
Jerry G.From the look of this thread it appears that no one outside of Canada uses an OS 10 BB yet. 247 views and no comments or help ? I'm sure I'm not the only BB user that uses Tether. If BB doesn't care to help then this will just be another nail in the corporate coffin that has been projected.
Maybe we need different forums for US users as the Canadians don't seem to have the same issues or cares.
The whole idea of the app Tether is not to have to pay the outrageous tethering fees that US carriers charge and it has worked well for years. But it can't work and won't work in the future without help from BB and the BB community. -
My 1st Generation time capsule won't connect to the internet thru a new motorola sb6121 - get continuously flashing yellow light. Using a router in between the modem and capsule yields good but slower connection to internet. Any thoughts?
Thanks for your response
Let me give the history - I started with an Apple Express being fed thru a D-Link EBTR 2310 cable Router from an RCA DCM315 Modem (Pure). Comcast service all the way.
Got the 1st generation TC in 2008 and merely replaced the Airport Express with the TC. Worked ok
A year or two ago I did try removing the modem and feeding the TC directly from the modem. Resulted in the same condition I have now - Continuous flashing amber on the TC. So I put the router back in the chain.
Some time later, at the recommendation of a Comcast rep, I replaced the router with (a Belkin F5D 5231) to see if speed and dropout problems would be improved. I thought it helped some at the time but now I am not so sure.
Last week I decided to see if a new modem would help with download speeds. So I got another pure cable modem (Motorola SB 6121- high on the Comcast recommended list).
Got up and running easily with Comcast help and with the modem connected directly to a computer.
Next I put the TC in the link and again could not get past the TC continuing to flash amber. Although I did get connected to the internet with this configuration I lost connection two both of my printers - one connected by USB and the other wirelessly to the TC. Again everything works fine when I put the Belkin router back in the system.
However with the router in there, the modem shows the downstream connection to be 10/100 ethernet speed. (Modem light changes color for indicating speeds.}
I have gone thru all of the combinations of powering down/ up, but all stays the same.
I can live with what I have but something still doesn’t seem right.
Thanks again -
Can't establish wireless connection between the printer and computer.
I recently upgraded my wireless to an Apple AirPort Time Capsule. I'm able to set up the printer via USB cable. And I'm able to set up the printer on the network via the Airport WPA utility. However I cannot establish a wireless connection between the computer and the printer. When I go to the printers window in my system prefereces, there is no wireless printer available to add in the "available printers" menu. Only the USB version printer is listed and of course when I disconnect the USB cable it shows as offline.I've tried all the fixes on HP's support pages. I've tried reinstalling the printer on both the router and the computer numerous times. The only thing I haven't done is reinstall the printer using the "Install Wizard" software that is supposed to come with the printer - (mine never came with it in the first place and of course HP doesn't have it available for download). And when I reset the printer to factory settings, then connect it to the computer via the USB, there is no installation software that pops up. Cant even find the **bleep** thing in "Finder". (I'm assuming that it should show up as some sort of external device.) I've checked to make sure both computer and printer are on the same network. (sometimes my computer will grab a connection with the next nearest network.) I've checked all the settings for the printer via the HTML configuration utility. I've even updated my Macbook software and restarted it multiple times. Note: the printer actually worked for a bit when I first switched routers, but the printer's wireless function went offline several times and then quit altogether. Really frustrated that I bought another HP product thinking this time things would be different. HP is no help unless you want to pay $$ for a phone call. I'm about ready to take this thing out in the desert to use for target practice and never buy another HP product ever again.
Hi , I saw your post regarding the problems you are having with your LaserJet Pro P1102w Printer not showing on your Macintosh computer. I may have found some resources for you.
I have a few questions for you, so I can offer some additional assistance:Before you upgraded to the Apple AirPort Time Capsule, was the printer working wirelessly without any issues?
When you say; 'I reset the printer to factory settings', how where you trying to do this?
I found some instructions from this post: How do I reset my Laserjet p1102w to its defaults, copied here for you:
To restore the printer back to factory settings, turn the printer off, hold down the wireless button and the cancel button (x button) then turn the printer back on and don't release the two buttons until the printer stops making noise. (When they say turn the printer off, I think they mean unplug the power cable.)
"I've checked to make sure both computer and printer are on the same network." Do you know if you are able to access the printers Embedded Web Server (EWS)?To access the EWS - Make sure that the Ready light () is on and that the printer is idle and silent.Press and hold the Cancel button (), and release it when the Ready light () begins blinking.The configuration page prints.Type the IP address or host name of the product in the address field of a supported Web browser, and then press Enter on your keyboardLet me know if this page loads
To answer a few more items you have listed:... When I go to the printers window in my system preferences, there is no wireless printer available to add in the "available printers" menu.This could be an issue with your print system, I recommend resetting the printing system and then Repair Disk Permissions - after that try to add the printer again.
... the "Install Wizard" software that is supposed to come with the printer - (mine never came with it in the first place and of course HP doesn't have it available for download)HP provides their software/drivers to Apple to be released through your Apple software updates. You can review this document on how to Install a Mac Printer Driver Using Apple Software Update. Which leads into your next point...
... there is no installation software that pops upWhen you connect the USB cable your mac may still recognize the printer software as being already installed - check for apple updatesOn the Mac, click the Apple menu (), and then click Software Update, or click About this Mac, and then click Software Update. A list of available updates displays.
... Not seeing the printer in "Finder" From what I understand most printers will not show in Finder unless you install a memory card into a supported port on certain printer models, only then will it read it like an external device. A few more things you can check are that the new settings in the Apple AirPort Time Capsule are setup to allow the printer to communicate. There are several of these settings listed in this document; Tips and Workarounds for Common Wireless Network Printer Issues. HP regularly releases firmware updates that may also correct the problem you are experiencing. You can click on this link to Getting Printer Updates for HP LaserJet Pro P1102w Printer. I did find 2 more documents that may offer some additional information as well;HP LaserJet Pro P1102w Printer - Connecting the Printer After Changing Your Wireless NetworkAn 'Unable to Find Printer' Error Displays for the HP LaserJet Pro P1102w Printer Please let me know if any of these steps resolved your issue, or the details of what happened. I look forward to hearing from you, hopefully with good news! Thanks,
Maybe you are looking for
-
How to get Livecycle Service Discovery Plug-in for Flash Builder working in 4.6
Hi all. Re this product: http://help.adobe.com/en_US/livecycle/9.0/sd_releasenotes.htm Does this work in 4.6? It worked fine in 4.5, but I'm not having much luck getting it up and running in 4.6. Adter installation, I can see the connect to Livecyc
-
Roles for user in supplier self-registration
Hello everyone, I was checking the configuration guide for Strategic Sourcing and for Servece Procurement and I have a doubt. For supplier self-registration is needed an anonymous user, but in the guide for Strategic Sourcing says that the roles for
-
Hi i have problem with my hp mini is giving me a error CNU9391WZR PLEASE HELP
Hi i have problem with my hp mini is giving me a error CNU9391WZR PLEASE HELP Hp mini 110 1140el
-
News from Apple Store: 10.6.3 - 10.6.3.1 seems to work on my iMac...
I originally shared my woes on this issue with "youngpunk" last week, but since my machine worked under Safe Boot and since I presumed my problem was overheating (based on other posts and my own SMC observations w/ioreg... GPU @ ~45 C. under Safe Boo
-
How to restrict views in MS INFOPATH 2010 based on a user Login id
Hi, I am the Admin of the Time Reporting SharePoint tool for my project. When a user enters/edit a time report ,it is done via an Infopath 2010 form. This form has 2 views: 1. For the normal users to see (default view) 2. For the Admins only. What i