Failed To Read Xar File
This error may indicate damage to the SYSVOL folder in domains where replication is based on outdated FRS instead of more modern. Compare the contents of the folder on the problem domain controller DCnamesysvoldomain.localPolicies with any other DC.
Failed To Read Xar File Download
We had this issue and discovered that some legacy Win2003 domain controllers only talk SMBv1. When we rolled out some Win10 client machines, they have SMBv1 disabled by default, so they could not read the domainSYSVOL folder if they hit one of the legacy DCs. When we enabled SMBv1 on the client, they could read the SYSVOL folder and were able to process GPOs.
Obviously, SMBv1 is not considered secure so view this as a temporary solution until you can get off Win2003 DCs and then go back and disable SMBv1 on those client machines.
.The LabKey Server configuration file, labkey.xml by default, contains settings required for LabKey Server to run on Tomcat. This topic describes modifications you may need to make to that file. The included moving it to /conf/Catalina/localhost.Configuration File NameThe default URL for your LabKey Server installation is so the configuration file name is labkey.xml.If you wish to rename the default URL path to include something else in the place of 'labkey', you can change the name by renaming the labkey.xml file.
If you do this, you should do it when you first install LabKey Server, as changing the name later will cause any external links to your application to break. Note that Tomcat treats URLs as case-sensitive.Note that if you rename the configuration file, you will also need to edit the context path setting within it, as described below.If you wish for your LabKey Server application to run at the server root, you can rename labkey.xml to ROOT.xml. In this case, you should set the context path to be '/'.
You would then access your LabKey Server application with an address like the LabKey Configuration FileImportant: The LabKey configuration file contains user name and password information for your database server, mail server, and network share. For this reason you should secure this file within the file system, so that only designated network administrators can view or change this file.Modifying Configuration File SettingsYou can edit the configuration file with your favorite text or XML editor. You will need to modify the LabKey Server configuration file if you are manually installing or upgrading LabKey Server, or if you want to change any of the following settings. The appdocbase attribute, which indicates the location of the web application in the file system.
Database settings, including server type, server location, username, and password for the database superuser. SMTP settings, for specifying the mail server LabKey Server should use to send email to users. Encryption Key - Configure an encryption key for the encrypted property set. Note that in our template, the placeholder values for these settings are highlighted with '@@', i.e '@@jdbcPassword@@', to make them easier to find in the file.
Failed To Read Xar Files
Replace the full placeholder with the correct password. Do not include the '@@' surrounding it.Many other LabKey Server settings can be set in the Admin Console of the web application. For more information, see.The path AttributeThe path attribute of the Context tag specifies the context path for the application URL. The context path identifies this application as a unique application running on Tomcat.The context path is the portion of the URL that follows the server name and port number. By default, the context path is set to 'labkey'.Note that the name of the configuration file must match the name of the context path, including case, so if you change the context path, you must also change the name of the file.The appDocBase AttributeThe appDocBase attribute of the Context tag must be set to point to the directory where you have extracted or copied the labkeywebapp directory. For example, if the directory where you've copied labkeywebapp is /usr/local/labkey/labkey, you would change the initial value to '/usr/local/labkey/labkey/labkeywebapp'.Database SettingsThe username and password attributes must be set to a user name and password with admin rights on your database server.
The user name and password that you provide here can be the ones that you specified during the PostgreSQL installation process for the database superuser. Both the name and password attribute are found in the Resource tag named 'jdbc/labkeyDataSource'. If you are running a local version of PostgreSQL as your database server, you don't need to make any other changes to the database settings in labkey.xml, since PostgreSQL is the default database choice.The following template resource tag for PostgreSQL applies to Tomcat 8 and above. If you are running LabKey Server against Microsoft SQL Server, you should comment out the Resource tag that specifies the PostgreSQL configuration, and add a Resource tag for the Microsoft SQL Server configuration. A template Resource tag for MS SQL Server is available at:.Notes:If you are running LabKey Server against a remote installation of a database server, you will also need to change the url attribute to point to the remote server; by default it refers to localhost.The maxWaitMillis parameter is provided to prevent server deadlocks.
Waiting threads will time out when no connections are available rather than hang the server indefinitely.GUID SettingsBy default, LabKey Servers periodically communicate back to LabKey developers whenever the server has experienced an exception. LabKey rolls up this data and groups it by the GUID of each server.
You can override the Server GUID stored in the database with the one specified in labkey.xml. This ensures that the exception reports sent to LabKey Server developers are accurately attributed to the server (staging vs. Production) that produced the errors, allowing swift delivery of fixes. For details, see.SMTP Settings (Optional, Recommended)LabKey Server uses an SMTP mail server to send messages from the system, including email to new users when they are given accounts on LabKey. Configuring LabKey Server to connect to the SMTP server is optional; if you don't provide a valid SMTP server, LabKey Server will function normally, except it will not be able to send mail to users.At installation, you will be prompted to specify an SMTP host, port number, user name, and password, and an address from which automated emails are sent.
Note that if you are running Windows and you don't have an SMTP server available, you can set one up on your local computer.The SMTP settings are found in the Resource tag named 'mail/Session'. mail.smtp.host Set to the name of your organization's SMTP mail server. mail.smtp.user Specifies the user account to use to log onto the SMTP server.
mail.smtp.port Set to the SMTP port reserved by your mail server; the standard mail port is 25. SMTP servers accepting a secure connection may use port 465 instead.SMTP Authentication and Secure Connections:Many LabKey installations run an SMTP server on the same machine as the LabKey web server, which is configured for anonymous access from the local host only. Since only local applications can send mail, this ensures some amount of security without the hassle of using a central, authenticated mail server. If you choose instead to use an external authenticated server, you'll need to add the following:.
mail.smtp.from This is the full email-address that you are would like to send the mail from. Replace @@masterEncryptionKey@@ with a randomly generated, strong password, for example, a string of 32 random ASCII characters or 64 random hexadecimal digits. Once a key is specified and used, the key can't be changed, otherwise the existing values will be irretrievable. Different LabKey Server deployments should use different encryption keys, however, servers that use copies of the same database (for example, most test, staging, and production server combinations) need to use the same encryption key.LDAP SynchronizationIf you wish to synchronize with the user and groups on an LDAP server, add an appropriate tag to the labkey.xml file.An example configuration to a public LDAP test service.
Comments are closed.