Solved Side-By-Side Configuration Error.

[oriontal]

I am getting a side-by-side configuration error. I worked through a post by niemiro (Richard). Couldn't get it working, decided to reimage my machine to factory. Even that didn't fix it. After reimaging I reinstalled all Vista Updates and the redistributes listed with no luck.
In the thread I was following, that leaves me at uploading sfcdetails.txt and sxstrace.txt. I am only having this issue with one program, so I ran the same program 3 times. After looking at the log files, it appears my sfcdetails only found an error with the ini for the sidebar ( which microsoft said to ignore ) and I couldn't make heads or tails out of sxstrace.txt.
If anyone is available to help, it would be greatly appreciated.

 

[niemiro]

Hello oriontal, and welcome to the Vista Forums!

Very, very well done on uploading those logs. You have done them perfectly, and have done very, very well by yourself!

As you have worked out, the SFC log is absolutely fine. Nothing to do there.

However, the albeit slightly confusing SXS Trace log has shown to me what I think is the problem.

I think that this problem is actually with the one piece of software you are having a problem with (NoScrubs IRIS)

I think that your issue lies in a Conflict between Processor Specific and Processor Agnostic assembly references.

What this actually means in normal English is that you are running 64bit Windows as you say that you are, and NoScrubs IRIS asks to start x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_d08d7bba442a9b36.manifest. However, later on, it asks to start either x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_d08d7bba442a9b36.manifest or the 64bit equivalent when required. This starts two copies of the same component, and causes your error.

Don't worry too much about this explanation. However, it is only my best theory. I need to check that this guess of mine is correct. I think that this is actually an error with the NoScrubs IRIS software, and if required, we can contact IRIS. However, before we contact the developers of that software, I shall see if there is anything I can do to fix it, or prove that it is the developer's problem to solve.

Right, I need to take a copy of the Manifest file for that software to analyse.

Please download the free Resource Extract (the normal, Unicode one) from here: ResourcesExtract - Extract files (bitmaps, icons, html files, and more) from dll files (Scroll down for the Download Link)

• Create a new folder on your Desktop called IRISClient, or any other name you prefer.
• Run Resource Extract.
• In Resource Extract, uncheck every check-box checked by default. Put a check back in Manifest Resources and Automatically Open Destination Folder.
• In FileName/WildCard, paste in C:\NoScrubs\NoScrubs IRIS\IRISClient.exe
• In Destination Folder, navigate to the new folder on your Desktop.
• Click Start.

As an example, my settings (but for a different .exe) would look like this:



Check in the folder on your Desktop. Hopefully, one or more .manifest files have been created (.manifest files can be opened with C:\Windows\notepad.exe, even if that is not the default program)

Either paste them here (preferably between [noparse]

[/noparse] tags), or right click on the whole folder > Send to > Compressed (zipped) folder, and upload that .zip file here.

Thanks a lot!

Richard

 

[oriontal]

Hi Richard,

And thanks for the speedy response. If I did the first files perfectly, it's because you explained how to do them so well in your other post.

Here is the file you requested.

I've been in contact with the people at NoScrubs since this was first became an issue, trying to help them resolve it as best I could. My user name there is hairfree. The link to that discussion if you are interested is NoScrubs.Net Discussions • View topic - Problems with new client? Read this first!

I'll also make them aware of this post so maybe they can follow along. Thanks again for the help.

John

 

[oriontal]

Richard,

While awaiting your reply, I read the how to ask a question. I realized there was a couple things missing from my first post, so here are the missing gaps.

Level of Computer Experience.
I have a bachelors in Computer Information Systems. I have 10 years programming experience, most of it is on the mainframe. My last work related Windows programming was Visual Basic 6 - so a while ago.

Link to Computer
Laptop Computers - Satellite A305-S6898

The Side-By-Side post I was following were
http://www.vistax64.com/general-discussion/283887-side-side-configuration.html#post1293020
and this one, scrolling down to see the correct redistributable packages to get since you list the x64 ones lower in thread.
side-by-side error - Windows 7 Forums

I also have Visual Studio 2005 Standard installed on my laptop. I got it from Microsoft in 2005/2006 when they were giving it away free for taking their surveys, seemed like too good of a deal to pass up.

 

[niemiro]

Hello again!

Looking at the manifest, it appears that it may actually well be with a piece of software on your computer, as you said about the Toshiba software.

unpacked PECompact version of IrisClient.exe

That was quite a clue that you were very good with computers! Not a huge number of people would have any idea where to start, although it really isn't very hard.

I haven't recommended this to anyone for ages, but how about trying a completely Clean Boot, or even seeing if this works in Safe Mode: How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

Can I just absolutely confirm that you have installed the x64 VC++ 2005 Redists. You should already have them if you have Visual Studio installed, but we do need to check.

However, I have a new theory! Do you have this file: C:\NoScrubIris\NoScrubs IRIS\Microsoft.VC80.CRT.MANIFEST?

Could you upload it?

Thanks a lot!

Richard

 

[oriontal]

Hi again, and thanks. I really appreciate the time and effort you've put in to this already.

Can I just absolutely confirm that you have installed the x64 VC++ 2005 Redists. You should already have them if you have Visual Studio installed, but we do need to check.

I'll go through and delete all my redist, reboot, and reinstall them in the order listed in the post I referenced. I tested the program in Safe Mode with networking, but it didn't work...then realized if I screwed up the redists it wouldn't have anyway, so I'll start back at the top. I'll include a screenshot of what it shows under programs in my next post. Not sure if that will be helpful, but it will at least show something is there.

*edit. Do I need to install both the x86 and x64 redist? I thought I only needed to install the x64 and that installing both would cause issues. I found a security update for the 2005 redist with Windows Update, and it installed both the x86 and x64 version, so I may not have the needed files on my computer after all.

I was not aware of the clean boot method, last time I did anything similar the instructions were to hold left shift while it booted. So, I learned something today.

I wanted to upload the file you requested while I check your other suggestions. I'll post back when I know more.

Oh, and I didn't mention about unpacking the program because it seemed unrelated. I did that because a few people said they were having problems with their antivirus picking it up, and I thought if there was a PEC2 section, it might need renamed. Their previous version of the client wasn't packed.

John.

 

[niemiro]

Hello again, John!

One little thing to try, based on those new logs. Is your issue fixed by renaming C:\NoScrubIris\NoScrubs IRIS\Microsoft.VC80.CRT.MANIFEST to C:\NoScrubIris\NoScrubs IRIS\Microsoft.VC80.CRT.MANIFEST.bak?

Do make sure you keep a backup though, (and obviously make sure to change the file extension to .bak, most likely requiring the viewing of File Extensions) If it doesn't help, just rename it back.

Thanks a lot!

Richard

 

[oriontal]

Hi Richard. Thanks again...I know this is getting a little frustrating for me, and I have the machine in front of me to try different things. I can just imagine how it is for you.

I will list what I have tried so far, and you can tell me if I have gone wrong somewhere.

1. Deleted, rebooted and reinstalled all x64 redist, rebooted again. I've included a picture called redist.jpg of what it looked like after I did this. Attempted to run program, no luck.

2. Clean boot. No luck.

3. Tried running without manifest.

4. Rechecked error log to see if the error message I was getting was the same or different from my first post, then realized I didn't include the error message I was getting. Here is the important parts of the error from Event Log.

1: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_d08d7bba442a9b36.manifest. Component 2: C:\NoScrubs\NoScrubs IRIS\Microsoft.VC80.CRT.MANIFEST

It looks like for some reason my system is trying to load 3053, instead of 4053.

5. Checked winsvs for 4053, to see if it existed. The only directory for 4053 is amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4053_none_88e046c92fae6f57 Not sure if this is correct or not.

6. Checked version of files in 4053, they were in fact the .dlls needed, tried copying them to noscrubs folder, didn't work, either with or without the manifest.

7. Installed x86 versions of redist. I wasn't sure how the system would handle this, but wanted to try it just in case I needed them.

I left the system in clean load state through all of this. Nothing runs at startup that isn't microsoft and is essential to this process. Running in Safe Mode didn't work either.

I was running Vista Service pack 2 before reimagine, I'm back to Vista Service Pack 1. I am going to reinstall Service Pack 2 to eliminate any issues that may have been in Service Pack 1.

 

[niemiro]

Hello again, John!

I know what you mean about frustrating. I am convinced that this is an issue for the developer to resolve, and we are just trying to find it to prove that it is their job to solve.

Now that we have completely ruled out VC++ Redist issues, let's leave those alone for a little while.

Can you please generate for me a new sxstrace.txt?


1: Make sure that C:\NoScrubIris\NoScrubs IRIS\Microsoft.VC80.CRT.MANIFEST is named just that.

2: Open an elevated Command Prompt. Elevated Command Prompt

3: Type sxstrace trace -logfile:sxstrace.etl into the Command Prompt window, and press enter ONCE! Set it continue to log!

4: Start the first program. Let it generate the error message, and OK out of the error message. Once the program has closed, rename C:\NoScrubIris\NoScrubs IRIS\Microsoft.VC80.CRT.MANIFEST.bak (ie add the .bak) and try the program once again. OK out of any error message.

5: Go back to the Command Prompt and press enter again to end the logging.

6: Type sxstrace parse -logfile:sxstrace.etl -outfile:%userprofile%\Desktop\sxstrace.txt and press enter.

Upload the file sxstrace.txt from your Desktop.

Please make sure to include sxstrace.txt in your next post.

Thanks!

Richard

P.S. I shall get back to you next post on everything which you have written and I have sort of ignored.

The error message in the Event Log changed because you .baked the manifest, I think.

The Application Embedded Manifest: 8.0.50727.4053 and 8.0.50727.762
The included manifest in the folder: 8.0.50727.4053

I shall just trace both of those paths, and maybe, just maybe, something interesting will come to light.

Richard

 

[oriontal]

Fixed.

Thanks Richard for all the time and effort you put in to this. In the end, it was my lack of understanding on how redist worked. I thought if I installed the x64, it took care of the x86 and that the .dlls were available for both.

I installed the x64 version of the files needed, but did not install the x86 version. I searched google for if I needed to install both x86 and x64, and got conflicting messages, but from what I could tell it would not screw your system up to install both, so I installed the x86 version for 4053. This fixed the issue.

*4053 is not one of the ones listed in the standard x86 and x64 downloads. I found it by searching for that specifically. The reason I had the x64 version is because that's the one that was listed on the NoScrubs page. I could have saved everyone a lot of time if I had downloaded both versions then, but I didn't know I needed both.

Thanks again, I feel like I wasted your time on this.

 

[niemiro]

It was no problem at all! I am really, really glad that the issue is now resolved! Thanks for letting me and future readers know what the solution was, and thanks a lot for the +rep!

Richard