Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-11845] Viewer version 4.0.4.314426 fails to install on Windows 10 #1964

Closed
1 task
sl-service-account opened this issue Apr 27, 2016 · 5 comments
Closed
1 task

Comments

@sl-service-account
Copy link

sl-service-account commented Apr 27, 2016

Steps to Reproduce

Upon restarting the SL viewer, the viewer install proceeded. Near the end, I received 10 Error messages, it was unable to install: winmm.ddl - win_crash_logger.exe - ssleay32.dll - msvcr120.dll - msvcp120.dll - libhunspell.dll - libeay32.dll - glod.dll - fmodex.dll - SecondLifeViewer.exe - each with the message: "Error opening or writing the file: [SEE attached image for an example]. For each one, I tried 'Retry', with a repeat of the Error, then clicked 'Ignore'.

I closed all SL windows, and downloaded Viewer version 4.0.3.312826 from the Alternative Viewers page, and went to install it. I received the same 10 Error messages.

Actual Behavior

I was running Viewer version 4.0.3.312826 on Windows 10
SL auto-downloaded Viewer version 4.0.4.314426, and attempted to install on the next restart.

Expected Behavior

Expected it to install without Errors/Error messages. - especially a second attempt direct download.

Other information

Attachments

Links

Duplicates

Original Jira Fields
Field Value
Issue BUG-11845
Summary Viewer version 4.0.4.314426 fails to install on Windows 10
Type Bug
Priority Unset
Status Closed
Resolution Duplicate
Reporter StarWolff2000 (starwolff2000)
Created at 2016-04-27T16:03:25Z
Updated at 2016-05-02T17:10:50Z
{
  'Business Unit': ['Platform'],
  'Date of First Response': '2016-04-27T14:17:38.653-0500',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'I was running Viewer version 4.0.3.312826 on Windows 10\r\nSL auto-downloaded Viewer version 4.0.4.314426, and attempted to install on the next restart.\r\n\r\n',
  'What were you doing when it happened?': 'Upon restarting the SL viewer, the viewer install proceeded. Near the end, I received 10 Error messages, it was unable to install: winmm.ddl - win_crash_logger.exe - ssleay32.dll - msvcr120.dll - msvcp120.dll - libhunspell.dll - libeay32.dll - glod.dll - fmodex.dll - SecondLifeViewer.exe - each with the message: "Error opening or writing the file: <filename> [SEE attached image for an example]. For each one, I tried \'Retry\', with a repeat of the Error, then clicked \'Ignore\'.\r\n\r\nI closed all SL windows, and downloaded Viewer version 4.0.3.312826 from the Alternative Viewers page, and went to install it. I received the same 10 Error messages.',
  'What were you expecting to happen instead?': 'Expected it to install without Errors/Error messages. - especially a second attempt direct download.',
}
@sl-service-account
Copy link
Author

Kyle Linden commented at 2016-04-27T19:17:39Z

Hi StarWolff2000,

You are using a Second Life Release Candidate viewer that was selected for you. You may be encountering a bug in that viewer.

It is not unheard of for there to be stuck processes from the prior instance of Second Life running that prevent installing a new version.

Win_crash_logger.exe is one of the common culprits here.

Please right click on your windows task bar at the bottom of your screen and click Start Task Manager.
If present click the button at the bottom of the Task Manager to Show processes from all users.

Do you see any of the following still running when you believe you have quit Second Life?

  • SecondLifeViewer.exe
  • SLVoice.exe
  • SLPlugin.exe
  • LLCEFlib_host.exe
  • Win_crash_logger.exe

If you do, select the process and click the End Process button.

Now you should be able to install any of the viewers from the Alternate Viewers download page http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers or the current release from http://secondlife.com/support/downloads/.

Please let us know if this helped at all and press the Info Provided button.

Thanks!

@sl-service-account
Copy link
Author

StarWolff2000 commented at 2016-04-28T07:43:49Z, updated at 2016-04-28T07:46:53Z

===SOLVED===

Thank you for reply, Kyle Linden

Steps I took BEFORE I found the solution:
I killed any/all SL-related processes in Task Manager, before each:

1st I re-downloaded the 4.0.4.314426, and attempted to install - still errors.

  • after the failed installation, the login screen opens, and SL begins to autoupdate, the installation of which likewise has the same errors.

    2nd, I re-downloaded 4.0.3.312826, and attempted to install - still errors.

  • after the failed installation, the login screen opens, and SL begins to autoupdate, the installation of which likewise has the same errors.

    Don't bother with the above, just do this:
    StarWolffs Solution:
    I killed any/all SL-related processes in Task Manager
    I opened \Program Files (x86)\SecondLifeViewer in explorer
    I made a new folder, and moved all those mentioned files into that folder
    I installed the latest version - NO error messages and now my grateful-for-Governor-Linden's-Realm ass is back globe-trotting the Linden-Worlds like a buzz-buzz-busy-bee flying through the air, hopping region-to-region.

@sl-service-account
Copy link
Author

Kyle Linden commented at 2016-04-28T18:47:22Z, updated at 2016-04-28T18:48:03Z

Hi StarWolff2000,

That's a very interesting solution you worked out and definitely something we need to investigate further.
Will you please confirm whether or not you have Unicode in your Windows Username.
Additionally, will you confirm that you were starting with viewer build 4.0.3.312816 (current release viewer) and not 4.0.3.312826.

Now that you can login will you please add the Help > About Second Life information to the environment field. This information will help us to reproduce the situation in which you encountered the install problems.

Please press the Info Provided button when you update.

Thanks!

@sl-service-account
Copy link
Author

StarWolff2000 commented at 2016-04-29T13:25:18Z

Hey Hy, Kyle Linden

No, I'm not using Unicode in either my Windows Username nor SL username

And yes, correction: I started with Viewer build 4.0.3.312816 (current release viewer) from the Downloads page

Then SL auto-downloaded Viewer version 4.0.4.314426, and I got the errors
I Downloaded Viewer version 4.0.4.314426 from the Alternative Viewers page (just in case the auto-download was corrupt), and got the errors again
I then downloaded Viewer version 4.0.3.312816 (current release viewer) from the Downloads page, and I got the errors
I moved the offending files, installed Viewer version 4.0.4.314426, and it installed just fine.

It is possible the issue might be because I did not kill win_crash_logger.exe, (not recognizing it as an SL process until I mucked around in the SecondLifeViewer folder), when I first started encountering the errors. [suggestion: rename it to SL_crash_logger.exe]

ABOUT Second Life:

Second Life 4.0.4.314426 (Second Life Release)
Release Notes

You are at 201.3, 250.7, 24.6 in Baku located at sim10295.agni.lindenlab.com (216.82.50.17:13007)
SLURL: http://maps.secondlife.com/secondlife/Baku/201/251/25
(global coordinates 258,761.0, 256,251.0, 24.6)
Second Life Server 16.03.31.313341
Retrieving...

CPU: AMD A4-5000 APU with Radeon(TM) HD Graphics (1499.98 MHz)
Memory: 3534 MB
OS Version: Microsoft Windows 8 64-bit (Build 9200) compatibility mode. real ver: 10.0 (Build 10011)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: AMD Radeon HD 8330

Windows Graphics Driver Version: 8.17.0010.1452
OpenGL Version: 4.2.13431 Compatibility Profile Context 16.150.2211.0

J2C Decoder Version: KDU v7.2
Audio Driver Version: FMOD Ex 4.44.31
LLCEFLib/CEF Version: 1.5.3-(CEF-WIN-3.2526.1347-32)
Voice Server Version: Vivox 4.6.0017.22050

Packets Lost: 27/4,411 (0.6%)

@sl-service-account
Copy link
Author

Kyle Linden commented at 2016-05-02T17:10:50Z

Hi StarWolff2000,

Thank you for the update. Given this information it does seem like a duplicate of BUG-7873. We'll do additional testing on our side to rule out any Win10 install issues.

Thank you

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant