SSRS 2012 ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

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 Services

Hi 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

Similar Messages

Crystal Reports Ver 11 Logon Failed IM014 [Microsoft] [ODBC Driver manager

Please help. I am using Crystal Reports Version 11. I have Windows 7 and 64-bit browser. I am receiving the following error message: Details: IM014: [Microcsoft] [ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.

Hello,
Two issues, CR XI is not support on Windows 7. To get this working upgrade to Cr XI R2 SP 6 for free, use your XI keycode.
https://smpdl.sap-ag.de/~sapidp/012002523100011802732008E/crxir2_sp4_full_build.exe
and then
https://smpdl.sap-ag.de/~sapidp/012002523100013876392008E/crxir2win_sp5.exe
https://smpdl.sap-ag.de/~sapidp/012002523100015859952009E/crxir2win_sp6.exe
Do not run CR between patches, When SP 6 is installed then CR should work.
Next issue is CR is a 32 bit application only and it will run on 64 bit OS's but it will not support any 64 bit third party applications including IE. To connect to your database you must use the 32 bit client.
Run the ODBC Administrator from the \syswow64 folder to create your DSN.
Thank you
Don
Edited by: Don Williams on Nov 4, 2010 10:06 AM

ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in windows server 2008 r2

ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in windows server 2008 r2.I made a application in asp.net c#.I am using ODBC connection.When I deployed my application in windows server2008 r2.There
is no Microsoft ODBC driver shown in ODBC Data source administrator.Then I go to the C:\Windows\SysWOW64 and open Odbcad32.exe and add Microsoft ODBC2 driver for Oracle and when I run my application I got following error
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
I am using follwoing string
<connectionStrings>
<add name="theconnetion" connectionString="DSN=abdb;UID=abc;PWD=xyz"/>
</connectionStrings>
Guide me What I do?

Did you add a System DSN or a User DSN? If you added a User DSN from your own login, the asp.net application will not be able to use it unless its application Pool in IIS is configured to run under the same credentials that you used for creating
the DSN. It's better if you add a System DSN.
Also, be careful to ensure that you are using a 64 bit DSN, unless you configure the application to run in 32 bits. If the 64 bit application attempts to use the 32 bit driver you get the same error message "Data source name not found and no default
driver specified". See this KB article:
http://support.microsoft.com/kb/942976/en-us

SQL Server Reporting Services: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

Hey everyone, So I am trying to get a report onto the server, and in BIDS I kept getting a login screen repeating over and over when I tried to deploy my report, so I tried to upload the file at http://<servername>/Reports This worked, but then trying
to run this report from http://<servername>/Reports did not work either because "An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'FTYDataSource'. (rsErrorOpeningConnection) For more information
about this error navigate to the report server on the local server machine, or enable remote errors" Anyways I tried to add a New Data Source (which I would use in the report) at http://<servername>/Reports, type ODBC, with the connection string Dsn=blah_blahblah.
I try to test the connection here and get the error ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified This is really getting old fast, everything I try, a new error comes up. Granted I am new at this,
but this still should not be this troublesome. Does anyone have any ideas on what could FINALLY allow me to just put a report out onto the server?!? THANK YOU in advance for ANY help.

Hi,
Please try setting the credentials of the datasource.
1. Double click and open the datasource in your project.
2. Click on the credentials tab, and click on option button 'Use this username and password'
3. Enter the username and password to connect to the datasource
4. Deploy or upload the datasource to the report server and try accessing the reports.
Hope this helps.
Please click "Mark as Answer" if this resolves your problem or "Vote as Helpful" if you find it helpful.
BH

Connection failed: SQLState:'01000' SQL Server Error:67 [Microsoft]ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Connection failed: SQLState:'08001' SQL Server Error:17 [Microsoft]ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist o

Help,
setup a new sql server 2012 on a windows 2012r2 server to replace old sql server 2005 on an old windows server 2003 machine. When i test the ODBC connection locally on the server it works fine, however when i try to connect via windows 7 client machine
i get the following error:
Connection failed:
SQLState:'01000'
SQL Server Error:67
[Microsoft]ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection failed:
SQLState:'08001'
SQL Server Error:17
[Microsoft]ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied
I think it must be a permissions thing, I've turned off the firewall for now and still no difference, 've also made sure remote connection is enabled. I can connect to the other sql server in studio manager on the new machine however, i can't go do
the same in the old server, says:
cannot connect to hbfsqlpro1\hbfsqlpro1
Additonal information a network related or instance specifc error occured while establising a connection to SQL server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL server is configured to
allow remote connections. (provider:SQL Network Interfaces, error 26 - error locationg server/instance specified) (Microsoft SQL server)
the instance is def correct, as that is what i use to connect locally on the new machine and what it comes up on the studio manager on the new machine. STarting to pull my hair out somewhat, i'm sure it's something really simple!

Hello,
You are trying to connect to a named instance. Make sure the SQL Server Browser service is started on the SQL Server computer.
Make sure TCP/IP is enabled.
http://msdn.microsoft.com/en-us/library/ms191294(v=sql.110).aspx
Try to disable Windows Firewall or security software on both, SQL Server instance and client computer.
Test basic connectivity too. Try to ping from the client computer to the SQL Server computer.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Database Connection Error 42000:[Microsoft][ODBC driver for oracle] Syntax

Hi,
This is Sathish, I am trying to create a report and retrieve data through stored procedure using ODBC Connection. When connecting to the Stored Procedure it is showing Database Connection Error 42000:[Microsoft][ODBC driver for oracle] Syntax error or access violation' Error.
CRXI R2, Oracle 9i.
What do i do to solve this issue.
Regards,
Sathish

Hi Satish
It could be an issue with the driver.
You can try with the OLEDB n Oracle native connection to test if the issue persists.
Also you can refer to the [Troubleshooting Database Connectivity for Crystal Reports|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/d05b3bb7-0f28-2c10-4ea3-84dbdc4e414e&overridelayout=true]
Hope this helps!!
Regards
Sourashree

"ODBC Error= [17] [] "[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQ

Hi,
I am getting the above error when trying to connect to a database located on remote database. if the database is on same system no problem.
any clue???????pls help me.

The full error msg is as follows and the back ground of the problem is decribed below...pls help me out.
I have written some perl programs to be called by java to execute some database related tasks. My database located at a remote win2K server and database is MSSql and my programs are executing on WIN2k server. The problem is with perl talking to remote database...the following error is displaying...
"ODBC Error= [17] [] "[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied."

Error [hyt00] [microsoft][odbc sql server driver] query timeout expired

I have the below network setup:-
1. Its a simple network at my father's office at a small town called Ichalkaranji (District - Kolhapur, Maharashtra).
2. We are using private network range 192.168.1.xxx with two Windows Server 2003 Enterprise Edition with SP2 licensed copies and 15 local Windows 7 clients who are only using Server A.
3. The network is having a TP-Link Braodband Router Connected to internet with the IP 192.168.1.1.
4. Both there Windows Server 2003 Enterprise Edition with SP2 are running separate SQL Server 2005 Express with Advanced Services, you can treat them as Server A (Problematic Server with IP of 192.168.1.2)
and Server B (this is not having any issue with IP of 192.168.1.3).
5. Server A is also being used by 6 Remote users from our Kolkata office using DDNS facility through the NO IP client software which installed separately on both the servers. Kolkata remote users
do not use OR access the Server B.
6. Server B is being used by only 2 Remote users from our Erode office (Under Salem District, Tamilnadu) using DDNS facility through the NO IP client software which installed separately on both
the servers. Erode remote users do not use OR access the Server A.
7. The front end application which running separately on both the servers have been developed in VB by a local vendor at Ichalkaranji (District - Kolhapur, Maharashtra).
8. Both Servers are having the same database structure in terms of design and tables format. Only difference is that both the servers are being used separately.
9. This error OR problem is only related to Server A, where on the clients we get the message "error [hyt00] [microsoft][odbc sql server driver] query timeout expired" every now and then.
10. We have to frequently reboot the server whenever we get this message on the client machines. May be after rebooting every thing works perfectly for 2 hours / 5 Hours / may be one full day but
the the error will come back for sure.
11. Current Database back up size on Server A is around 35 GB and take around 1 hour 15 minutes daily to take the back up.
12. Current Database back up size on Server B is around 3 GB and take around 5 to 10 minutes daily to take the back up.
13. One thing I have noticed is that when ever we reboot Server A, for some time sqlsrvr.exe file will show memory usage of 200 to 300 MBs but it will start using slowly, what i understand is that
this is the way SQL Server works.
14. Both the Servers are also running Quick heal Antivirus Server Edition separate licensed copies also.
15. Server B is also running Tally ERP 9 Licenses copy which is being used locally by 15 users of Ichalkaranji (District - Kolhapur, Maharashtra) same users
Can any one help to resolve this issue. Any help will be highly appreciated.

The error message "query timeout expired" occurs, because by default many APIs, including ODBC only waits for 30 seconds for SQL Server to send any output. If no data has been seen for this period of time, they tell SQL Server to cancel execution
and return this error to the caller.
This timeout could be seen as a token that the query is taking too long time to execute and this needs to be fixed. But it can also be a pain in the rear parts, if you are content with a report taking five minutes, because you only run it once a day.
The simplest way to get rid of the error is to set the timeout to zero, which means "wait forever". This is something your vendor would have to do. This may, however, not resolve the problem, as the users may just find that the application is hanging.
To wit, there are two reasons why the query takes more than 30 seconds to complete. One is that there is simply that much work to do. This can be reduced by adding indexes or by doing other tuning, if the execution time is not acceptable. The other possibility
is blocking. That is, there is a process blocking this query from completing. This is much more likely to require attention.
It is not clear to me, whether the vendor has developed the database part as well. In this case, you should probably call the vendor's support desk to have them to sort this out.
Finally, I am little puzzled. You say that you are using Express Edition, but one of the databases is 35 GB in size. 35 GB is far above the limit for Express Edition.
Erland Sommarskog, SQL Server MVP, [email protected]

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

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

Error: A user with the specified SID could not be found in the domain.

Hi All,
I am getting a error as below,
A user with the specified SID could not be found in the domain.
Check the spelling of the account name 'domain\usersAMAccountName' and try again.
-    at Microsoft.Office.Server.UserProfiles.UserProfileGlobal.GetSidFromAccount(String strAccountName, SID_NAME_USE[] IntendedAccountType, SID_NAME_USE& sidUse)
   at Microsoft.Office.Server.UserProfiles.UserProfileGlobal.GetSidFromAccount(String strAccountName)
   at Microsoft.Office.Server.UserProfiles.UserProfileGlobal.GetSidFromAccount(UserProfileApplicationProxy proxy, Guid partitionID, String strAccountName, Boolean isWindowsAccount)
   at Microsoft.Office.Server.UserProfiles.UserProfile.set_SID()
   at Microsoft.Office.Server.UserProfiles.UserProfile..ctor(UserProfileManager objManager, String strAccountName, String strPreferredName)
   at Microsoft.Office.Server.UserProfiles.UserProfileManager.CreateUserProfile(String strAccountName, String strPreferredName)
   at Microsoft.Office.Server.UserProfiles.UserProfileManager.CreateUserProfile(String strAccountName)
Any help?
Thanks,
Mohakk

Hi,
Per my understanding, the code should be OK, I have two suggestions as below:
1. Please ensure that the account of that user is valid in your production environment;
2. Try other accounts in the CreateUserProfile() funciton to see if it can work.
Feel free to reply if there any progress.
Best regards,
Patrick
Patrick Liang
TechNet Community Support

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?
Regards

Hi 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.

Microsoft.Exchange.WebServices.Data.ServiceResponseException : The specified folder could not be found in the store

In office365, I am trying to access conversation history folder of another user using EWS api.The user that is trying to access has full access rights of the mailbox . If i connect to the mailbox using owa, i can access the conversation history folder
including all other folders. But when i try to connect from the code using ews api below exception is being thrown:
Microsoft.Exchange.WebServices.Data.ServiceResponseException occurred HResult=-2146233088 Message=The specified folder could not be found in the store. Source=Microsoft.Exchange.WebServices StackTrace:
Here is the relevant code
var mailbox = new Mailbox(lyncUser.UserName);
var lyncFolderId = new FolderId(WellKnownFolderName.ConversationHistory, mailbox);
var lyncFolder = Folder.Bind(_exchangeService, lyncFolderId);
Also, the exception doesn't occur if connected to WellKnownFolderName.Inbox.

The WellKnowFolderEnum only works if the folder was created via the Lync 2013 client if the Mailbox is old and has been using older lync clients then you need to search for the folder via name eg see
https://msdn.microsoft.com/en-us/library/office/hh243707%28v=office.14%29.aspx . Generally you want to use both methods eg try to bind to the WellKnowFolderEnum first then use the search method if that fails.
Cheers
Glen

SBO Mailer Error - The specified resource type cannot be found in the image file

Hi Experts,
I have created an alert in SBO and selected email and internal option for same. I get internal message however email is not getting delivered, I checked the Event Viewer of Windows and below error is shown for SBOMail.
The description for Event ID 62 from source SBOMail cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Failed to mark records error [-1]
The specified resource type cannot be found in the image file
I can send email from sbo for other documents but the alert is not delivering email.
Please advise.
Thanks
Deepak

Hi Deepak..
Check with these threads...
http://scn.sap.com/thread/966957
http://scn.sap.com/thread/1295818
SBOMail Application log error
SBOMail error in event log
Hope Helpful
Regards
Kennedy

Error using "Microsoft ODBC for Oracle" driver

I am trying to connect to Oracle 10g Express Edition from Access 2003 on Windows XP. I created a DSN using "Microsoft ODBC for Oracle" driver. When I try to connect using ADO, I get this error:
[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
I googled this error and got a lot of hits but no solution.
Any help would be greatly appreciated. I am new to Oracle and am coming from SQL Server 2000.
Thanks a lot!

This is the connection string I am using:
Conn1.ConnectionString = "driver={Oracle in XE};Dbq=GMIS_LIVE.WORLD;Uid=Administrator;Pwd=ubs;"
These are the contents of my tnsnames.ora (what entries do I add to make this work)?
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = your-a9279112e3)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
)

SSRS 2012 ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application

Similar Messages

Maybe you are looking for