Sxstrace.exe Download Windows 7 32bit
Jovanna Ponder
The links in this blog may lead to third-party Web sites. Winthrop Development Consultants provides third-party resources to help you find customer service and/or technical support resources. Information at these sites may change without notice. Winthrop Development Consultants is not responsible for the content at any third-party Web sites and does not guarantee the accuracy of third-party information.
I try to down load certain e-mail from one paticilar person an I get this message: c;terryconnellappdatalocalmicrosoftwindowstemporary internet. side-by-side configuration is incorrect. please see the application event log for more detail.
Hey I'm not sure if it's the same thing but like everything i've downloaded/tried to play it will say side by side error usually the program files (x86) i'm not sure how i should do this it even does it when i try to open skype it says exactly ''C:Program Files (x86)SkypePhoneSkype.exe'' The application has failed to start because it's side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
What should i do?
I get this for Cyberlink PowerDirector:
C;ProgramFilesCyberlinkPowerdirectorPDR9.ex
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.
I'm on a 32-bit Windows Vista.
While I by no means speak for Cyberlink or can tell you how their app was built, I would think the solution is going to be the same.
If you check your application event log in windows, there will be an entry for this application. It will look similar to my screenshot for the error Dynamics GP was getting.
In it it will tell you the assembly and the version that this application is looking for. Now depending on what the file is, you'd then have to load that version of the components on your system.
Since I don't have your app and repro the issue, I can't tell you the version you need.
patrick
Hello Patrick,
I also have same problem. My project is of vb.net. I installed my project in one of my japanese machine. When i try to run my project .exe file. Its giving me error message saying:
"Side-by-side configuration of the application for this is not correct, could not start the application. For more information, please see the application event log"
I thinks this issue is similar to yours. Can you please guide, is this same or any else?
Rahul,
You might have build your app as a debug executable and so requires the debug components which a typical machine won't have. Try building "retail" and see if that resolves the issue. I didn't mention this in my article because no end users would ever have the debug version of this exe.
If retail also fails, then it is going to be the same solution as this article though perhaps not the same version of whatever assembly it is failing on. You'd have to check the event log to see which specific version of the file is failing and then verify that this version of the dll is loaded on the target machine.
I guess it could be language specific as ou mention a "japanese machine" is giving you the issue but that might just be coincidental.
In our environment, we have GP 10.00.1634 installed. So the machine was P2V'd since it was a server 2003 and was then in place upgraded to server 2008R2 x 64 bit. The application started throwing the same side to side configuration error. I m a newbie with the application, I did check the MSVC ++ 2005 and 2008 both were already installed.
Can someone please guide me get rid of this error and make this application work on this new VM please? Does this error has anything to do with DB as the DB as of now is SQL2005?
i got this C:/Users/giygas/Desktop/mugen.exe
The application has failed to start because its side-by-side configuration is incorrect Please see the application event log or use the command-line sxstrace.exe tool for more detail im on a 32 bit windows 7
Believe it or not.. 12+ years after this original post, this article saved me from some serious headache.. Ran into this message after having to install GP 2010 as a maiden setup on a brand new Windows 2019 & SQL 2019 server to perform upgrade of and old GP environment. After downloading the VC++ 2008 libraries, GP started just fine ?
If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more
I am using the .NET SDK in a console app that is being deployed to the Trim workgroup server (64-bit windows server 2008 environment) that has the 64-bit Trim installed. My console app references a class library I wrote to contain all the Trim-specific code, and this library in turn references the Trim dlls (HP.HPTRIM.SDK, HP.HPTRIM.SDKUI, TRIMSDK, trimsdkPIA20) which are all the 32-bit versions. The class library has its platform target set to Any CPU, while the console app has the platform target set to x86 (I'll get to this in a second). When the console app is run from the server, the following error occurs:
Could not load file or assembly 'HP.HPTRIM.SDK, Version=7.0.0.0, Culture=neutral, PublicKeyToken=93ab772ef8ad9a2e' or one of its dependencies. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (Exception from HRESULT: 0x800736B1)
Has anyone seen anything like the above when using the Trim .NET SDK? I tried changing the platform target of my console app to Any CPU, hoping that might resolve the issue, but that leads to another problem. The app has to connect to an Oracle db to execute a query, and so we are encrypting the Oracle connection string in the registry using a utlity program that is most likely targetting x86. When the console app is also targetting this platform, it knows to look for the connection string in the Wow6432Node folder in the registry. If I change its platform target to Any CPU, it no longer looks in that folder, causing it to crash because it can't find the connection string...
The only problem with using the 64-bit dlls in my class library is that this library will also be referenced by another existing app that's used by clients who will have the 32-bit Trim client installed. Can the 64-bit .NET SDK dlls be used to communicate with Trim that's 32-bit? If so, then I can replace the dlls in my class library with the 64-bit ones. Otherwise, need to perhaps have two class libraries, one for communicating with 64-bit Trim and the other for communicating with 32-bit Trim??!
Yes, I can tell the console app to look in the Wow6432Node folder, though I've read that hardcoding it is not best practice :/ Still, the code can now find the connection string when the target platform is set to Any CPU. However, I still get the "side-by-side configuration" error...
I have an update on this problem. We realized that this error was occurring because the MS Visual C 2008 Redistributable Package wasn't installed on the workgroup server. This is listed as an installation pre-requisite in the Trim 7.1 Specifications document. Trim still seemed to be working fine on our Dev workgroup server, so I guess this component is only needed for the TRIM SDK?
The TRIM CD image comes with two versions of the VS2008 Runtimes, x86 and x64 - did you install just one or both? That might explain the new issues - It sounds like a HP.TRIM.SDK dependency relies on them?
Sorry I forget to mention our Trim version: 7.1 build 1157. Also, we now have the Visual C 2008 redistributable package installed, which is what we are supposed to according to the Trim 7.1 specifications document.
At the moment I'm trying different combinations of platform target in the project (e.g. Any CPU, x86) and switching between referencing the 32-bit and 64-bit dlls. So far, the 32-bit dlls always seem to give me the error "is not a valid Win32 application", while using the 64-bit dlls give the error "Could not load file of assembly 'HP.HPTRIM.SDK' ...or one of its dependencies. An attempt was made to load a program with an incorrect format."
TRIM .NET SDK setup is two-fold. First you need to access the correct HP.HPTRIM.SDK.dll file (32 or 64 bit). Second you need to be able to access all the other dll's it accesses. The first part uses .NET loading principals (curent directory, GAC, various sub directories - not 100% certain of the order). Looks like you are finding this. The second step does not use the .NET assembly load stuff, but uses the PATH variable, so my question would be, do you have the appropriate TRIM directory in the PATH? It is looking to me, from reading the thread that you don't - both parts of the SDK must be 32bit or 64 bit and the PATH variable should point to the appropriate directory for the other DLL's. I must admit to being slighty confused over whether you have installed both the 32 and 64 bit clients (which is fine) or just copied certain DLL's from them....
b37509886e