Music - Sibelius 5
From Jonsdocswiki
Sibelius 5 can be licensed in either standalone or "license server" mode. When using a license server, the server limits the number of copies of Sibelius 5 that can run concurrently.
Contents |
Setting the license server in registry
If you've got a lot of clients to install, it would take a while to load each one, type the license server address and port and load the program. By adjusting a key in the registry, this can be done quickly and easily for all clients.
- Open the Windows Registry Editor
- Expand the HKEY_LOCAL_MACHINE category by clicking the plus symbol
- Expand software
- Expand Sibelius Software
- Expand Sibelius 5
- Expand Preferences
- Expand LicenseServerInfo
- There should be one key in there already: (Default) REG_SZ - edit that key so the data reads the correct server info (e.g. licenses:7313
- Exit the registry editor
- Launch Sibelius 5
Program Errors
Invalid short file names
Problem
When a limited user runs Sibelius they are presented with an error, for example: 03-ytesting is not a valid short file name. There may also be errors in the Windows event log:
Windows Event Log errors
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11325
Date: 29/01/2008
Time: 14:57:54
User: DOMAIN\03-ytesting2
Computer: TESTBEDV2
Description:
Product: Sibelius 5 -- Error 1325. '03-ytesting2' is not a valid short file name.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 43 32 33 42 38 43 33 {C23B8C3
0008: 30 2d 45 30 35 45 2d 34 0-E05E-4
0010: 43 42 35 2d 38 31 38 38 CB5-8188
0018: 2d 46 32 37 43 43 33 42 -F27CC3B
0020: 32 44 44 33 45 7d 2DD3E}
Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 0
Date: 29/01/2008
Time: 14:57:17
User: N/A
Computer: TESTBEDV2
Description:
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Unable to open shim database version registry key - v2.0.50727.00000.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 29/01/2008
Time: 14:57:17
User: DOMAIN\03-ytesting2
Computer: TESTBEDV2
Description:
Detection of product '{C23B8C30-E05E-4CB5-8188-F27CC3B2DD3E}', feature 'DefaultFeature' failed during request for component '{79D49330-492B-0531-C170-8D884682AE9D}'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 29/01/2008
Time: 14:57:17
User: DOMAIN\03-ytesting2
Computer: TESTBEDV2
Description:
Detection of product '{C23B8C30-E05E-4CB5-8188-F27CC3B2DD3E}', feature 'DefaultFeature', component '{6A36DFA4-83F5-FC67-DDB2-0AD22AB03E71}' failed. The resource 'HKEY_CURRENT_USER\Software\Sibelius Software\Sibelius 5\{6A36DFA4-83F5-FC67-DDB2-0AD22AB03E71}\DesktopFolder' does not exist.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The registry key in question points: DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Resolution
Browsing the edugeek forums in this thread suggests an update is available from the Sibelius website to Sibelius 5.1. The forum post suggests the update causes other problems although these seemed to be resolved by the time I deployed the upgrade. The readme states:
Installing Sibelius
- Problems with running Sibelius in a different user account to that in which it was installed have now been resolved (Windows only).
Sibelius are aware of the credentials request box appearing for unprivliged users and are working to correct this.
Problems with Kontakt player (limited users)
When loading Sibelius as a limited (non-admin) user, if the kontakt player is installed the user will receive an error about a missing install directory. Regrettably, Kontakt requires the user to be able to be able to write to the install directory. Thus there are 2 solutions:
- Either install Kontact to the shared user profile.
- Adjust the DACL on the install directory to allow the relevant users modify access.
See also
