Start from the end of the file and work your way toward the beginning. If you still can’t start, look in the Second Life log file: C:\Users\\AppData\Roaming\SecondLife\logs.
SL CACHE VIEWER FILE ERROR INSTALL
See their wiki: Crashing During Install or Startup. There are a number of steps recommended by the Firestorm Team for solving the crash problem. I am assuming you have already manually cleared the cache. This is a pre-beta version of Linden Lab’s viewer. (era 2010)īefore tearing your computer apart, try installing the latest Development Viewer. See: Second Life Viewer Crashes While Starting. On Windows machines try a System Restore to a time when things were working.
SL CACHE VIEWER FILE ERROR DRIVER
Search the forum for your video card and driver version to see if others are having a similar problem. From time to time the latest driver is not the best and one must roll back one or two versions for things to work. For more info on that see: Overcoming Second Life Start-Up Crashes (Era 2009).Ĭheck to see if you have the latest video driver. If you have an ATI card try turning off the Catalyst AI in your ATI/AMD/Radeon control panel.
SL CACHE VIEWER FILE ERROR MAC
SSLCertificateFile /etc/httpd/conf/ssl.crt/server.crt Inc., OU=unit, verify that the ssl.conf configuration file is pointing to the correct files: # grep ^SSLCert /etc/httpd/conf.d/ssl.conf Inc., OU=unit, a third-party SSL certificate, the CN field should be FQDN in Subject, Subject: C=US, ST=North Carolina, O=Example Corp. Subject: C=US, ST=North Carolina, O=Example Corp. Issuer: C=US, ST=North Carolina, O=Example Corp. Verify that the Satellite or Proxy server has a fully-qualified domain name (FQDN), and that the CommonName ( CN) in the SSL certificate used by Apache is set to the FQDN:įor a self-signed Satellite certificate, the CN field should be FQDN for Issuer and Subject and these two fields should be matching, # grep CN /etc/httpd/conf/ssl.crt/server.crt