Home » SQL Server

Package Fails When Using 32-bit Teradata Driver

Upfront - I'm not sure if this question belongs with this forum or another more specific to SQL Server Agent.

I have a package running on Windows 2003 (64-bit) attempting to pull data from a Teradata server using its 32-bit driver.  The package runs as expected within BIDS and when called from a BAT file run from the command prompt using the 32-bit version of DTEXEC. 

The package fails with the following error when I attempt to run it using the same *.BAT file (which succeeds from a command prompt) or when specifying the DTEXEC command directly in an operating system job step.  Any insight, suggestions, or workarounds would be helpful.

Executed as user: <<<userName removed>>>. ...\dtexec.exe /SQL \HRD_ODS\TheW_Connection_Test /SERVER CRPRDNMSQR2  /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EMicrosoft (R) SQL Server Execute Package Utility  Version 9.00.4035.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  11:47:59 AM  Error: 2011-01-25 11:48:01.26     Code: 0xC0047062     Source: Data Flow Task DataReader Source [419]     Description: System.Data.Odbc.OdbcException: ERROR [IM003] Specified driver could not be loaded due to system error  126 (Teradata) .     at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode)     at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle)     at System.Data.Odbc.OdbcConnectionOpen..ctor(OdbcConnection outerConnection, OdbcConnectionString connectionOptions)     at System.Data.Odbc.OdbcConnectionFactory.CreateConn...  Process Exit Code 1.  The step failed.


10 Answers Found


Answer 2

Hello , please check this


maybe you need Edit your step and then go to Execution options and Check the Box for 32 Bit.

give a try



Answer 3

Arthur, Aamir:


I appreciate the reply guys the option is available.  I should have mentioned in the original post I'm using SQL Server 2005.


Answer 4

You are welcome Orlanzo,

curious if you have resolved the issue by applying this setting.


Answer 5

Hi Arthur,

No, the setting isn't available in SQL Server 2005.  What you're referring to was introduced in SQL Server 2008.


Answer 6

Add the /X86 key to the DTExec

Answer 7

Add the /X86 key to the DTExec
Arthur My Blog
By: TwitterButtons.com
That option is not available with SQL Server 2005.

Answer 8

Follow this article "How to use the 64-bit SQL Server Agent to schedule a SQL Server 2005 Integration Services package":


The post walks you through on how to properly set up the Agent Job to run the 32 Bit version of DTExec.


Answer 9

Hi Arthur,

I'm familiar with how to call the 32 bit version of DTEXEC from SQL Server Agent.  I did review the article you provided and confirmed my end result is identical to what it describes.


Answer 10

Started to think this can be because your environment is clustered.

I can see how this was be fixed here: http://blog.vyvojar.cz/dotnet/archive/2008/04/09/227349.aspx

Short excerpt:

w3wp.exe didnt see path \Program Files\NCR\Common Files\Shared ICU Libraries for Teradata\lib -- in your case it might be different

Fix solution:
Copy files from Teradata\lib to one from directorys where execept w3wp.exe files (System32 dir, ..)

So in your case running the package as SQL Server Agent does not let the file be found. It runs in BIDS because you execute the package locally (on your PC) unless you are running it directly on the server.

Arthur My Blog
By: TwitterButtons.com


Is there a way to control Which Oracle Drivers is used by System.Data.OracleClient if more than 1 exists? Such as 32 bit and 64 bit versions in different home folder? I mean I need to control this from different processes, and the only place I can control that is through connection string.

Or fundamentally, can a process use the appropriate driver (32/64 bit) depending on itself being 32 or 64 bit?



I am on process of migrating our SQL Server INtegration server packages from a 32 Bit(server A)  serevr to a 64 bit server(Server B).

In our packages we connect to the IBM I series server DB2 databases, and we have all the required drivers installed on to our earlier server, we used to connect via the client tools for IBM I series access, and the Connection manger in SSIS package is a Natvie Oldeb Provider which uses the IBMDADb2.1 provider, this i have checked via the advance settings on the connection manager.

I have tried this in our development 64 bit environment, and whenever i try opening the package there it states the type of connection manager is not recognised despite the IBM I series client tools installed correctly as per above which works fine on 32 bit serevr,

Also i did download some drivers from IBM sites and registered them, the difference from 32 bit serverA here was that the new .dll went to c\programm files(x86) folder and then from there i registered it, once done i was able to see same IBM DB2 OLEDB provider cropping up on my SSIS package, but this time in advance setting the type of this was IBMDADB2.db2 and still my package conneciton manager wouldnt open. as the type above was IBMDABdb2.1

My query here is :

1. Is it that i have installed some wrong version of DB2 driver that connection mangaer is not working and in 64 bit the IBMDADB2.db2 driver only works and not IBMDABdb2.1?

2. I still cant fint the .dll file needed for IBMDABdb2.1 type of driver, is it possible if i can get this from somewhere my pacakage will work fine on 64 bit also


Any help is greatly appreciated, am stuck


I've seen many post close to this question but none that actually address the problem I'm having.

I have an IE extension which works perfectly well with several version of IE on several different OS versions.  That is, the 32bit version of the extension works with the 32bit version IE7 and IE8 on the 32bit version of the Windows - (XP, Vista, and 7).  The 64bit version of the extension works with the 64bit version of IE8 on Windows-7 (haven't tested on Vista... but figure it would work the same).

But I have a specific issue with the extension to the 32 bit version of Internet Explorer running under Windows-7 64 bit OS.

If I understand how Wow64 works on the 64 bit OS:

My 32bit extension would go in a folder: \program files (x86)\<Name>

I would then create the following registry entires:

HKLM\Software\Classes\Wow6432Node\CLSID\{My32bitGUID} with subkeys (1) InprocServer32 pointing to my DLL in \progarm files (x86)\<Name> with string ThreadingModel="Apartment" and (2) Implemented Categories with subkey {00021493-0000-0000-C000-000000000046} (for a vertical extension bar)

HKLM\Software\Wow6432Node\Microsoft\Internet Explorer\Extensions\{My32bitButtonGUID} with strings: BandCLSID={My32bitGUID}, CLSID={E0DD6CAB-2D10-11D2-8F1A-0000F87ABD16}, ButtonText, Default Visible, and Icon

Other than the Wow6432Node in the registry keys this is basically the same (but with different GUIDs) as what I use for the 64bit extension in the 64bit Internet Explorer.

When I do this, the custom tool button appears in the 32bit IE8 window as normal - but when I click the button IE8 does not access my extension in anyway that I can tell.  No window is created and as best I can tell none of the window creation routines are called.

It seems I'm missing something trival and simple... but I can't seem to find any reference that points me in the right direction.  I've read everything I could find in the extensions guides.

Any help/input appreciated.


In our setup application we make a call to pkgmgr in order to install IIS7.
As our application is 32-bit it will launch the 32-bit version of pkgmgr (Windows 7, 64-bit).
However, when launching the pkgmgr tool a misleading message box error shows up:

"Operation failed with 0x8007000B"
"A attempt was made to load a program with an incorrect format."

The command used: pkgmgr /norestart /iu:IIS-WebServerRole /l:c:\output.txt

If launching the 'native' 64-bit version of pkgmgr with the same command line then the execution succeeds.
In the log file we see that the call is translated into a call to dism.exe:
dism.exe /online /norestart /logpath:"c:\output.txt.txt" /enable-feature /ignorecheck /featurename:"IIS-WebServerRole"

The reason why it failed is now clear:
"You cannot service a running 64-bit operating system with a 32-bit version of DISM.
Please use the version of DISM that corresponds to your computer's architecture."

Shouldn't the 32-bit version of pkgmgr.exe 'redirect' the call to the 64-bit version of pkgmgr/dism, since all Windows packages are native 64-bit?  How can I get around this?
Hi All,

I am having an Application build on Win32 Platform. This application enumerates available processes on the local machine. This application works fine on Win32 however it does not work on 64 bit.  It retrieves 32bit process names and fails to get 64bit process names. I read few questions on forums and they say that we cannot access 64bit processes from a 32bit application. However there are few methods such as EnumProcessModulesEx which can access both 32 and 64 processes. This method is available only on Vista 64.
Is there any corresponding API which I can use it on Win2k3 x64 ? or anyother way we can access process names both 32 and 64bit on Win 2k3 x64 computer.
Any help!!!



#pragma once

 #pragma managed

 using namespace System;

 using namespace System::Runtime::InteropServices;

extern "C" __declspec(dllexport) bool Foo(char* text)


// System::String __gc *str = Marshal::PtrToStringAnsi((System::IntPtr) text)



 I call this method from unmanaged C++ and I get exception thrown in debug:

file f:\dd\vctools\crt_bld\self_64_amd64\crt\src\dbgheap.c Line 1511

Expression: _CrtIsValidHeapPointer(pUserData)

I commented out the managed lines and I still get the same exception thrown. But if I add #pragma unamanaged and leave managed lines comment out. Runs fine in 32 bit system. I loaded the dll in depends and looks like all the dependent modules are 64 bit. I am stuck not knowing what to do.  Any help would be appreciated?


Hello -

I have isolated what appears to be a bug in 32-bit IE8 running on 64-bit Windows 7: "window.open()" fails.

Consider the following very simple PHP file:

        require_once($_SERVER[DOCUMENT_ROOT] . '/sency.jquery.inc');
    <script type="text/javascript">

(Of course, the include file points to the standard JQuery include file.)

Accessing this PHP file in 32-bit IE8 on 64-bit Windows 7 causes the new window to appear, but it hangs and never loads any content.  It works fine on 64-bit IE8.

Sure seems like a Microsoft bug to me.  Can others confirm?


Dan Nissenbaum


Hi there,

I have a 32-bit windows service that runs fine under 32-bit Windows 2003, however it failed to start under 64-bit windows 2008. I already spent 3 days of searching and debugging but still cannot solve it, hope someone could shed some light on it.


The .exe can run without problem both as a windows service and console app on a 32-bit Windows 2003.

On 64-bit Windows 2008, the same .exe can run without problem as a console app. However, when I start it as a service (by running net start myService) it returns "service could not be started" .... NET HELPMSG 3523.

I have add some debug code in the ServiceMain function (the function that passed to StartServiceCtrlDispatcher ) and found that the ServiceMain was NOT called. But the StartServiceCtrlDispatcher did not return, so it seems to me that it failed to get connected to the SCM.

However, I have no idea how to proceed and wish to get someone could shed some light on it


Thank you











Hi, I'm having a lot of trouble connecting to my out-of-proc COM service.  It was initially a 32-bit service, and everything was working just fine, but it became necessary to turn it into a 64-bit service in order to load a 64-bit DLL that I need. I do not have the ability to do a 64-bit build of the application that uses the service, but I didn't think this was a big deal.  I created a 64-bit build of the service, but when that is registered, the application hangs on the call to CoCreateInstance, but a breakpoint in the class factory for the requested object never gets hit... if I kill the service process, then CoCreateInstance returns with a failure... I have no idea how to go about narrowing down the actual problem... any help would certainly be appreciated

Thanks in advance,




I want to create pipe and execute 64-bit command using my 32-bit application. But it fails to open 64-bit command and gives message as '.... is not recognized as an internal or external command,
operable program or batch file'.

But if I create 64-bit application, it works properly. I want to run 32-bit application.

There is any way  to resolve this problem?


Thank you.


We are installing Windows 2008 using the Winpe 3.0 environment which I understand is essentially a stripped down Windows 7.  All of my Dell Machines can be installed using this environment except two models that have the PERC 4e/Di Scsi Controllers.  I partition and format the drives in Winpe and kick off an install if Windows 2008.  I've created a Winpe 3.0 32-bit and Winpe 3.0 64-bit image.  I loaded the Dell Windows 2008 R2 (of course 64-bit) driver into the off line winpe 3.0 64-bit image and I'm able to successfully install Windows 2008 64-bit on a Dell 2800 with the Perc4e/Di SCSi Controller.  I'm not able to find a 32-bit driver to load into the 32-bit Winpe 3.0 image.  Would the inbox driver in Windows 2008 32-bit work?  If so, how do I extract that driver to load into the Winpe 32-bit offline image?   I've spoke to Dell support without any success because the technicans I've spoke to so far do not understand winpe. 

I recently started working with WES2011 and have been successfully working with WES2009 for some time now. I have a good image created for the Ampro RB820 that I'm working with right now under WES2009.  However, when I ran the WES2011 32 bit IBW disk, after the installation I have 2 devices that Device Manager has flagged. 

Video Controller - I know this board has the Intel integrated 915GM chipset and I had no problems with 2009.  I have tried downloading drivers from Intel to no avail.  Everything I have tried said it wasn't compatible with the OS.  Also, I have an Optiplex GX280 here with the same chipset. After I installed Windows 7 - 32 bit (RTM) on it, it also complained about video drivers, but I was able to install drivers from the Dell website.  I'm confused, this video chipset is so popular as it is found in just about every "budget" system out there.  Why would W7 and WES2011 not have native support for that chipset right out of the box? Forthermore, how comes drivers that do work for W7 aren't compatible with WES2011? Currently, it is using the "Standard VGA Graphics Adapter" @ 1024 x 768. Vendor ID: 8086 Dev ID: 2592

Multimedia Controller - the RB820 has onboard audio via an AC '97 interface. It is built into the82801FBM Southbridge chipset. Tracking down the numbers, it is identified as SoundMAX Integrated Digital Audio Manufacturer Analog Devices, Inc.  Vendor ID: 8086 Device ID: 266E

These both seem like normal devices and they worked fine under Windows XP and WES 2009 (of course).  I would understand a little more if I was running 64 bit, but I'm not. 


I downloaded the WES 2011 CTP toolkit and followed the installation instruction to use the WindowsEmbeddedStudio.msi (not the Setup.exe) to install the toolkit.  It failed the installation more than half way through and displayed a dialog asking for the 64-bit WES runtime.  I clicked on cacel to close the dialog and the installation rolled back all the way.   This is a bit odd because I am using a 32-bit Win XP SP OS and not 64-bit.   

When I tried to use the Setup.exe to install the WES 2011 CTP, the installation worked fine but the installation instruction indicated "NOT TO USE SETUP6.EXE" to do the install and tells the user to use the WindowsEmbeddedStudio.msi.   Why is that?  

What are the side effects of using the Setup.exe to install the WES 2011 CTP?


I am not able to successfully run and pass "Reinstall with IO" test which is being run for Scanner using WLK 1.4(RTM) for Win7(RC) 32-bit client. Studio is installed in Windows 2003 server R2 with SP2.

Please do let me know how to pass "Reinstall with IO" test. I have two more tests to pass, which is again dependent on this.


MY device is a touch device with USB. I use Win7 32 bit client for testing this device for Win7 logo. USB Address Description test fails. I connect this device to the client through a external USB hub. Please provide me some insight on why this test fails.


I switched computers and went to the old faithful loaded with Windows XP...but alas, still not loading. At least this time the setup did produce a Log Summary which I supplied below. Any help would be appreciated. Thanks,

Microsoft SQL Server 2005 9.00.1399.06
OS Version      : Microsoft Windows XP Home Edition Service Pack 3 (Build 2600)
Time            : Sat Sep 18 12:51:56 2010
D11LGX61 : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features.  Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
Machine         : D11LGX61
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_SQLSupport_1.log
Machine         : D11LGX61
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_SQLNCLI_1.log
Machine         : D11LGX61
Product         : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_OWC11_1.log
Machine         : D11LGX61
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_SqlWriter_1.log
Machine         : D11LGX61
Product         : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_BackwardsCompat_1.log
Machine         : D11LGX61
Product         : MSXML 6.0 Parser (KB925673)
Product Version : 6.00.3888.0
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_MSXML6_1.log
Machine         : D11LGX61
Product         : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_SQL.log
D11LGX61 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.

 SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

Time            : Sat Sep 18 13:06:58 2010

List of log files:
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_Core(Local).log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_SQLSupport_1.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_SQLNCLI_1.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_OWC11_1.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_SqlWriter_1.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_BackwardsCompat_1.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_MSXML6_1.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_SQL.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_Datastore.xml
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_.NET Framework 2.0.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_Core.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_.NET Framework 2.0 LangPack.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_.NET Framework Upgrade Advisor.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_.NET Framework Upgrade Advisor LangPack.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_.NET Framework Windows Installer.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_.NET Framework Windows Installer LangPack.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_Support.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_SCC.log
 C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_D11LGX61_WI.log


We do analysis and testing of different scenarios we might use to upgrade our SQL Server 7.0 upto newer version.

The last successful upgrade was done on SQL Server 2008 Standard and Windows Server 2003 Standard 32-bit. Now we do testing of SQL Server 2008 Standard installed on Windows Server 2008. This time we met a problem with SQL Mail service.

When we started the SQL Mail service by means of system procedure sp_startmail, we got error message:

SQL Mail session started.
Msg 17925, Level 16, State 1, Line 0
xp_startmail: failed with mail error 0x8004011d

The code 0x8004011d means and error MAPI_E_FAILONEPROVIDER. Despite the error the MAPI session was started.
We know that, because if the procedure sp_startmail is run again, we receive the message: SQL Mail session is already started.
If we try to send an e-mail by means of procedure xp_sendmail, we get another error message:

Msg 17925, Level 16, State 1, Line 0
xp_sendmail: failed with mail error 0x80004005

The code 0x80004005 means the error MAPI_E_CALL_FAILED

We know that it is recommended to replace SQL Mail with Database Mail. But the xp_sendmail is used in 50 stored procedures. The change will take much time (development, testing, Change Management process).

We are happy, if we can make the MAPI functions to work well on Windows 2008, do upgrade and then replace the MAPI with SMTP after.

Please help.



I have a 32-bit app which has been running under XP for years.

Running it under Win7-x64 WOW64 however, I find that it crashes.

After hours of debugging, I find that WOW64 clobbers the ESP value (as returned by GetThreadContext(), of which the the main thread in the app relies upon to get the current stack pointer of worker threads) when it's running kernel code (but restores ESP upon returning). Prior to calling GetThreadContext(), the main thread suspends all worker threads. If the main thread just so happens to suspend the worker thread while it's running the code in (note that my 32-bit debugger can't single step into 64-bit code)

73472320 jmp 0033:7347271E 

the ESP gets changed to a value indicating a higher address than the actual stack pointer. I've seen this happen for SetEvent and SwitchToThread (as these are the most frequently called kernel functions in the app).


This means that either SuspendThread is suspending a thread in an incompatible way to native x86, or the thread's context in WOW64 is not being protected when the code jumps to translation mode. Either way, it's a bug.


Our application developed under Visual Studio 2008 fails to launch under Windows 7 -32 bit. This is a silent error - with no complaints from Windows itself.

I have double-checked  the usual suspects of C++ runtime versions.

Running "Profile" under Dependency Walker shows that the point of failure.....

DllMain(0x6F0B0000, DLL_PROCESS_ATTACH, 0x005AFC8C) in "c:\windows\system32\SHUNIMPL.DLL" called.
DllMain(0x6F0B0000, DLL_PROCESS_ATTACH, 0x005AFC8C) in "c:\windows\system32\SHUNIMPL.DLL" returned 0 (0x0).

If I set the "Compatibility Mode" of our application to Windows XP SP3, then the application launches without failure.

So my suspicion is that somewhere we are calling a "deprecated" API, and that causes a failure to load.







Hi I am new to 64 bit OS. Till now i Develop everything on 32 bit.
I had not made any program as 32 bit. I just open the VS2008 IDE and there I select new project as Web Service Application .  In webservice application I refer SharePoint Dll.

I write one webmethod called HelloWorld() in which i just write one line code on for SharePoint
SPWeb obj = Site.OpenWeb();

but as soon as i try to run it thorws an exception

Attempted to load a 64-bit assembly on a 32-bit platform. Use ReflectionOnlyLoad() instead if trying to load for reflection purposes

can any one pls help me...



<< Previous      Next >>

Microsoft   |   Windows   |   Visual Studio   |   Sharepoint   |   Azure