Windows Installer

[paulie]

Hi. I tried to upgrade from Ver 9.0.4.224 to Version 9.1.10 and keep getting an error. Please see Log details below. Any help would be most appreciated. I couldn't get the Log file to upload.

[1B1C:20A4][2018-10-20T08:53:48]i001: Burn v3.10.2.2516, Windows v10.0 (Build 17134: Service Pack 0), path: C:\Users\Paul\AppData\Local\Temp\{A4AE8A96-8C87-4253-8187-4B83F0A45224}\.cr\SageTVSetup_9.1.10(1).exe
[1B1C:20A4][2018-10-20T08:53:48]i000: Initializing string variable 'InstallFolder' to value '[ProgramFilesFolder]SageTV'
[1B1C:20A4][2018-10-20T08:53:48]i000: Initializing string variable 'SageInstallerVersion' to value '1.013'
[1B1C:20A4][2018-10-20T08:53:48]i009: Command Line: '-burn.clean.room=C:\Users\Paul\Downloads\SageTVSetup_9.1.10(1).exe'
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Paul\Downloads\SageTVSetup_9.1.10(1).exe'
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\Paul\Downloads\'
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Paul\AppData\Local\Temp\SageTV_20181020085348.log'
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting string variable 'WixBundleName' to value 'SageTV'
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting string variable 'WixBundleManufacturer' to value 'TheSageTVAuthors'
[1B1C:0F78][2018-10-20T08:53:48]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033
[1B1C:0F78][2018-10-20T08:53:48]i000: Setting version variable 'WixBundleFileVersion' to value '9.1.10.0'
[1B1C:20A4][2018-10-20T08:53:48]i100: Detect begin, 5 packages
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'VersionNT64' evaluates to false.
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'NOT VersionNT64' evaluates to true.
[1B1C:20A4][2018-10-20T08:53:48]i000: File search: GetAC3X86onX86Exists, did not find path: AC3Filter\ac3filter.ax
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting numeric variable 'ac3x86Exists' to value 0
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'VersionNT64' evaluates to false.
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'VersionNT64' evaluates to false.
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'NOT VersionNT64' evaluates to true.
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting numeric variable 'vc10x86Exists' to value 1
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'NOT VersionNT64' evaluates to true.
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting version variable 'vc10x86Version' to value '10.0.40219.325'
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'VersionNT64' evaluates to false.
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'VersionNT64' evaluates to false.
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'NOT VersionNT64' evaluates to true.
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting numeric variable 'vc14x86Exists' to value 1
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'NOT VersionNT64' evaluates to true.
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting version variable 'vc14x86Version' to value '14.0.23506.0'
[1B1C:20A4][2018-10-20T08:53:48]i000: Setting string variable 'JavaCurrentVersion' to value '1.7'
[1B1C:20A4][2018-10-20T08:53:48]i102: Detected related bundle: {e57ab375-2419-4e82-a06d-f8fad82c403d}, type: Upgrade, scope: PerMachine, version: 9.0.4.224, operation: MajorUpgrade
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'JavaCurrentVersion AND (JavaCurrentVersion >= v1.7)' evaluates to true.
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'vc10x86Exists AND vc10x86Version >= v10.0.30000' evaluates to true.
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'vc14x86Exists AND vc14x86Version >= v14.0.23026' evaluates to true.
[1B1C:20A4][2018-10-20T08:53:48]i103: Detected related package: {33FFAEF2-4B1E-4650-8E62-44D36DA2B5A5}, scope: PerMachine, version: 9.0.4.224, language: 0 operation: MajorUpgrade
[1B1C:20A4][2018-10-20T08:53:48]i052: Condition 'ac3x86Exists' evaluates to false.
[1B1C:20A4][2018-10-20T08:53:48]i101: Detected package: Java7Runtime, state: Present, cached: None
[1B1C:20A4][2018-10-20T08:53:48]i101: Detected package: vc100, state: Present, cached: None
[1B1C:20A4][2018-10-20T08:53:48]i101: Detected package: vc140, state: Present, cached: None
[1B1C:20A4][2018-10-20T08:53:48]i101: Detected package: SageTVSetupMSI, state: Absent, cached: None
[1B1C:20A4][2018-10-20T08:53:48]i101: Detected package: ac3filter, state: Absent, cached: Complete
[1B1C:20A4][2018-10-20T08:53:48]i199: Detect complete, result: 0x0
[1B1C:0F78][2018-10-20T08:53:53]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1
[1B1C:20A4][2018-10-20T08:53:53]i200: Plan begin, 5 packages, action: Install
[1B1C:20A4][2018-10-20T08:53:53]w321: Skipping dependency registration on package with no dependency providers: Java7Runtime
[1B1C:20A4][2018-10-20T08:53:53]w321: Skipping dependency registration on package with no dependency providers: vc100
[1B1C:20A4][2018-10-20T08:53:53]w321: Skipping dependency registration on package with no dependency providers: vc140
[1B1C:20A4][2018-10-20T08:53:53]i000: Setting string variable 'WixBundleRollbackLog_SageTVSetupMSI' to value 'C:\Users\Paul\AppData\Local\Temp\SageTV_20181020085348_000_SageTVSetupMSI_rollback.log'
[1B1C:20A4][2018-10-20T08:53:53]i000: Setting string variable 'WixBundleLog_SageTVSetupMSI' to value 'C:\Users\Paul\AppData\Local\Temp\SageTV_20181020085348_000_SageTVSetupMSI.log'
[1B1C:20A4][2018-10-20T08:53:53]w321: Skipping dependency registration on package with no dependency providers: ac3filter
[1B1C:20A4][2018-10-20T08:53:53]i000: Setting string variable 'WixBundleLog_ac3filter' to value 'C:\Users\Paul\AppData\Local\Temp\SageTV_20181020085348_001_ac3filter.log'
[1B1C:20A4][2018-10-20T08:53:53]i201: Planned package: Java7Runtime, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[1B1C:20A4][2018-10-20T08:53:53]i201: Planned package: vc100, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[1B1C:20A4][2018-10-20T08:53:53]i201: Planned package: vc140, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[1B1C:20A4][2018-10-20T08:53:53]i201: Planned package: SageTVSetupMSI, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[1B1C:20A4][2018-10-20T08:53:53]i201: Planned package: ac3filter, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: None, cache: No, uncache: No, dependency: None
[1B1C:20A4][2018-10-20T08:53:53]i207: Planned related bundle: {e57ab375-2419-4e82-a06d-f8fad82c403d}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None
[1B1C:20A4][2018-10-20T08:53:53]i299: Plan complete, result: 0x0
[1B1C:20A4][2018-10-20T08:53:53]i300: Apply begin
[1B1C:20A4][2018-10-20T08:53:53]i010: Launching elevated engine process.
[1B1C:20A4][2018-10-20T08:54:10]i011: Launched elevated engine process.
[1B1C:20A4][2018-10-20T08:54:10]e000: Error 0x800700e8: Failed to wait for child to connect to pipe.
[1B1C:20A4][2018-10-20T08:54:10]e000: Error 0x800700e8: Failed to connect to elevated child process.
[1B1C:20A4][2018-10-20T08:54:10]e000: Error 0x800700e8: Failed to actually elevate.
[1B1C:20A4][2018-10-20T08:54:10]e000: Error 0x800700e8: Failed to elevate.
[1B1C:20A4][2018-10-20T08:54:11]i399: Apply complete, result: 0x800700e8, restart: None, ba requested restart: No

[jusjoken]

Did you try running the installer as admin?

Seems its having issues elevating.

k

[waylo]

After upgrading to 9.1.10, I've noticed more spinning circles of patience, mostly (?only) when viewing on a client. I'll try to grab a relevant log as soon as it happens again.

Anyone else with this issue?

[perfessor101]

I have similar but on the client, server and extenders

I’m trying to automate a google drive folder with logs from the past 7 days for debugging

[wnjj]

What version did you update from. The latest update was very minor, according to the update log.

If it’s a memory issue, be patient a 64-bit version is coming soon!

[waylo]

I updated from just the last one, v9.1.9.

I was surprised also, given the minimal logged changes.

I've yet to revert back to 9.1.9 to see if that truly is the reason. Though I have made no other changes to my system.

[photon]

Originally Posted by waylo

I updated from just the last one, v9.1.9.

I was surprised also, given the minimal logged changes.

I've yet to revert back to 9.1.9 to see if that truly is the reason. Though I have made no other changes to my system.

In the past one time I had a significant problem with spiny circle and slow response and it was suggested that I try rebooting my Ethernet switch. That resolved my issue immediately. Worth trying a reboot of everything before you try downgrading IMHO. I have been running 9.10 for weeks and have not noticed any significant change in behavior from the over year old version I upgraded from. I have a dedicated sage server and play back on HD300s.

[waylo]

Good idea, would have tried the reboot if I had seen your message sooner.

I did revert though and immediately found that the spinning circles returned to their 'normal' frequency, which is to say, far less.

What is your server machine?

[wnjj]

That’s interesting. To be fair, the “minor” update did actually affect the memory usage by storing the show titles and descriptions in UTF (i.e. 2-byte per char java strings) instead of just byte arrays. It’s possible that is pushing your heap over its limits. If you are so inclined, look at the memory usage under the system info with both versions and see if there’s a measurable difference.

In any event, a 64-bit Windows server will mean you can crank up the heap size and make this go away, even for the occasional 9.1.9 spinning circles.

[waylo]

Originally Posted by wnjj

That’s interesting. To be fair, the “minor” update did actually affect the memory usage by storing the show titles and descriptions in UTF (i.e. 2-byte per char java strings) instead of just byte arrays. It’s possible that is pushing your heap over its limits. If you are so inclined, look at the memory usage under the system info with both versions and see if there’s a measurable difference.

In any event, a 64-bit Windows server will mean you can crank up the heap size and make this go away, even for the occasional 9.1.9 spinning circles.

Good points. Do you have a recommendation on heap size?

[wnjj]

Originally Posted by waylo

Good points. Do you have a recommendation on heap size?

I run my at the default (768M) with 2 extenders and a vanilla GUI setup. Pushing it higher has shown to have mixed results since increasing the heap cuts into the native memory. There's only 2GB available to 32-bit processes for all of the native and Java code. When the 64-bit Windows version is complete and released your heap can can be several GB if needed.

[waylo]

A couple more questions in preparation for the 64-bit version...

The Java version installed would need to be 64-bit then, correct?

OpenDCT, I think that could still be the 32-bit version?

[wnjj]

Originally Posted by waylo

A couple more questions in preparation for the 64-bit version...

The Java version installed would need to be 64-bit then, correct?

OpenDCT, I think that could still be the 32-bit version?

Yes for Java and I'm pretty sure yes, OpenDCT runs as it's own app.

[graywolf]

Originally Posted by wnjj

What version did you update from. The latest update was very minor, according to the update log.

If it’s a memory issue, be patient a 64-bit version is coming soon!

Woo Hoo

Can't wait. Hopefully it'll be an early Christmas present for my wife.
Especially if able to bump up the heap and it takes care of the sporadic spinning circles.

[KarylFStein]

Originally Posted by waylo

A couple more questions in preparation for the 64-bit version...

The Java version installed would need to be 64-bit then, correct?

OpenDCT, I think that could still be the 32-bit version?

There's a 64-bit version of OpenDCT. I'm not sure how it determines which JAVA to use, but seems like I had issues that required some manual configuration changes to get things to work when I tried to have both 32-bit and 64-bit versions of JAVA installed on Windows. If it stops working after installing 64-bit JAVA you could just uninstall the 32-bit version and install the 64-bit one...

[photon]

Originally Posted by waylo

Good idea, would have tried the reboot if I had seen your message sooner.

I did revert though and immediately found that the spinning circles returned to their 'normal' frequency, which is to say, far less.

What is your server machine?

It is an HP EX495 with 4 GB RAM running Windows home server 2011. Having read the subsequent posts I checked the java heap size setting in the registry. Max Java Heap size is set to 1024. While recording 1 show Sage reports Java heap size (used/total /max) 724/1038/1038. Checking server memory I see that 3.16 GB is in use. WHS 2011 is a 64 bit OS.

[waylo]

Mine is set to 1024 as well.

Without anything going on in Sage, my JVM Heap size info was 402/615/1038 (on 9.1.9).

When another version pops up (9.1.11?), maybe I'll upgrade to 9.1.10 first to get a screen grab of its memory usage before upgrading once again.

[wnjj]

Originally Posted by waylo

Mine is set to 1024 as well.

Without anything going on in Sage, my JVM Heap size info was 402/615/1038 (on 9.1.9).

When another version pops up (9.1.11?), maybe I'll upgrade to 9.1.10 first to get a screen grab of its memory usage before upgrading once again.

Any revisions after 9.1.10 will likely have the same memory footprint. If you want to help measure the difference from 9.1.9, save the sage.jar file somewhere before upgrading to 9.1.10. To revert back after upgrading you can just shut down sage and revert the sage.jar back to the 9.1.9 version since that's the only change.

[EnterNoEscape]

Originally Posted by KarylFStein

There's a 64-bit version of OpenDCT. I'm not sure how it determines which JAVA to use, but seems like I had issues that required some manual configuration changes to get things to work when I tried to have both 32-bit and 64-bit versions of JAVA installed on Windows. If it stops working after installing 64-bit JAVA you could just uninstall the 32-bit version and install the 64-bit one...

It works based on whatever version is defined in the PATH environment variable. That usually translates to whatever Java you installed last. I wish JSW was a little more intelligent about this.

[davidk21770]

Originally Posted by wnjj

Any revisions after 9.1.10 will likely have the same memory footprint. If you want to help measure the difference from 9.1.9, save the sage.jar file somewhere before upgrading to 9.1.10. To revert back after upgrading you can just shut down sage and revert the sage.jar back to the 9.1.9 version since that's the only change.

I can't even run 9.1.10. All I get is the spinning circle. If it finally loads, after a few operations, it goes to the continuous spinning circle. I was able to access sage service using my tablet/mini-client, but I didn't do much of a test. Now that I see this, I will experiment with the heap size, but I'm pretty sure that it's already way up there. So right now, I"m stuck at 9.1.9.

Edit: I had JVMMaxHeapSizeMB set to 0400 (1024), the max. SageService won't run if it's set to 0300. SO, I'm maxed-out with 9.1.9 and can't upgrade to 9.1.10 with the current memory use under windows.

Another edit: Any suggestions? I wonder if I have unintentionally installed a plugin that uses a lot of memory. Any way to check? (Or it could just be that I have a LOT of shows).