以前遇到smartplant licsense问题基本上PDS或3D,PID程序因某种原因异常中断引起的，一般客户端·重启或运行一下license回收工具就可以解决。实在不行的，第二天会自动释放license。
昨天碰到的很怪，即使过了一个晚上，license还是挂在那里。回收了及几次都没有成功。看了提示，说是connect refused。刚开始以为是windows 防火墙·引起的，关闭防火墙问题依旧。上网搜了，按照·下面文章的方法才得以解决。
（1）卸载并重装license manager
（2）先用netstat -noa，查看807端口所运行的进程号，到task manager中看pdlice。
http://www.asbuilt-dba.com/Forum/tabid/53/forumid/13/threadid/40/scope/posts/Default.aspx
Please find bellow troubleshooting for PDLicense:
Problem: SPF product tag is invalid
Solution:
When an invalid tag message pops up, the software is trying to move and validate the seats that are taken during the installation of the new key. Possible an older version of lice was installed before and the old key has not been removed before installing the new key. At the dos command enter pdlice -m and get the output to see if there is some weird seat tag there.
Remove key - Uninstall SW and verify registry, rebbot – install latest and generate new machine id and key.
Problem:Server Key file mismatch
Solution:
This problem has been addressed in SPLM 9.0.
This is the explanation and the work around: "The license file and the DSKFILSH.RTI file in the windows directory are not in sync. You can delete the DSKFILSH.RTI and not have to install a new key. The software will recreate the DSKFILSH.RTI if it is not there."
Problem:While trying to install key receive error:
Seat count is too low to transfer current reserved seats to new key
Cause:
The new key has less seats then are currently in use.
Solution:
You either have to exit out of the application which might result in loss of seat usage for the reminder of the time or you can setup the batch command to install the new key at a later time at night when the other key expires and everybody exited the application.
Problem:Message: SPLMFailed: [connecting socket] Connection refused – servername
Cause: Licensing service not started
Solution – check Install and start licensing service in Install and remove options or my computer – services
Check port 807 – firewall
check if the port 807 is available for pdlice in your Citrix Server is doing the following: 1) Open DOS Window and key in: netstat -noa 2) Look under the LOCAL ADDRESS column for port 807 (for example: 0.0.0.0:807), check the Process ID(PID) under the PID colum 3) Open the Task MAnager, select processes and enable the PID column in View --> Select Columns Look for the PID reported in step 2 and it should be assigned to pdlice.exe
Problem:Message: SPLM Failed : Invalid Key. Mismatching parameters
Cause: the physical network adapter is disabled.
Solution: Enable the physical network adapter
In SPPID – no license server defined
Problem: Error "Run-time error 481, Invalid picture".
Cause:
temp folder is deleted
through DOS window: SET and check the folder for TEMP and TMP variables and make sure that folder exists.
Solution:
Create temp folder
More information about how to enable or disable this option:
Do not use temp folders per sessionRequirements:
At least Microsoft Windows XP Terminal Services
Location: Computer Configuration\Windows Components\Terminal Services\Temporary folders\
Specifies whether to prevent Terminal Services from creating session-specific temporary folders.
You can use this setting to disable the creation of separate temporary folders on a remote computer for each session. By default, Terminal Services creates a separate temporary folder for each active session that a user maintains on a remote computer. Unless otherwise specified, these temporary folders are in %USERPROFILE%\Local Settings\Temp\
If the status is set to Enabled, per-session temporary folders are not created. Instead, users' temporary files are stored in a common Temp directory for each user on the server (by default, %USERPROFILE%\Local Settings\Temp).
If the status is set to Disabled, per-session temporary folders are always created, even if the administrator specifies otherwise in the Terminal Services Configuration tool.
If the status is set to Not Configured, per-session temporary folders are created unless otherwise specified by the server administrator
Problem:“Fatal SPLM failed: [Read Pipe] Garbled Data From SPLM (Client”)
Cause:
invalid version of SPLM on client –
e.g. could happen if customer install a PDS QF for 08.00.00.09 which was build with latest libraries and requires >=08.00.02.01.
Solution:
Upgrade client and server to 08.00.02.01
Problem:
Error “ -5009:0x8002802b" installing SPLM is some machines
Cause:
The problem seems to be related to the Install shield
Solution:
Rename the folders located in the following in "C:\Program Files\Common Files\InstallShield\Professional\RunTime"
Problem:Batch Iso seat not released
pdlice.exe is not in the exceptions list on the machine running the batch iso.
Ask the customer to make sure that pdlice.exe is in the exceptions list. Also check to see if pdsidf.exe is still in the task list (pdsidf.exe is the executable which actually takes the seat). If pdsidf.exe is still active, the error message should be 'Seat Not Recoverable -- Licensees Up'. Ask them to send us the scavenge report and also verify that the node name/tcpip combo for the batchiso machine in the report is correct.
Problem:PDLICE Failed: [Check Size] Server key File Improperly Modified - Reinstall –
This error occurs after the new key was successfully installed and the customer is trying to open PDS.
Cause:
1. unknown
2. pointing to incorrect location: Regedit --> HKEY_LOCAL_MACHINE --> SOFTWARE--> INTERGRAPH-->PDLICE_ETC--> Double-click on PDLICE_KEY_S and check the value it should be like: c:\windows\servlice.dat – verify the path
Solution:
Cleaned up machine (removing SW – registry , path and servlice.dat file. Rebooted and installed SPLM latest 08.00.02.01 – generated new machine id and installed new key.
The solution for the other problems, has been to remove the license key (pdlice -c), re-generate the machine id and install a new key.
To make certain that the license file was truly removed (BEFORE generating a new machine id), at a dos prompt enter:
more < c::SPLMLog
If the file is not there, you will get an error message that it cannot find the file. The license file MUST BE REMOVED for this to work. The software does not have to be removed and re-installed.
The problem was the server has McAffee products loaded
On a server running Terminal Server (application mode) you must set the server to install mode before installing the PDLICE license key. This is done from a command line by executing "change user /install". After the key is installed, change the mode back by executing "change user /execute" from a command prompt.
If it's not set to install mode, the pdlice_key_s value is set to
P:\Windows...., where the P: in my case is my home drive. Setting the server to install mode before installing the license key enables the entry to be made properly.
This is why it worked when I removed the software, then reinstalled it. The server automatically prompts you to set the server to install mode when you run an installation program - I didn't think of it for installing the license until I looked at the value of the registry entry
Problem:SPLM not working if PANDA Antivirus is installed.
Error: Connection reset by Peer
Solution:
After installing Panda, you have to enter Panda > Status>Security Protection Settings>Select Firewall>Select Programs with access to the network Settings>Turn off Automatically assign communication permissions. Then Add Program for pdlice.exe (inbound and outbound), license.exe (inbound and outbound), and pdshell.exe (inbound and outbound). Hopefully, by turning off, Automatically assign... you will be prompted on what to let through the firewall. I have NOT been able to get Panda to work if the machine is a license SERVER. It should be prompting when the machine is a license server and it does not seem to be working correctly.
Problem:Socket reset by peer
Solution: remove bmwebcfg.exe
I should add that the offending component comes from a company called ByteMobile. If you run process explorer you should see a process called bmwebcfg.exe if you do a google search you will get a lot of hits and a lot of PC tools that will remove it for you,etc.
Besides the air cards I don't know whatever applications may load it, but any time you get the message about socket reset by peer on the server, I would look for this particular executable, to see if it is the same problem.
Problem:Error: COULD NOT SET INSTALL DATE
While loading SPLM software (Not the License) we are getting error message "COULD NOT SET INSTALL DATE": The error message has been enclosed for your reference. (SPLMsnap.jpg). The registry entry and operating system detail also has been enclosed in snap_reg doc file
Before installing SPLM we had removed PD_License server which was there on that server.
Solution: After reinstalling the SP2 the problem got solved.
Problem:Error scavenging: Connection reset by peer
Connection reset by peer – unable to scavenge license
Solution:
Firewall on client not setup properly (port 807, pdlice in exception list or IP address changed.
Machine not turned on
Problem:Error claiming a seat : Connection reset by peer
Connection reset by peer – unable to obtain license
Solution:
UNC path was specified in Log product usage. This will be fixed in 9.0 until then don’t use UNC path
Problem: License Database Locked By Another Process
When a new license key is installed with PDS users working and the SPLM software is left open, when the user close PD_Shell they get the following errors:
- License Database Locked By Another Process
- Error releasing seat - Please exit
Solution:
License need to be released with the scavenge command.
Close SPLM software after installing the license key.
Same error occurs if scavenge interferes with new license request. Simply try again.
Problem: Error –701 Occurred on OS local set to Korean, SPLM is NOT internationalized yet.
Remove key – uninstall SPLM – reboot – set language to English – install SPLM create new machine id – new key – also check path to windows – lok out foie strange characters.
-701 License file on machine is invalid - zero size and nonexistent (file in registry)
means that they deleted the previous license key.
There is a hidden file on a license server. This message means that this file is bad --
(1)they removed the license which deletes the file (not good with SPLM license server because the machine ID is stored here ) or
(2)the file does not exist (they didn't install SPLM and run GenerateMachineID on a non-PD_Lice license server).
If (1) occurred, then the only way to fix this is to generate a new machine id and send them a new key.
If (2) occurred, then the only way to fix this is to install SPLM, generate a new machine id and send them a new key.
If the customer has a PD_Lice license server, runs generate machine id (there is a registry entry written for machine id in this case and not a license file change since PD_Lice is already using it), removes pdlice, installs splm, then installs the key, he should not be getting -701 message
Other Install Key Error Codes:
-101 Process (Computer) Identifier does not match key.
-201 Network Identifier does not match key.
-301 Disk Identifier does not match key.
-401 Guid generated by hardware verification does not match key. (means that they re-ran Generate Machine ID AFTER sending us machine id for the key. There is no way to correct this problem without getting a new machine id.)
-501 SPLMid key is not in registry and license file is OLDer version.
-601 PD_Lice Current Version key is not in registry
Error: Connecting Socket Timed Out
1.) Stopping and starting service
2.) Server was still pointing at same server but it had record of old IP address. Unpointed server then repointed to current machine which worked fine.
If SPR doesn’t start but seats are available and the message complains about missing SRM keys:
use START>PROGRAMS>SPR>SELECT MODULES and UnCheck all the modules.
Incorrect number of seats reported:
SPLM always shows the Total Seats Currently Checked Out as 2 more than the actual number listed in the details, etc.
Even if no seats are checked out, it still shows 2.
There was a bug in the first 8.0 release that caused this mismatch. If I remember correctly, it was fixed in 8.0.2. It doesn't really hurt anything, but the only way to get rid of it is to UNINSTALL key, then regenerate machine ID and receive a new key. The error could re-apear when the next new key is installed with the older 8.0 version over the existing key.