Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Microsoft Silverlight is a programmable web browser plugin that enables features such as animation, vector graphics and audio-video playback so you can experience rich Internet applications. Silverlight offers a flexible programming model that supports AJAX, VB, C#, Python, and Ruby, and integrates with existing Web applications. From light planes to wide-body jets, fly highly detailed and accurate aircraft in the next generation of Microsoft Flight Simulator. Test your piloting skills against the challenges of night flying, real-time atmospheric simulation and live weather in a dynamic and living world. Create your flight plan to anywhere on the planet. Data logged by SIL, but stored locally (if the forward to the target URI fails), or data that is successfully forwarded to the target aggregation server, is stored in a binary file (for each day’s data). To display this data in PowerShell, use the Import-BinaryMiLog cmdlet. Software Inventory Logging Security.
-->Applies To: Windows Server (Semi-Annual Channel), Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2
Understanding SIL
Before you start troubleshooting SIL, you should have a good understanding of its components and how it works. The following videos give an overview of SIL and SIL Aggregator, and how to use them to forward and report inventory data:
How SIL data flow works
The SIL framework has two main components and two channels of communication. Flow of data over both channels, and between both components, is necessary for a successful SIL deployment (this assumes a virtualized, or cloud, environment -- purely physical environments only need one of the communication channels). You'll need to understand the components and data flow of SIL to deploy it correctly. After watching the overview videos above, you will have seen the architectural diagram that illustrates the components and the flow of data over both channels. Orange arrows indicate remote queries over WinRM, green dashed arrows indicate HTTPS posts to the SIL Aggregator from SIL in each WS end node:
If you encounter a problem with SIL, it is likely related to a disruption in the flow of data over the channels, and between the components. Following are the most common issues related to data flow, followed in the next section by the troubleshooting steps to resolve each of the three issues:
Data flow issue 1 – No data in the report when using the Publish-SilReport cmdlet (or generally missing data).
Data flow issue 2 – Too many servers under Unknown Host in the report.
Data flow issue 3 – Too many VMs under physical hosts listed as Unknown OS in the report, and/or an error produced when using Publish-SilData on Windows Servers running SIL.
Troubleshooting data flow issues
Before you begin, you'll need to know how long ago SIL Aggregator started with the Start-SilAggregator cmdlet.
Important
There will be no data in the report until the SQL data cube is processed at 3AM local system time. Do not proceed with troubleshooting steps until the cube has processed data.
If you are troubleshooting data in the report (or missing from the report) that is more recent than the last time the cube processed, or before the cube has ever processed (for a new installation), follow these steps to process the SQL data cube in real time:
- Log in as an administrator of SQL Server and run SSMS at a command prompt.
- Connect to the Database Engine.
- Expand SQL Server Agent and then expand Jobs.
- Right click SILStagingRefresh and then select Start Job at Step.
- Click Start and wait for the refresh progress bar to complete.
- Open PowerShell as an administrator and run the publish-silreport -openreport cmdlet.
If there is still no data in the report, proceed with troubleshooting the three data flow issues.
Data flow issue 1
No data in the report when using the Publish-SilReport cmdlet (or data is generally missing)
If data is missing, it is likely due to the SQL data cube not having processed yet. If it has processed recently and you believe data that is missing should have arrived at the Aggregator before cube processing, follow the path of the data in reverse order. Pick a unique host and a unique VM to troubleshoot. The data path in reverse would be SILA Report < SILA database < SILA local directory < remote physical host or WS VM running SIL agent/task.
Check to see if data is in the database
There are two ways to check for data: Powershell or SSMS.
Important
If the cube has processed at least once since SILA inserted data into the database, then this data should be reflected in the report. If there is no data in the database then either polling the physical hosts is failing, or nothing is being received over HTTPS, or both.
PowerShell
Open PowerShell as an administrator and run the get-silvmhost cmdlet, and then run get-silaggregator.
Note
The output of get-silaggregator will always mimic the Windows Server Details Tab of the Excel report. Don't expect a different result.
Run get-silvmhost
- If there are no hosts listed, then add hosts using the add-silvmhost cmdlet.
- If hosts are listed as Unknown, then go to Issue 2.d - If hosts are listed but there is no datetime under the Recent Poll column, then go to Issue 2 below.
Other related commands
Get-SilAggregator -Computername <fqdn of a known server pushing data>: This will produce information from the database about a computer (VM) even before the cube has processed. Thus this cmdlet can be used to check on data in the database for a Windows Server pushing SIL data over HTTPS, before, or without, the cube process at 3AM (or if you haven't refreshed the cube in real time as described at the beginning of this section).
Get-SilAggregator -VmHostName <fqdn of a polled physical host where there is a value under the Recent Poll column when using the Get-SilVmHost cmdlet>: This will produce information from the database about a physical host even before the cube has processed.
SSMS
nCheck for data from hosts being polled:
Open SSMS and connect to the Database Engine.
Expand Databases, expand the SoftwareInventoryLogging database, expand Tables, right click the HostInfo table and then select top 1000 rows.
If there is data for one or more hosts in the table, then polling for that/those host(s) has been successful at least once.
Check for data from VMs, or standalone servers, that have pushed data over HTTPS:
Open SSMS and connect to the Database Engine.a2. Expand Databases, expand the SoftwareInventoryLogging database, expand Tables, right click the VMInfo table and then select the top 1000 rows.
Note
Each row for a unique VM will represent one processed bmil file successfully pushed over HTTPS and processed by the SIL Aggregator. Bmil files are proprietary files used by SIL, one is created each our by each SIL instance Note that this is only necessary when SIL and SILA are used in virtual environments. Otherwise only HTTPS traffic is necessary/expected).
All data in the database should be reflected in SIL reports after the cube has processed.
Data flow issue 2
Too many servers under Unknown Host
This is likely to occur in virtual environments when SIL Aggregator is not successfully polling physical hosts that are hosting the virtual machines.
Open PowerShell as an administrator and run the get-silvmhost cmdlet.
If hosts are listed as Unknown, the add-silvmhost cmdlet did not work correctly – usually because of bad credentials added for access to these hosts (thus, Unknown). But if credentials are verified, it could mean the auto-detection of hosttype and hypervisortype in the add-silvmhost cmdlet was not able to recognize the platform. There are advanced troubleshooting steps available for these situations, but are not covered here (check EventViewer SIL Aggregator channels).
If hosts are listed, and hosttype and hypervisortype are listed with values that are NOT Unknown, i.e Windows and HyperV, or Ubuntu and Xen, etc., but there is no datetime under Recent Poll column, then polling has not successfully occurred yet.
You'll need to wait an hour after adding the host for polling to occur (assuming this interval is set to default – can be checked using the get-silaggregator cmdlet).
If it has been an hour since the host was added, check that the polling task is running: In Task Scheduler, select Software Inventory Logging Aggregator under Microsoft > Windows and check the history of the task.
If a host is listed, but there is no value for RecentPoll, HostType, or HypervisorType, this can be largely ignored. This will only occur in HyperV environments. This data actually comes from the Windows Server VM, identifying the physical host it is running over HTTPS. This can be useful in identifying a specific VM that is reporting, but requires mining the database using the Get-SilAggregatorData cmdlet.
Once the hosts are polling correctly, you will be able to see the data for these physical hosts in the SILA database where there is a datetime under recent poll. The Issue 1 section above provides steps for retrieving this data.
Data flow issue 3
Too many physical hosts with VMs listed as Unknown OS
- Pick one Windows Server end node (VM) that you know is on one of these hosts, login as an administrator.
- Open PowerShell as an administrator.
- Verify SilLogging is running by using the Get-SilLogging cmdlet.
If running, try to manually push SIL data by using Publish-SilData.
If there is an error:
- Ensure the targeturi has https:// in the entry.
- Ensure all pre-requisites are met
- Ensure all required updates for Windows Server are installed (see Prerequisites for SIL). A quick way to check (on WS 2012 R2 only) is to look for these using the following cmdlet: Get-SilWindowsUpdate *3060, *3000
- Ensure the certificate being used to authenticate with the aggregator is installed in the correct store on the local server to be inventoried with SilLogging.
- On the SIL Aggregator, be sure the certificate thumbprint of the certificate being used to authenticate with the aggregator is added to list using the Set-SilAggregator–AddCertificateThumbprint cmdlet.
- If using enterprise certificates, check that the server with SIL enabled is joined to the domain for which the cert was created, or is otherwise verifiable with a root authority. If a certificate is not trusted on the local machine attempting to forward/push data to an Aggregator, this action will fail with an error.
If all of the above has been checked and verified,but the issue persist:
Check that the certificate used to install the SIL Aggregator is healthy and matches the name of the SIL Aggregator server itself. Also, if enterprise certificates are used for installing the SIL Aggregator, the Aggregator may need to be joined to the domain where the certificate was created (these steps are unnecessary if other machines are successfully forwarding to the same SIL Aggregator).
Finally, you can check the following location for cached SIL files on the server attempting to forward/push, WindowsSystem32LogfilesSIL. If SilLogging has started and has been running for more than an hour, or Publish-SilData has been run recently, and there are no files in this directory, than logging to the Aggregator has been successful.
If there is no error, and no output on the console, then the data push/publish from the Windows Server end node to SIL Aggregator over HTTPS was successful. To follow the path of the data forward, login to the SIL Aggregator as an administrator and examine the data file(s) that have arrived. Go to Program Files (x86) > Microsoft SIL Aggregator > SILA directory. You can watch data files arriving in real time.
Note
More than one data file may have been transferred with the Publish-SilData cmdlet. SIL on the end node will cache failed pushes for up to 30 days. On the next successful push ALL data files will go to the Aggregator for processing. In this way, a newly set up SIL Aggregator could show data from an end node well before its own setup.
Note
There are rules SILA follows when processing data files in the SILA directory that are only relevant in low traffic situations. High traffic will always trigger processing in real time. The default behavior is that processing will commence either after 100 files arrive in the directory, or after 15 minutes. When troubleshooting end-to-end in a small environment, it is often necessary to wait 15 minutes.
After these files are processed, you will see the data in the database.
About
Ezra SIL is a typeface fashioned after the square letter forms of the typography of the Biblia Hebraica Stuttgartensia (BHS), a beautiful Old Testament volume familiar to Biblical Hebrew scholars.
For more information on certain characters used in the Biblia Hebraica Stuttgartensia, go to this page.
One download, two fonts
Ezra SIL v2.51
Containing the basic set of Unicode characters needed for Biblical Hebrew texts following the typeface and traditions of the Biblia Hebraica Stuttgartensia.
Ezra SIL SR v2.51
Containing the same set of Unicode characters as above but with a different style of cantillation.
Ezra SIL SR — a Different Style of Marking
The two Ezra SIL fonts are available to provide two different styles of cantillation marks. They were developed together, but there are some differences in how they display markings. This was done intentionally. The Ezra SIL font is supposed to render text identically to the printed BHS. The Ezra SIL SR font has a different style of cantillation marks which may be more familiar to users working with other editions.
- Beginning with v2.0, Ezra SIL SR ceased to combine SHIN DOT with a preceding HOLAM.
- With v2.0, Ezra SIL SR ceased to center U+0592 HEBREW ACCENT SEGOL above a consonant. SEGOL is placed to the left except in the rare medial instance, when it centers.
- Ezra SIL characters and markings follow the printed BHS as much as possible. Ezra SIL SR follows a different style of text.
- Ezra SIL differentiates vocalic holam-waw (U+05D5 U+05B9) from consonantal waw-holam (U+05D5 U+05BA) by displaying the holam slightly to the right for the former and slightly to the left for the latter. This is determined by the choice of code point for holam. Ezra SIL SR does not do this.
- With v2.0, Ezra SIL SR uses a diamond-shaped mark for the puncta, rather than a round dot.
- Ezra SIL shows furtive patah to the bottom right of the consonant, as in the printed BHS. Ezra SIL SR does not do this, but centers it, as for a normal patah.
Version 2.51 Feature List
- Unicode 5.0 support of Hebrew and Latin-1 codepages
- Improved placement of extra-biblical punctuation, such as period and comma.
- Includes Latin-1 characters, but should not be used for solely Latin texts, since the punctuation is done in a Hebrew style.
- Works in any application that uses OpenType fonts.
- Follows the recommendations for character order and encoding determined by a group of font developers during discussions in May 2003. This does not follow canonical order. Texts which have been converted to NFC or NFD canonical order will not display correctly with these fonts.
- No transliteration fonts are provided. Any font with full Latin support should be adequate for Hebrew transliteration (see Doulos SIL, Charis SIL, or Gentium for an acceptable Unicode font for transliteration of Biblical Hebrew).
Data Conversion
If you have text files typed with the pre-Unicode SIL Ezra font, they will have to be converted to Unicode to use with this font. Mapping files are available for download below (after the font packages). These can be used with TECkit and/or SILConverters 4.0.
Keyboarding
Windows and Mac operating systems provide a Hebrew keyboard as part of the OS. However, those provide for modern Hebrew input, not Biblical Hebrew.
SIL Hebrew is a Keyman keyboard useable on Windows, Mac, and Linux. Be sure Keyman is installed before installing the keyboard.
Windows only: An Israeli keyboard layout (using Microsoft Keyboard Layout Creator) is available from the Society of Biblical Literature. They also offer an MSKLC keyboard which closely follows the SIL Keyman layout.
Transliteration Resources
Data Conversion
If you have text files typed with the pre-Unicode SIL Heb Trans fonts, they will have to be converted to Unicode. TECkit mapping files for SIL Heb Trans fonts are available here and can be used with TECkit and/or SILConverters 4.0. Any font with full Latin support should be adequate for Hebrew transliteration (see Doulos SIL, Charis SIL, or Gentium for an acceptable Unicode font for transliteration of Biblical Hebrew).
Keyboarding
Hebrew and Greek Transliteration (SIL) keyboard is a Keyman keyboard useable on Windows, Mac, and Linux. Be sure Keyman is installed before installing the keyboard.
Downloads
License
Hebrew layout intelligence copyright © 2003 & 2007 Ralph Hancock and John Hudson, and licensed under the MIT/X11 License:
MIT/X11 License (for Hebrew layout intelligence only)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
All other font software licensed under the SIL Open Font License (OFL)
Changes from Ezra SIL v2.5 to 2.51
Ezra SIL v2.51
- Word-final Zinor (U+05AE HEBREW ACCENT ZINOR) is always to the left. When it occurs word-medial, it is also to the left, unless that position is obstructed by a sin dot, holam or lamed, in which case it is centred. This is the same behaviour as for U+0599 HEBREW ACCENT PASHTA.
- When U+0592 HEBREW ACCENT SEGOL and U+05A9 HEBREW ACCENT TELISHA QETANA occur word-medial, they are centred unless followed by U+200C ZERO WIDTH NON-JOINER, in which case they move to the left.
- When U+05A0 HEBREW ACCENT TELISHA GEDOLA is word-medial, it is centred unless the consonant is preceded by U+200C ZERO WIDTH NON-JOINER, in which case it moves to the right.
- There have been a few minor positional adjustments.
Ezra SIL SR v2.51
- U+05AE HEBREW ACCENT ZINOR is always to the left, whether it is word-final or word-medial.
- When U+0592 HEBREW ACCENT SEGOL, U+05A9 HEBREW ACCENT TELISHA QETANA and U+05A0 HEBREW ACCENT TELISHA GEDOLA occur word-medial, they are always centred.
- There have been a few minor positional adjustments.
NOTE: Text typed with v2.0 fonts will display legibly using v2.5 or v2.51, with only minor errors. However, text typed with v2.5 or v2.51 will not display acceptably using v2.0 fonts.
Fonts
| Ezra SIL 2.51 | for all platforms |
| Ezra SIL source files 2.51 | for all platforms |
| Ezra SIL web fonts 2.51 | for all platforms |
“EzraSIL-2.51-source.zip” contains the same files as “EzraSIL-2.51.zip” – plus the FontLab, VOLT, Word, Excel, and Keyman source files. However, it does not contain the .pdf files since the source files are included.
“EzraSIL-2.51-web.zip” contains the same files as “EzraSIL-2.51.zip” – plus Web Open Font Format (WOFF) fonts and sample web files.
This font is also available in the SIL software repository for Ubuntu. Users can subscribe to this software repository and get current versions and updates automatically.
Release history
- 2007-10-03 – Windows OpenType Unicode version 2.5.1
- 2007-06-15 – Windows OpenType Unicode version 2.5
- 2004-01-08 – Windows OpenType Unicode version 2.0
- 2002-09-30 – Windows OpenType Unicode version 1.1; minor documentation changes only
- 2002-09-11 – Windows OpenType Unicode version 1.0
Previous Versions
Download for previous versions »
Data Conversion
| Ezra SIL Mapping Files 2.51 | for all platforms |
Other Resources
The Westminster Leningrad Codex – Complete Hebrew Bible
For more information on how MS Office handles right-to-left (RTL) scripts, see RTL scripts in Microsoft Office.
Support
As these fonts and utilities are distributed at no cost, we are unable to provide a commercial level of personal technical support. Note: Version 2.51 is the final release of the Ezra SIL fonts.
Please note that these fonts are intended for use by experienced computer users. Installing and using these fonts is not a trivial matter. The most effective technical support is usually provided by an experienced computer user who can personally sit down with you at your computer to troubleshoot the problem.
Contact
Microsoft Silverlight
General troubleshooting information, including frequently asked questions, can be found in the documentation. Additional information is also available on the general Font FAQ page. If that fails to answer your question, send an email via this contact form.
Before requesting technical support, please:
- Carefully read all the documentation provided with the font and on this site.
- Try the Support and Troubleshooting path on scripts.sil.org.
Language Software Community
Microsoft Silver Partner
Support from other software users may be available through the SIL Language Software Community. This community will be growing to become the major source of software support.
Download Microsoft Silverlight For Windows 10
If that fails to answer your question, or you have a bug report, feature suggestion, or need help using the software, please contact us using the form below.