Windows Native Install

Transcription

1 ROES Support 101

2 ROES Client Install Best to always use the native installers ROES Web Start exists for Windows and Mac Page we host will differ for Windows/Mac to offer proper install

3 Windows Native Install

4 OS X Native Install

5 Native Install Benefits Java has introduced several bad bugs in last couple of years Java 8u31 prevented proper SSL checks RWS eliminates Java update concerns as it locks in a Java version ONLY for ROES use Link on your site should not link directly to launch.jnlp just the launch folder name and / Modify links with to use - high availability cluster

6 Windows Basics Launch.msi is native installer, will prompt for user approval in Windows Some Vista, Win 7 and Win 8 systems will be 32 bit, especially if they were upgraded from XP XP 14 years old now and not considered secure due to lack of Windows Updates for 2 years Paths C:\ProgramData\SWROES and C:\Program Files (x86)\roes

7 OS X Basics Launch.dmg is native install package Apple only truly supports 3 versions at a time, so 10.9 thru (10.8 considered unsupported as of Sept 2015) DMG unpacks.app file and some hidden files to be used for install Both JWS and RWS can exist on system, RWS if installed 2 nd icon will have alias in label

8 OS X RWS Basics Main area is.roesenginecache This is hidden folder, so must use Finder and Go Go to Folder in top menu Enter in ~/.ROESEngineCache Same steps to get to ~/.roescache and.labname folder in OS X when needed

9 ROES Client Support Basics Information to get on 1 st call Windows or Mac OS, and what version Always get the roeslog Try to get install method - RWS or JWS (log will help to show this) New install or existing (log should show as well) If issue occurs during usage, MUST get roeslog to analyze

10 ROES Client Log - The Basics ROES v9 starts logging immediately ROES v8 started logging after templates file downloaded and parsed Available from Diagnostics Show Log button in Home pane or on drive in.labname folder (hidden on OS X) Shows Client version, JRE version, Operating System and Memory Allocation:

11 ROES Log - The Basics - JWS 2) 2016/04/09:16:31:56 Client ) 2016/04/09:16:31:56 Java 1.8.0_73 4) 2016/04/09:16:31:56 OS Windows en_us 5) 2016/04/09:16:31:56 Memory 12/683 MB, 8 processors.

12 ROES Log - The Basics - RWS 2) 2016/04/09:16:37:44 Client ) 2016/04/09:16:37:44 Java 1.8.0_05 4) 2016/04/09:16:37:44 OS Windows en_us 5) 2016/04/09:16:37:44 Memory 27/3925 MB, 8 processors.

13 ROES Log - The Basics OS X 2) 2016/04/09:17:35:12 Client ) 2016/04/09:17:35:12 Java 1.8.0_60 4) 2016/04/09:17:35:12 OS Mac OS X en_us 5) 2016/04/09:17:35:12 Memory 8/910 MB, 8 processors.

14 Common Error OS X Initialization Error Delete.ROESEngineCache folder, re-execute launch.dmg and run fresh install could an issue making connection to web to pull down install or missing pieces of app (if current users) Rights issue - may need to copy.app file to Applications folder and execute from there instead of folder from dmg unpack

15 Possible Errors - Windows Initialization Error Delete SWROES folder and re-execute launch.msi NullPointer Exception Delete ~/.roescache and relaunch through icon as this should occur post-engine install

16 Possible Errors - Windows ProgramData folder hidden in Windows, to see must select to change View Options:

17 Common Issues Customer.xml and other xml files (even colors.xml) can get corrupted by bad shutdown Log will show error reading customer.xml or other Content not allowed in prolog ; delete it and launch should work In the.labname folder the labname.properties file may have old screen locations and last used folder info, so if customers are hanging trying to read in images deleting can have clean start

18 Templates File Not Found Startup may fail due to templates file not found (most common cause is lab web site down!): 10)2016/04/10:11:43:46 Logging to: C:\Users\smbar\.RUGTest1\roeslog.log 11) 2016/04/10:11:43:46 ProductsFactory.notifyOfTemplatesFileSelected: enc 12)2016/04/10:11:43:46 Download & DOM XML ( java.io.filenotfoundexception: enc

19 Templates File Corruption Occasionally a change to the templates file can corrupt it (odd characters, etc.) Log will show bad read of the file: 7) 2016/03/15:16:13:00 ProductsFactory: All catalog parsing [ 8) 2016/03/15:16:13:00 Exception occurred:premature end of file. 9) 2016/03/15:16:13:00 Parse cached XML [ [Fatal Error] :1:1: Premature end of file. org.xml.sax.saxparseexception; linenumber: 1; columnnumber: 1; Premature end of file.

20 Memory Basics JWS memory based on value in launch.jnlp; RWS in Windows 64 bit editions uses 4GB 64 bit Java allows exceeding 1GB and even installed RAM amount Render via Designer may fail with lower memory and larger images and java heap space error in roeslog; RWS in 64 bit Windows should be fine 32 bit systems no easy resolution, can try to bump jnlp to 1GB max memory do we still have a lot of XP users??

21 Preferences Stack Tabs in Sizes more room for templates/os X-like appearance Search enclosed folders unchecked prevents overpopulating the thumbs pane Uploads pane check time to retain old orders

22 Home Pane - Diagnostics Diagnostic Tools offer fresh start options Clear Preferences will reset things like hold images, hold options, etc. to the new install defaults Clear Caches will remove program cache and cached image files from.roescache

23 Startup Tips The.roescache folder/subfolders still holds startup files as well as lab-defined images (maskimages, layoutimages, etc.) Clearing.roescache can help with launch issues (such as a corrupted templates file) or rare occurrences where Sizes aren t properly showing icon images for cards or books