• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

More Rosetta frustrations!

O

OhioDude

Diamond Member
I just upgraded a DC in my fleet from NT4 Server to Win2K server. R@H was running fine since last December on this machine. Following the upgrade, every single workunit aborts with the following message:

Unrecoverable error for result <blah blah blah> (There are no child processes to wait for. (0x80) - exit code 128 (0x80))

The event viewer contains the following entries for each workunit as it aborts:

rosetta_5.01_windows_intelx86.exe - Application Error : The application failed to initialize properly (0xc0000142)

This is Windows 2000 Server, SP4. All patches are up to date. The only purpose this machine serves is a DC and a file server. No other applications are installed. Hardware is an AMD XP2000+, 1GB RAM.

I have done the following:

1. Completely uninstalled BOINC, removed the BOINC folder, and reinstalled BOINC.

2. Installed .NET framework 1.1

3. Installed .NET framework 2.0

There is no joy in Mudville. 🙁
 
Originally posted by: Insidious
Windows 2000 server does not meet the system requirements set out by Rosetta

Sorry for the bad luck OD 🙁

-Sid
Click to expand...

Hmmm... I'll have to tell that to the three other Win2K Server systems I have Rosetta running on just fine. 😉

Interestingly, I have a Win2K Pro machine that I never could get Rosetta running on that suffered from the same symptoms. That one I wrote off months ago because I thought it was due to old hardware...

 
I was just trying to answer the post with a possible explanation of what might be going wrong. The System Requirements listed for Windows are WindowsXP, Windows 2000, and windows 2003 server.

I understand your frustration, but shooting the messenger won't help

-Sid
 
Originally posted by: OhioDude
Originally posted by: Insidious
Windows 2000 server does not meet the system requirements set out by Rosetta

Sorry for the bad luck OD 🙁

-Sid
Click to expand...

Hmmm... I'll have to tell that to the three other Win2K Server systems I have Rosetta running on just fine. 😉

Interestingly, I have a Win2K Pro machine that I never could get Rosetta running on that suffered from the same symptoms. That one I wrote off months ago because I thought it was due to old hardware...
Click to expand...

I've got Rosetta running on a win2k pro machine with no problems.

Can't be your hardware since it was fine with NT4.

Perhaps it's a driver problem?

Tried the "reset project" button yet or tried different versions of BOINC?

Stabs in the dark here😉
 
Originally posted by: Insidious
I was just trying to answer the post with a possible explanation of what might be going wrong. The System Requirements listed for Windows are WindowsXP, Windows 2000, and windows 2003 server.

I understand your frustration, but shooting the messenger won't help

-Sid
Click to expand...

Perhaps you didn't notice the 😉 in my reply...

So here it is again: 😉
Along with a huge smilie: 😀
And a little smilie: 🙂
And a cookie to thank you for your attempt to help: :cookie:
 
Hmm, "There are no child processes to wait for"... can't say for certain, but one possibility is a "missing" dll...

There's multiple *.dll's in the main BOINC-directory, among these msvcp71.dll and msvcr71.dll, try copying these 2 files to your windows-directory, and see if this fixes your problem...
 
I agree it's probably a .DLL issue. It's definitely not a system requirement problem. NT wasn't in the list but obviously it was running, and I just joined one of my "Windows 2000 Server" rigs to the project a couple minutes ago: YU

 
Tried moving the DLL's to the <windows> folder - No luck.
Tried moving the DLL's to the <windows>\System32 folder - No luck.
Uninstalled BOINC and re-installed again - No luck.

I have tried two different versions of BOINC. Both behave the same.
 
When installing BOINC, how are you doing it? Most folks I know with servers choose the Service Install but I use the Shared install.. might make a difference.
 
Einstein@Home crashes on every workunit, too.

Would appear to be a BOINC'ing problem.

I have tried two versions of BOINC and both behave the same.

Any suggestions?
 
Which versions of BOINC have you tried? 5.2.xx or 4.45.xx or the latest?

When doing the uninstall, have you checked that all traces of BOINC were gone? Have you rebooted after uninstalling? I am asking because I have had problems uninstalling BOINC on a couple of comps because the processes were not ended in a proper way; had to reboot the computer, clean all BOINC-stuff out and then reinstall.

It seeems to that you have had BOINC running on that computer before you upgraded. Did you do a migration (i.e. went from NT4 to Win2K) or did you do a new clean install (e.g. formatted the HDD or changed it or something similar...). A migration may have left some old drivers (which may work OK with Win 2K but not with BOINC.

I hope this gives you inspiration to solve the problem ...

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top