PalstatCAQ - instalation

​Basic information

Introduction

This manual describes the installation of the PalstatCAQ quality management software on the server including all its components.

System requirements

• Systémové požadavky
• Microsoft SQL Server Instalace
• Možné způsoby nasazení z pohledu ICT

Remote access from multiple locations

If the requirement is to make data available for multiple locations located in different states and thus accessed remotely. We strongly recommend a solution using RDP access to the central server where the application and MSSQL are located.

• When used on a VPN, it is not possible to specify a line throughput requirement. This is highly dependent on the volume and form of data to be handled over the VPN. Thus, what data the customer puts into the database will be used and retrieved.

Example1: A user on the local network inserts a 50MB attachment into the QSD module and works with the document or attachment in any Palstat module on the local network without any problems. However, a user on a VPN with 256kbps line throughput has no chance to work with the program.

Example2: Users on the local network use the STOPKARTY module and it contains 800tis records. No one has set up a global filter that will not show outdated and archived data. On the local network the program will be slow every time the grid is loaded, but on the VPN it will be completely non-functional. Before the SQL server can return the data to the application over the VPN it will timeout.

The speed of the application startup when using a VPN can be partially solved by a local copy of the system on a Clint PC. Please refer to the document for a possible solution, which is only informative and more solutions can be found.

Virtualization of HW resources

Technologically, it is possible to run PALSTAT CAQ and MSSQL server on many virtualization technologies.

Example:

• VMvare
• VirtualBox
• Micrtosoft Hyper-V

General HW recommendations

We recommend using branded HW (IBM, DELL, HP, Lenovo) with the possibility of purchasing an extended warranty - repair directly at the customer's site, the possibility of guaranteeing the start of work on the removal of HW defects or guaranteeing the time of removal of HW defects.

RAM memory size

For MS SQL Server operation, the recommended RAM size is 1:1 to the size of the running database (or the sum of active databases *data). For MS SQL Server, enough RAM has a significant impact on the responsiveness of the PALSTAT CAQ system. If it is not possible to provide the required RAM, place the MSSQL data files on SSDs.

Disk configuration

RAID 10 or RAID 1 is recommended for database storage. RAID 5 is not recommended for SQL databases (http://cs.wikipedia.org/wiki/RAID). The speed of the disk/disk array and the quality of the disk controller have a major impact on the response of the PALSTAT CAQ system. Use SSD and NVMe to achieve high performance and fast response of the entire system.

Licensing Terms

1. Subject matter of the licence agreement and basic provisions
   1. By this license agreement the Provider undertakes to provide PALSTAT CAQ licenses including implementation to the Customer in the scope specified in the price offer and the issued order.
   2. The Customer is allowed to use a separate parallel copy of the system on hardware owned by the Customer (laptop, PC) for testing purposes for a maximum of 2 months.
   3. The customer is entitled to use the software product in networked form for an indefinite period of time on the basis of the order, but only in accordance with the terms and conditions agreed in this specification and the performance of clauses 4 and 4.1.
2. Time, place and method of fulfilment
   1. The Customer hereby declares that it is well aware of the terms of the licence, in particular that the licence rights granted are non-exclusive and non-transferable to third parties, and is aware of them and undertakes to comply with them. The Provider authorizes the Customer to use the software only at the Customer's company headquarters, with the exception of the granting of the right to use the software and licenses that have arisen or will arise as a result of the legal separation of the network operator's activities from other activities, so-called unbundling (the Provider must be informed in advance of any changes).
3. Price and terms of payment
   1. The right to use the licenses according to the terms of the license agreement is subject to full payment of the agreed amount according to the offer and the issued order.
4. Warranties and liability
   1. The warranty for the provided PALSTAT CAQ software license comes into force on the date of handing over the software to the Customer for permanent use and lasts for 12 months. The warranty is not extended by changing the type of the granted License.
   2. The Customer shall be liable for all damages incurred by the Provider as a result of breach of the license agreements, in particular copyright infringement.
   3. Other conditions of warranty and post-warranty service are given in the Service Contract.
5. Concluding provisions
   1. Both parties represent that they have read the License Agreement and understand all of its provisions.

 

PalstatCAQ installation

When installing all components on a single server, we recommend the following directory structure

• Palstat3G
  • CAQservice (Unshared, configuration management and distribution service)
  • CAQapi (Unshared, site na IIS)
  • CAQweb (Unshared, site na IIS)
  • CAQdesktop (Application shared for clients)

COMPONENT INSTALLATION - CAQdesktop

What is CAQdesktop

It is a desktop Win32 application executable on Windows systems, which is the main UI for system users.

Installation on the server

• Download the installation/upgrade package from our customer portal or the link sent to you, downloading the upgrade from the link is limited in number and frequency (upgrades can only be downloaded 3 times and 1 time per hour).
• Check that the downloaded file is not marked as potentially dangerous and unblock it if necessary, see picture.
• Extract the ZIP into a directory structure as recommended above.
• Go to CAQdesktop
• Rename the "CONFIG (TEMPLATE)" directory to "CONFIG"
• Go to the CONFIG directory
• Insert the LICENSE files "key.enc, license.enc" can be downloaded from the customer portal (temporarily)
• Rename the config.xml file to config.xml.bak (temporarily)
• Insert the database.enc file found in the installation package under the CAQservice directory (temporarily)
• Create a share on the server of this directory and set the rights for users who can access the share. Set all content to READ for users to prevent unwanted deletion and modification of the application.
• Edit the database.enc configuration file

 

 

 

 

Modifying the configuration file and encrypting it

Open the ./CONFIG/database.enc file for editing and modify it according to the following example. First of all you need to edit the "Data Source" values where you insert the name or IP of the server where the SQL server is located, then edit the "user" and "password" according to the previously set. When editing, it is always necessary to follow the semantics of the XML standard.

The configuration file is described in the section SUPPORT - Sample database file

Run the application on the server ./APL/Launcher.exe

If the application is configured correctly, the initial initialization, creation of tables and auxiliary structures occurs. Use the ADMIN user for access without entering a password.

Client installation

Never start the client installation until PalstatCAQ is up and running on the server. In order for the SQL database to be accessible from another computer, it is necessary to configure TCP/IP on the SQL Server and enable the appropriate ports on the firewall. If you are not sure which port SQL communicates on, disable the firewall on the server during testing and create the appropriate rules on the server after testing Palstat functionality on the client. By default, MSSQL communicates on port 1433 and 1434 browser.

Next, just create a shortcut on the client PC from a shared folder on the server that will point to the application signpost, i.e. ./APL/Launcher.exe. It is possible to launch the application from a UNC path or from a mapped disk.

Setting the appearance of PALSTAT

If you want to personalize the appearance of PALSTAT or are experiencing difficulties when you have changed the appearance in WINDOWS. You can customize the launch shortcut and assign one of the looks below. In the example you can see the use of the style for the FMEA module.

Edit shortcut: ../APL/launcher.exe /style 2019COLOR

Available looks (each style separated by a comma):
BASIC (default), BEZIER, 2019COLOR, 2019WHITE, 2019DARK, 2019BLACK

 

COMPONENTS INSTALLATION - CAQservice

What is CAQservice

The CAQservice will be used in many aspects of your PalstatCAQ deployment and is recommended to be installed and run alongside your existing system package. It is a win64 system service and thus can only be installed on Windows OS.

What the service provides

• The Microsoft SQL access configuration and config.xml will be distributed to clients (users) from one central location and will be hidden from them.
• Configuration will be centrally managed for other services CAQapi, CAQweb
• Possibility to automate the sending of e-mail, SMS reports, their management via the CAQadmin (System Administration) user interface and replace the existing solution via the task scheduler.
• PUSH notifications, notifications can go ONLINE to selected actions in the Palstat system in the form of SMS or Email.
• External calibration, possibility to connect the meter module to an external calibration company ONLINE via AzureCloud.
• Custom API with the possibility to monitor the status of the PalstatCAQ system.

 

Installation on the server

Before installing and configuring the service, verify that you have a free and available port that you plan to use, for example, by using the "Resource Monitor" application, "Network" tab, then "Listening Ports"

• The installation package includes the ".../CAQservice" directory, which you unpack on the server where you want to run the service, often the same machine where the application itself is. However, this directory must not be part of the user share.

• Rename the "CONFIG (TEMPLATE)" directory to "CONFIG".
• In the file ".../PalstatCAQ/CAQservice/CONFIG/PalService.xml" set
  • serverIpAddress - on which IP address/DNSname the service should listen (obsolent from 2025.01.000)
  • apiPort - on which port the service should publish its API, default 8001
  • apiBaseUrl - on which adapters the service should listen. e.g. "*:8001" "172.10.0.10:8001,192.168.0.1:8001"
• On the server where the service is installed, ensure firewall throughput to the selected port or application.

 

You can set the rule on the firewall with this command, assuming you are using port 8001:

netsh advfirewall firewall add rule name="CAQservice" dir=in protocol=TCP localport=8001 action=allow

Service Settings

• The basic CAQdesktop package must always be running first.
• Rename "./CAQdesktop/CONFIG/config.xml.bak" to "config.xml" and edit the file by defining the IP and port where the service will work.
• MOVE the license files from "../CAQdesktop/CONFIG" to "../CAQservice/CONFIG" (in the ../CAQservice/CONFIG directory there must be only the config.xml file with valid configuration on CAQservice -> IP/PORT)
• Continue by checking the "PalService.xml" configuration and starting the service.

Service registration on the server

• As a user with administrator rights, run the ".../CAQservice/CaqService.Install.bat" command to register and start the service on port 8001. It is advisable to include the service in your internal monitoring system and keep it active at all times. The service on the server will log to its own log "PalstatServerLog", check that it has been created by the registration (EventViewer -> Applications and Services Logs -> PalstatServerLog), it may happen that the log is not created, then you need to restart the server to complete the registration correctly.
• You can verify the functionality with the examples below, which must include the port you configured for the service and its API. You can get the same result under "Resource Tracking"
• Next, check the following examples of API availability via a web browser, e.g. "http://[SERVER_IP]:[PORT]/api/"

Change the user to run the service

• In some cases, you are required to run the service under a specific domain-controlled user. You make the change as usual under service settings and restart to apply the user change. If the user does not have the right to connect to "Listener", i.e. port 8001, the service will not work and you will find the message in the system log of the service
  • "System.Net.Http.ListenerExeption" a "Access id denied
• To resolve the error, set a user with sufficient permissions or add an exception to the requested port directly on the machine running the service using the command below. In the case of a different port, modify your environment.

netsh http add urlacl url=http://+:8001/ user=DOMAIN/user

 

Verification can be done by.

netsh http show urlacl

We have confirmed that when a user changes, various non-standard service behaviors and correct port opening can occur. In some cases it is necessary to manually delete the port from the system and then restart the service. For example, when calling the CAQservice API service URL, an "HTTP Error 503" error is returned. The service is unavailable".

Proceed as follows:

• Stop CAQservice.
• Run the command prompt as Administrator and insert the command below to delete the associated Listener if it is "stuck".
• Start the CAQservice and monitor the corresponding LOG and then test some URLs of the "Service API" section.

netsh http delete urlacl  url=http://+:8001/

 

• Verification of service functionality, PowerShell

  netsh interface ipv4 show tcpconnections  | Select-String "Listen"

•  Verification of service functionality, CommandLine

  netstat -aon | find /i "listening"

Adding a user

In the "User Database" module there must be a user "SERVICE" with rights for the "Reporting Viewer" module

• Print
• View all records
  
  The service below it accesses the database. You do not need to set a password.

​

Servis API

CAQservice has its own service API for extracting some basic information about the operation of the PalstatCAQ system. The functionality is still being extended and will be updated on this page.

URL address	Functionality
http://mujserver:8001/api/	Default page
http://mujserver:8001/api/status/	The service status display returns 1 if the service is functional.
http://mujserver:8001/api/status/info/?encrypt=false	Detailed information
http://mujserver:8001/api/mail/test?receiver=example@example.com&sender=example_sender@example.com	Testing the SMTP server configuration
http://mujserver:8001/api/activation/	License activation status
http://mujserver:8001/api/data/eventlog/	Displays the last 100 events from the system logging table.
http://mujserver:8001/api/web/string?url=https://www.palstat.cz/caqservice_request/&encrypt=false	Verification if the service has access to WEB / PROXY permeability check
http://mujserver:8001/api/debug/checklistener	Status Listener

​

​Automation settings for data loading, "Scheduler" tab

Přejděte na "CAQservice - plánovač úloh"

To configure a proxy service

If your company uses a proxy server for Internet access, edit the palservice.xml configuration file. In the section enter the IP address of your Proxy server including the port it is running on e.g. 192.168.0.1:8080.

Proper proxy settings affect:

• Seamless application activation. If you use the proxy and it is not configured here, you will need to activate the application at regular intervals of about 1 year.
• Functionality of automatic connection to external IS.
• Non-functionality in case of using online calibrations.
• Non-functional display of news in the program.

The correct configuration and availability of the requested URLs can be verified using the query below, where the request is passed to the CAQservice, which attempts to contact the requested URL and returns the result to the browser. The test result must not result in an error. "An error has occurred."

http://server:8001/api/web/string?url=https://www.palstat.cz/caqservice_request/&encrypt=false

​

CAQservice configuration for sending SMS notifications

This functionality is available from version 2022.01.xxx and requires an active CAQserver component together with a purchased SMS package. The messages are sent via a third party service and the sender number defaults from the USA. The form of sending notifications for certain events is always defined by customer requirements.

Message reception can be tested in CAQadmin (System Administration) under the Diagnostics tab.

• Under the CAQservice window, click on "TEST"
• For the "Send sms via CAQservice" entry, set the mobile number where you want to send the test, including the international area code.
• Click on "Run" and wait for the result.
• Click on the field according to point 4. and watch the test result. A message will arrive on the mobile phone you specified within 10 minutes.

 

​ ​

 CAQservice configuration for sending email report

If you have defined any report in the PalstatCAQ system to send the output to the users' email, you must configure an SMTP server for the CAQservice to send the emails. Configuration is done in the ".../Palstat3G/CAQservice/CONFIG/Config.xml" file. Your configuration file may contain many other parameters and settings. Editing should only be done by an IT person with knowledge of the structure and operation of XML.

Description of the parameters:

• host - IP address of your SMTP server, it is the only REQUIRED parameter
• port - must be set if it is different than the default 25 (typically when SSL is enabled)
• user and password - if they are not filled in, the Windows user account under which the program is run is used for authentication against the SMTP server, this is the recommended procedure, so the password is not visible to normal users, if the parameters are filled in, they take precedence
• defaultmailadress - should be set, it is used if the user sending the message does not have the email listed in the Palstat User Database module
• encoding - the default is Unicode, other frequently used ones are Ascii and Utf-8, or any other from the C# Encoding Class (be careful to write everything with the first capital letter)
• enablelessl - default is false, enables/disables encrypted communication with SMTP server

 

<?xml version="1.0" encoding="utf-8" ?>
<palstat>
    <globalconfig>
        <mail>
            <email host="192.168.0.1" port="587" enablessl="true" user="username_smtp" password="pwd_smtp" defaultmailaddress="palstat@domain.com" encoding="Utf-8" />            
        </mail>
    </globalconfig>
    <appconfig>
    </appconfig>
</palstat>

Activating a function in "System Administration"

To activate the sending of emails, you must set up the appropriate reporting and enable it in System Administration.
Furthermore, the "Scheduler" tab in ./CAQdesktop/APL/CAQadmin.exe (System Administration) must be checked for the "Mail" line.

Testing email throughput

To verify the correctness of the configuration of email parameters, you can use the service API call from CAQservice, as shown on this page in the "Service API" section. This step is required to verify functionality and without performing it, do not perform or attempt to configure the Reporting module to send messages.

 

Testing the functionality of an SMTP server

Testing using the service API

This is a basic form of test that is sufficient to verify the throughput of the CAQservice to the SMTP server.

http://server:8001/api/mail/test?receiver=example@example.com&sender=example_sender@example.com

Testing from CAQadmin "System Administration"

It offers a graphical interface and it is necessary to have the CAQservice running beforehand, without which "System Management" will not even start.

Go to the "Diagnostics" tab, select the "TEST" button and edit the sender and recipient address.
Finally, click on the "Run" button where the SMTP test line must have a response content of "Sent".

 

​

CAQservice email processing diagram

With proper configuration of the service, SMTP server and reporting, individual email messages are forwarded to the PALMAILQUEUE queue table where each email can take on different states. For example, when the SMTP server is unavailable or other errors occur. By opening the named table and sorting by the status column, it is possible to see which emails are in error status and why. The table is also accessible in the CAQadmin.exe diagnostic tool where you can view the table under the Diagnostics -> Log tab.

Check out FlowChart email processing.

COMPONENTS INSTALLATION - CAQapi and CAQweb

What is CAQapi and CAQweb

CAQapi: HTTP/S data layer that allows data to be extracted from the system to other systems and visualizations.
Required for CAQweb mobile appNutné pro mobilní aplikaci CAQweb
More information can be found in a more detailed document.

CAQweb: HTTP/S UI layer for users in limited functionality on selected modules.

What the components provide

• CAQapi - access to system data using JSON, SWAGGER
  CAQapi - provides data for CAQmobile
  CAQweb - web interface for modules Controlled Documentation, Measurement Database, Reporting, Production Documentation

 

Preparing the environment, IIS Server

• Install IIS - Internet Information Server using the Add/Remove Roles tool
• Install Microsoft .NET Framework 4.5.
• From the Start menu, locate and run Microsoft Web Platform Installer (discontinued MS support as of 10/2023)
• Use this application or the "Add Roles and Features Wizard" to install the items:
  • IIS: Basic Authentication
  • IIS: ISAPI Filters
  • IIS: ISAPI Extensions
  • IIS: Windows authentication
  • ASP.NET 4.5
  • Microsoft Rewrite 2.x / URL Rewrite, this package is shipped separately and can be found in the CAQsupport directory of the installation ZIP package.
• Restart IIS Server, just Site is not enough

Installation on the server

• Copy CAQapi and CAQweb from the installation package to the desired directories. Suitable for ../PalstatCAQ/CAQapi and CAQapi respectively
• Rename the "UserConfig (TEMPLATE)" directory in the destination directory to "UserConfig"
• In the "../UserConfig/CONFIG" directory, paste/overwrite the config.xml from CAQdesktop or edit manually.
• Set the correct access rights to the newly created folder on disk. Depending on the IIS version and system, the user IUSR and group IIS_IUSRS should be set here with Read&Execute rights.
  WARNING: without the correct permissions the application will not work.

 

IIS Settings

• Search the server and launch Internet Information Services (IIS) Manager 
• On the desired web page, right-click to add the application or site and route it to the expanded directory.
• Name the new site CAQapi or CAQweb depending on which extension you are installing.
• If you are installing as Website, set the domain name under which it will be available.

 

• In Application Pools, select the one you use for the application and in Advanced Settings set Start Mode to Always to ensure faster first launch of the application when not in use for a long time. It is advisable to set the Application Pool with the name "Palstat" and then use this for both CAQapi and CAQweb.

 

---

• For the created CAQapi or CAQweb application, set Authentication Anonymous and Forms Authentication to Enabled if you want to log in to the web interface using the login window and thus authenticate the user against the internal Palstat database, or set Windows Authentication to Enabled if you want to authenticate the user against Active Directory.

ATTENTION This setting must match how you have set up user authentication in Palstat itself and you must also fill it in the "Authentication.config" configuration file (see below).

If you use authentication against Active Directory, then you will probably need to add the IIS server (http://url.example.cz) on the stations in the "Internet Options" in the "Control Panel" to the "Trusted Sites" or "Local Intranet" zone, depending on the security level set on your network, so that the domain controller can be contacted and the user authenticated.

Testing functionality

You should now see the default page for CAQapi and CAQweb at the address of the web page where you added the application under IIS. For example:

CAQweb
Production address:	http://url.example.cz/CAQweb/
Configuration test address:	http://url.example.cz/CAQweb/status/
CAQapi
Production address:	http://url.example.cz/CAQapi/
Configuration test address:	http://url.example.cz/CAQapi/status/xml/
Swagger	http://url.example.cz/CAQapi/swagger/

 

Setting up IIS to run HTTPS

The setup can be done, for example, by using a free service that can be used to sign the IIS server. The certificate is automatically renewed at regular intervals. The implementation can be applied in the following ways see https://letsencrypt.org/docs/client-options/

Our company uses win-acme (.NET), which is published on GitHub - https://github.com/PKISharp/win-acme/releases

    You download and extract the ZIP to any location on the server where you want to apply IIS e.g. c:/LetsEncrypt
    The DNS must be set to the correct resolution and the machine where you want to apply must be able to see the address.
    Run letsencrypt.exe
    You then go through the wizard as per your needs. One possible scenario is described below, but it is not fixed.
    The result is a signed IIS machine or site and a task created in the scheduler to check the certificate for currency and renew it when it is about to expire.

Possible SSL deployment using LetsEncrypt

We set up an IIS site called ssl.palstat.cz and set up DNS routing (the address is only fictitious, use the appropriate DNS name for your deployment).

•     Set up the site as a classic HTTP site and set up DNS
•     On the machine, verify that the DNS is working, e.g. by pinging ssl.palstat.cz or by opening it in a browser
•     Run LetsEncrypt.exe and select "N"
•     Select "Single binding of an IIS site"
•     Select the Site we want to sign
•     Confirmation of successful certificate deployment
•     The address must work in HTTPS
•     Scheduler contains a task to renew the certificate

 

1)

 

2)

 

3)

 

4)

 

5)

 

6)

 

 

7)

 

 

8)

 

Sample configuration files

Configuration files are always included in the installation or upgrade package and can be used during installation with appropriate customization for the installed environment.

Sample configuration file for CAQservice

".../Palstat3G/CAQservice/CONFIG/palservice.xml"

<serviceSetting>
  <serverIpAddress>192.168.0.1</serverIpAddress>
  <apiPort>8001</apiPort>
  <apiBaseUrl></apiBaseUrl>
  <palstatPath></palstatPath>
  <serviceName>CaqService</serviceName>
  <lang></lang> <!-- to force the use of a particular language, otherwise it is taken out of the system; values: cs/de/en -->
  <tempDir>Service</tempDir> <!-- When not set, the default value is used, values: [Service] (default value), [System] (c:/windowstemp) or defined path example: [C:/Palstat_3G/CAQservice/TMP], WEB app CAQservice on IIS ignores this setting -->
  <userAuthMode>0</userAuthMode>
  <log>
    <information>true</information>
    <error>true</error>
    <warning>true</warning>
    <debug>false</debug>
  </log>
  <runDelay>10000</runDelay>
  <webSettings>
    <Credentials>DefaultCredentials</Credentials>
    <Proxy>
      <Url></Url>
      <Credentials>DefaultCredentials</Credentials>
    </Proxy>
  </webSettings>
  <modules>
    <module id="WebPortal" enable="false" />
    <module id="ErrorReport" enable="true" />
    <module id="EventHandler" enable="true" />
    <module id="Scheduler" enable="true" />
  </modules>
</serviceSetting>

 

".../Palstat3G/CAQservice/CONFIG/config.xml"

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<palstat>
  <globalconfig>
    <webserver>URL ADDRESS OF CAQweb MODULE</webserver>
    <webapi>URL ADDRESS OF CAQapi MODULE</webapi>
  </globalconfig>
</palstat>

 

Sample configuration file for CAQdesktop, CAQweb and CAQapi

Place the other parameters that were previously contained in this file into ../CAQservice/CONFIG/config.xml in the directory of the service itself. Respectively, the application's config.xml file will contain only the following. You will use the same file for CAQdesktop, CAQapi and CAQweb.

".../Palstat3G/CAQdesktop/CONFIG/Config.xml"

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<palstat>
  <globalconfig>
    <serviceipadress>192.168.0.1</serviceipadress>
    <serviceapiport>8001</serviceapiport>
    <serviceapicontrol>true</serviceapicontrol>
  </globalconfig>
  <appconfig>
  </appconfig>
</palstat>

 

 

Error states

 

CAQdesktop a CAQservice

Client stations cannot connect to CAQservice

It works on the CAQdesktop server, but not on the client stations. Check the basic settings as with any other program that is supposed to communicate on a dedicated port:

•     Is there a pass-through port set on the server? Check from the client station using "telnet".
•     Is the service on the server active and listening on the selected port?
•     Check the firewall on the server.
•     If you have the server name as DNS in the Palservice.xml configuration, modify to IP address. Likewise in config.xml for CAQdesktop
•     Are the clients on the same network segment? If the clients are on a VPN it may not work properly and you need to choose a different procedure and settings.
•     Restart the CAQservice

 

 

 

WINDOWS error appears on startup and PALSTAT does not start at all

This is a rather vague error and is often caused by the absence of .NET4 or the client PC does not have a server with the application included in the local zone, continue with the chapter "Client Installation".

Connection error

It is called immediately when you try to log in to the application. It is caused by incorrect configuration of the database.enc configuration file or incorrect user settings on the SQL server. As a trial, you can set higher access rights for the user "pal" see. "Creating a user"

 

Decryption error

It is caused by an invalid key for decoding the license file or connection file.

 

Invalid database setting configuration file

The connection configuration file is miswritten (not UTF-8) or the message follows the "Decryption error" and it is necessary to resolve the previous error condition first. Or you have a syntax error in the file writing.

 

 

 

CAQapi a CAQweb

Non-functional write-back via CAQmobile when depreciating actions.

The documented problem is the use of the WebDAV module, which is not required for CAQapi or CAQweb, but can be installed on IIS for another project of yours. You need to modify the configuration of this module for Site or Application on IIS for CAQapi/web or remove it from IIS. More details can be found in the discussion thread on stackoverflow.com

Modifying WebDAV handler behavior.

•     Go to IIS Manager.
•     Click on your app.
•     Go to "Handler Mappings".
•     In the feature list, double click on "WebDAV".
•     Click on "Request Restrictions".
•     In the tab "Verbs" select "All verbs" .
•     Press OK.

 

 

 

Downgrade SW Palstat 3G

New versions of applications make irreversible changes to the databases when they are updated. Thus, downgrading is only possible at the cost of data loss. Not only must the APL directory be replaced with an older one from the backup, but also the databases corresponding to the respective Palstat 3G version must be restored from the backups. Technically this is possible, but for the reasons described above we do not recommend it.

For each update we recommend to backup the APL directory e.g. to APL.old1, APL.old2... and also backup the database. If you have set up automatic daily backups, a regular backup is sufficient.

If the customer for any reason requires a downgrade with data preservation this will first have to be assessed by the technical director and any SQL modifications and conversions will be charged according to complexity.

In most cases DOWNGRADE can be done one version number back. For example, if you have been sent a new version 2020.02.005 and it is subsequently determined that there is a serious problem that prevents you from using the program to its fullest extent, you can revert to 2020.02.000. This example cannot be applied as a precedent.

PALSTAT lock and termination enforcement

In some cases, it is required and necessary to centrally terminate PALSTAT on all stations and prevent users from running PALSTAT again. This is commonly used when performing a SW Upgrade.

Each PALSTAT installation contains a CONFIG directory where you can find the file service.lck.bak By renaming the file to service.lck you will activate the application lock, which has two basic functions.

• Terminate running applications on client stations. After activating the lock, the system prompts the user to save everything and close the application within 1min. If the user does not respond to the prompt, the termination will be forced. In this case, loss of unsaved data is possible.
• It will ensure that no one else can run any PALSTAT program and will alert them with a configurable message.

Setting the lock

The content of the file consists of several configuration values. Individual parameters can be commented by placing a semicolon at the beginning of the line.

command=service
runtimemessage=The PALSTAT system is currently undergoing maintenance and the restart will be possible in a few minutes
startmessage=Maintenance of the PALSTAT system is in progress
manager=OMZaccngDiUBADgA

Description of parameters:

• command [mandatory], must always be specified
• runtimemessage [optional], a message to be displayed to clients when the application is running
• startmessage [optional], a message to be displayed when a new application is attempting to start
• manager [optional], PC key identifier to be an exception and applications can be started even when the lock is active

You can get the key for the manager parameter from the registers in the

HKEY_CURRENT_USER/Software/PALSTAT.NET pod ID

​