August 2012 Issue TECH TIP Managing PSQL v11 Server Licensing on Virtual Machines One of the key reasons that VM adoption continues to grow is that it is very easy to configure and deploy new virtual machines and, with them, instances of applications. Companies can meet demand for new systems - either for internal use (testing, development, new hires) or for external use (new customers) - more quickly and cost efficiently than purchasing, configuring and delivering physical servers. And, it is easy to move VMs from one physical server to another to allow for hardware upgrades or to move VMs to a more powerful machine. The end result is that IT departments can create, move and distribute copies of software with very little effort, which can create a compliance risk for companies that do not have well defined processes and controls.

• Pervasive Sql Tools
• Sql Server V11

To help reduce that risk, licensing controls on PSQL v11 Server and Workgroup are stricter on VMs than for physical machines. With the exception of changing the amount of memory available to a VM, any changes to a VM configuration will put a PSQL v11 Server or Workgroup product key into a failed validation state. And, if the key is not repaired, failed validation can lead to the key being disabled.

How a Change to a VM Can Trigger a Failed Validation State During the authorization process, Pervasive PSQL collects attributes about the VM. These attributes include machine name, host name, OS type, CPU name and type, MAC address and others.

PSQL combines a specific set of these attributes and the details of each attribute to create a machine ID. That machine ID is stored locally on the VM and in the Pervasive licensing database (in the Cloud) along with the product key. Each time Pervasive PSQL services are started, PSQL reviews the configuration, generates a machine ID and compares the just generated machine ID with what is stored locally.

Pervasive Sql Tools

If nothing has changed, the machine ID's match and everything is fine. If there has been a change in the VM configuration, the machine ID's don't match and the key state changes from Active to Failed Validation. What Happens When a Key Moves to Failed Validation State? Pervasive PSQL will continue to operate if a key goes into a failed validation state. But.if the issue is not corrected, the key will eventually move to a disabled state and the database will stop working (will not accept any connections).

When the key state changes, PSQL will begin to generate alert messages in the PSQL log, in the OS log, and in the Pervasive Notification Viewer on the desktop of the system where PSQL is installed. To learn more about the Notification Viewer,. Some Tips to Help Keep PSQL v11 Licenses on VMs Valid. Always, always deauthorize the key before making any changes to a VM.

Deauthorizing the key tells the Pervasive licensing server that the key is available for use on another machine. If there are changes to a VM from a move or from a reboot, the key can be reauthorized with no problems. Note: PSQL v11 Server and Workgroup keys have a limited number of authorizations - typically 10. To check the number of remaining authorizations, go to the PSQL license administrator, highlight the key and click the Remaining Authorizations button. Update to the most current service pack of PSQL v11. More current versions of PSQL v11 have features to tell customers what's happening with their license, provide alerts in the event of a license state change, and give plenty of time to repair the key before the license is disabled.

How fast can I get with CLL? You can get sub 3 fairly easy. Your website sucks for printing! Do you have a PDF? Why yes, yes I do. Thanks to Andy Klise, you can download it here. Why are there so many options for algs? Something that is useful at the highest level of 2x2 is knowing multiple algs to skip pre AUF or post AUF.Missing. F (R U R' U')*3 F' (JWC). F2 R' F2 R2 U2 R' F2 (RD). Arranged by Andy Klise Inspired by David Woner (R U2 R' U')(R U2)(L' U R' U' L). (x' R2 U2 R' U')(R U2)(L' U R'). R U R' F' R U R' U' R' F R2 U' R'. (R U' R') U' F2 U' (R U R') D R2. Algorithms by.Missing. 2x2 cll algorithms pdf creator. Sunes: 1: 0:06 R U R' U R U2 R' 2: 0:28 R' F R2 F' U' R' U' R2 U R' 3: 0:53 F R' F' R U2 R.

PSQL v11.0 - Key state moves from Active to Disabled without a Failed Validation state. PSQL v11.0 does not have license state warning notices (via Notification Viewer) and does not have a Failed Validation state. PSQL v11 SP1 - Introduced Failed Validation state and intelligent 14-day period between Failed Validation and Disabled. 'Intelligent' 14-day period means the product key takes at least 14 days to move from Failed Validation to Disabled and it won't be disabled on weekends or on holidays.

PSQL v11 SP1 also introduced the Notification Viewer which delivers alerts and recommended action to handle key validation issues. Alerts are posted to the PSQL log, OS log and to the desktop of the system where PSQL is installed. PSQL v11 SP2 - Introduced updated Monitor Utility to help customers estimate Pervasive PSQL Vx Server capacity requirements. PSQL Vx Server is a great fit for heavy users of virtual machines - we've adjusted the license enforcement mechanism to support operation on hypervisors (most notably moving live VMs from one physical machine to another without having any effect on PSQL licensing.).

Configure the VM to reduce the likelihood of PSQL licenses becoming invalid. Check your VM vendor documentation for specifics:.

Configure a static MAC address for VMs running PSQL. If the VM changes location, is cloned or copied, the MAC address typically will change - changing the machine ID and invalidating the product key.

Tie the VM to a specific CPU. This will make sure that when the VM is rebooted, migrated or moved it is not inadvertently tied to a different CPU (for example on a multi-processor server, where CPU properties are sometimes slightly different), causing the machine ID to change and invalidating the product key. Locking down a CPU in VM's depends on your VM vendor:.

Microsoft's Hyper-V 3.0 will be the first version of Hyper-V to support locking the VM to a CPU. Citrix XenServer (vcpu pinning) and VMware (CPU affinity) both support locking a VM to a specific processor. Define which VMs can be moved automatically by the hypervisor. A machine ID change caused by a hypervisor initiated VM move is one of the most common reasons for PSQL v11 failed validation states.

By requiring that VMs running PSQL be moved manually, it is less likely that an IT staff defined (and hypervisor implemented) load balancing rule will inadvertently move a PSQL instance and cause a failed validation state. Consider moving to Pervasive PSQL Vx Server. Pervasive PSQL Vx Server was designed with licensing features that simplify live migration of PSQL applications in a virtual environment. License validation for PSQL Vx Server product keys requires only VM hostname and all VM NIC MAC address remain the same in each VM. With Pervasive PSQL Vx Server, a PSQL application in a VM can move between physical servers automatically as part of a failover operation for example, or manually as part of a hardware upgrade - all without affecting the state of the product key.

Sql Server V11

Error: 'Your temporary Pervasive license will expire in xx days (on mm/dd/yy).' Error: 'Your temporary Pervasive license will expire in xx days (on mm/dd/yy).'

Products Sage 100 Contractor Sage 300 CRE Sage Estimating Description. Error: 'Your temporary Pervasive license will expire in xx days (on mm/dd/yy).'

. Temporary Pervasive error.

It says my Pervasive is about to expire. Pervasive expiration error. Why is my Pervasive key about to expire? Do I not have a permanent one? Disclaimer Support Sage Customer Support does not provide assistance for issues related to third party products or enhancements, hardware, report customizations, state or federal tax-related questions, or specific accounting questions. Please contact your Sage business partner, network administrator, or accountant for assistance.

Please review for additional information on the scope of Sage Customer Support Services. Cause The affected computer was unable to obtain a permanent Pervasive/Actian license from the Internet. This process can be blocked by software or hardware firewalls, or sometimes proxy servers. Resolution Note: This article only applies to Sage Estimating and Sage 300 Construction and Real Estate version 13.1 or higher. Symptom 1: After installation of 13.1 (or higher versions) and/or launching of Sage applications, the message will appear.

Symptom 2: A few months after installing a Sage product, another error with similar wording appears: “ The temporary Pervasive license on your server expired on MM/DD/YYYY” NOTE: If your Pervasive License Administrator shows that there is a 'Permanent & Active' license this will override the 'Temporary' license expiration date. If you are on 13.1 Rev 5 or earlier, installing 13.1 Update 5 or higher may resolve this issue and allow Pervasive to obtain a permanent license key properly. If after installing Update 5 or higher and you still have this issue, please follow the below steps. Have all users exit all Sage applications. At the server or workstation (non-Pervasive workgroup engine (WGE) install), perform the following:.

In the Services applet ( Start, Run: services.msc) window, restart the Sage Pervasive Licensing Service. After waiting a few minutes this should cause the server to get a permanent key.

Launch Pervasive License Administrator from Start, All Programs, Pervasive PSQL 11, Utilities, Pervasive (PSQL) License Administrator. Verify the following fields. Product = Pervasive PSQL 11/Actian PSQL 12 (server/workstation) - for versions 15.1 and later, the workstation no longer has a license. Product Key = blank. License Type = Temporary. Expiration Date = note the date.

Note: If a permanent Product Key is present for Pervasive PSQL 11/Actian PSQL 12 (server/workstation), then delete PLCSTATUS.txt file. See Step 3 to find location of this file. Do not perform any more steps. The message will go away. Check the date stamp in the PLCSTATUS.txt file found in C: ProgramData Sage Timberline Office 9.5 Shared Config (for Windows Server 2008, 2012, and Win 7 and Win 8) or C: Documents and Settings All Users Application Data Sage Timberline Office 9.5 Shared Config (Windows Server 2003 and Win XP). If the date in the PLCSTATUS.TXT file matches the same date as the Expiration Date in Step 2, leave it alone. Otherwise, delete it.

Close Pervasive License Administrator. Close all Sage Application on server/workstation. Open Services and restart the Sage Pervasive License service. After a few minutes you will see Pervasive Notification Viewer window display a Pervasive Product code. You can also launch Pervasive License Administrator ( Step 1). There will be a Product Code now present under Product Key for Pervasive PSQL 11/Actian PSQL 12 (Server/Workstation).

If PLCSTATUS.TXT file is still present in folder (see Step 3), delete it. If it is a workstation (Pervasive WGE install) that does not appear to get a permanent license, perform the following to gain a permanent license on this machine.

This is only for versions 14.1 and 13.1. Close out of all Sage 300 and Sage Estimating applications. Find and stop the w3dbsmgr.exe in Windows Task Manager or click on the blue Pervasive icon in the system tray and select the option to Stop/Exit. Browse to the location of the w3dbsmgr.exe on the machine (Example: C: Program Files or Program Files (x86) Pervasive Software PSQL bin ). Right-click and select Run as Administrator. In the Services applet ( Start, Run: services.msc) window, restart the Sage Pervasive Licensing Service. After waiting a few minutes this should cause the workstation to get a permanent key.

Contact Sage Support if these steps fail to obtain a permanent Pervasive/Actian license key. Related resources Category Configuration Entitlement Open Defect ID DevTrack Escalation 3915 ID:26508 Last modified: 520.