Forum Discussion
Room System, version 4.4.25.0 does not start
Hi there,
A new version for Room System has been launched. On here Lenovo's device says:
Log Name: Skype Room System
Source: SRS-App
Date: 06/04/2020 10:23:29
Event ID: 1003
Level: Warning
Description:
App failed to launch error:This command cannot be run due to the error: Unknown error (0x80040900). HRESULT: -2146233079
Log Name: Skype Room System
Source: SRS-App
Date: 06/04/2020 10:23:29
Event ID: 1010
Level: Warning
Description:
Detected app registration error. Attempting manual app registration...
Log Name: Skype Room System
Source: SRS-App
Date: 06/04/2020 10:23:30
Event ID: 1009
Level: Information
Description:
Manual app registration complete
Log Name: Skype Room System
Source: SRS-App
Date: 06/04/2020 10:23:33
Event ID: 1001
Level: Error
Description:
App failed to successfully launch within the timeout period.
And on the logs it says:
04/06/2020 | 11:22:45 | 3924 | LVL_INFO :: Telemetry event: s4sh_AppState. AppSessionId = A9A083C8-1F62-41DA-8FE0-08D0D9C577F1. BluetoothAdvertisementEnabled = True. ContentCameraEnhancementEnabled = True. ContentCameraId = . ContentCameraInverted = False. IsTeamsDefaultClient = False. LastPasswordUpdate = 01/01/0001 00:00:00. PasswordRotationEnabled = False. PasswordUpdateFrequencyInDays = 30. Reason = Meeting mode at App Launch. TeamsMeetingsEnabled = True.
04/06/2020 | 11:23:29 | 3924 | LVL_ERROR :: [App.xaml.cs:723:OnSuspending] APP_SUSPEND
04/06/2020 | 11:23:29 | 3924 | LVL_INFO :: [App.xaml.cs:841:LogMemoryInformation] Memory: Usage:64, UsageLevel:Low, UsageLimit:9360MB, TotalWorkingSet:67MB
Any others have the similar experiences?
Petri-X
Our HP Slice which the blank screen start up then time out was fixed by this Microsoft powershell fix:https://support.microsoft.com/en-gb/help/4565998/teams-rooms-application-does-not-start-after-update
The log i saw it repaired the Skype installationThis is weird. At least you Petri-X Mika Seppänen and I seem to be Finnish. Can this be language / geography -based in some way?
Hit the similar thing with a new device after 4.4.41.0 update. Scriptlaunch log was also indicating that one of the powershell scripts was failing, I tried to run that manually and it failed with "cannot translate date/time" or something similar. Language and locale settings were Finnish.
I changed the admin account UI language and Locale to English (united states) and after reboot Room system was working again.
- It looks like Windows 10 Pro licensed devices are affected on my side. Enterprise editions all look good. Do you have Pro or Enterprise?
Gerco0426 same issue here - W10 Enterprise Smart Docks were fine, the same devices running W10 Pro all fail to launch MTR/SRS on restart.
All but one had updated to 4.4.41.0 over the weekend, that one was interrupted by a user and needed manual intervention.
Not great to come in on a Monday to find 60% of our VC units not working! Would love to know why I lost a big chunk of my day to this and how to reinstate auto-start of MTR.
We have Win 10 Ent. 1903 in Crestron Flex systems, 3 of 6 updated and all out of the game at the moment.
We have the same problem. Logitech Smartdock with Surface Pro. Any feedback from support to your tickets?
- same issue here with 4.4.41.0 on Logitech Smartdock devices. Have you received any update from MS? I also opened a case
Hey all, had the same thing here, on the 4.4.41.0 update and had to do the factory reset following this MS guide: https://docs.microsoft.com/en-us/microsoftteams/rooms/recovery-tool
It does work, keeps you up to date (as the system is still on 4.4.41.0) and takes about an hour to do... which is probably less time then you have already spent looking for an answer. Our system is very standard though so that might factor in total time.
Surface pro 5 in the logitech system.
Hi,
Same here, Crestron Flex devices ,now two devices have version 4.4.41.0 and together 4.4.25.0 and the problem is the same. Did you get solution for this?
I expect a comment from Crestron on this.From the proxies we could found that the new devices has started to use host:
But at the moment that gives the following message:
<h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0g7O+XgAAAABgB/YZk5V9SLL0abxT216mQkVSMzBFREdFMDcwOQBFZGdl
When take the same trace from older devices (4.3.42.0), we could see that host like that is not used.
No, just writing a case to MS.
So far 4.3.42.0 is the only working version. 4.4.41.0 have the same issue.
