Ticket #145 (closed Defect: worksforme)

Opened 3 years ago

Last modified 3 months ago

64bit daemon fails to run on longhorn server x64

Reported by: Tank_Master (Jaeger_reg at hotmail) Assigned to: romw
Priority: Blocker Milestone: 5.10
Component: Client - Daemon Version:
Keywords: longhorn 64bit daemon Cc:

Description

The installation process for the 64bit client for both 5.9.4 and 5.9.5 works fine, however, as soon as the BOINC service starts, I get a windows pop-up saying "BOINC has encountered a problem and needed to be closed" and asks if you want to report the error. I do send the error just because it is a beta OS, and perhaps some compatibility issues can still be resolved, if this is indeed the issue. The instillation process never completes for BOINC never successfully starts.

My system is a core2duo e6700, 2 GB ram, nvidia 6800, 975 chipset. I had 5.9.4 fail under server longhorn enterprise x64 and 5.9.5 fail under the standard version. I have no AV, and just windows firewall. No added rolls are installed. If you need any added info, just contact me.

Change History

(in reply to: ↑ description ) 05/01/07 07:03:34 changed by Tank_MAster

I should mention that the 32bit BOINC installs and runs just fine. (5.9.5)

05/01/07 10:04:27 changed by romw

  • owner changed from davea to romw.

Could you by chance attempt to run boinc.exe from the commandline?

There is a good chance a more descriptive error will show up running it manually.

05/01/07 11:16:57 changed by Tank_Master

I wont be able to get to this until tonight. How would you recommend I go about trying this, given that its failing to install? My plan is to just wait for the install to error out "cannot start BOINC - retry or cancel" and while that message is still there, open up cmd and then try it that way. Do you think this will work? I will also try to get screenshots of the error messages and the dumps this time.

thx for the help and speedy reply.

05/01/07 11:28:56 changed by romw

I suspect that it'll install if you select a single user install. It just won't run for some reason.

My hunch is that the Windows program loader is failing to find some DLL or something like that, just running boinc.exe should show that kind of error.

If it is just the service mode install that is having problems, then we'll have to do more research.

05/01/07 11:51:32 changed by tank_master

Could having installed it into a previous BOINC directory containing the 32bit client lead to any problems?

05/01/07 19:29:52 changed by anonymous

I installed BOINC x64 into a new directory as a single user. It installed just fine, and strted fine. I do see that BOINC is running in the task manager, howver the projects (simap and SETI BEta) said -

5/1/2007 7:20:55 PM|boincsimap|Message from server: platform 'windows_x86_64' not found 5/1/2007 7:20:55 PM|boincsimap|Deferring communication for 1 days 0 hr 0 min 0 sec

BOINC did not download work (even x32bit)

attaching to projects and BAM! worked as expected.

I will next try installing as a service on the new folder.

05/01/07 20:14:16 changed by anonymous

ok, so I got sidetracked.. I used BAM! to attach EVERY project it could (40 in total). only 4 projects gave me work, all the rest said "platform not found"

05/01/07 20:27:39 changed by Tank_Master

I uninstall boinc and reinstalled it as a service into the new folder. Its working fine. It would appear that istalling BOINC x64 ontop the x32bit folder causes it to crash when starting. I will let the work I downloaded finish then reinstall the 32bit client so I can finish that work.

p.s., the previous 2 posts are mine as well.

05/02/07 11:10:03 changed by romw

When you say on top of a 32-bit folder do you mean c:\\Program Files (x86)\\BOINC?

Windows is doing some funny translation within that directory structure which may even attempt to redirect information in the application manifests. For instance attempting to load a 32-bit binary into a 64-bit process should cause a failure.

05/02/07 16:57:21 changed by tank_master

no, I dont install to the default directory

d:\boinc

05/02/07 17:29:39 changed by romw

If you still have the original directory structure around, could you zip up the exe's and dll's and send them back to me?

I would like to see if the installer replaced all the 32-bit binaries with their 64-bit counterparts.

05/02/07 22:23:35 changed by Tank_Master

My e-mail is in the first post. Send me and e-mail from an account you want to receive from and I will get you what I have. Note that since I have a climate project, the zip will be fairly large, so I will send an ftp link that you can download from.

When I installed the 64bit on top the 32bit, I first made a backup. When the install failed, I deleted the modified BOINC and restored the copy, and installed the latest 32bit client (5.9.5). It should be a simple thing to reinstall the 64bit into the directory and get the error. I have continuously upgraded in the same folder for the past several years, so there might be other things hanging around in it.

05/03/07 09:29:59 changed by romw

  • status changed from new to closed.
  • resolution set to worksforme.

Well the problem would only manifest itself on your computer and not mine.

The MSI installer technology stores what files were copied to what locations in the computers registry, so if the installer technology has gotten confused with whether or not to copy over the top of zlib, openssl, or libcurl it would only show up on your computer at the moment.

The MSI installer technology can choose to skip an upgrade of a file if it believes the destination file is already the version it is about to install or newer than the version it is trying to install. It is something of a hold out from the DLL hell days.

Installer to a new folder skips all of that, since it doesn't have a record of any of those files at the new location. So it goes ahead and copies all the files to the new location.

We'll have a new installer for the next major release of the client software, we hope that we can force the installation of all the files for every release, so stuff like this won't happen in the future.

If this page is incomplete or incorrect, please edit it or add it to the wiki to-do list. To do this, you must be logged in; click Login or Register above.