Typically, the default port (1700 or 1717) set in your license file will be fine. However, you may find that there is another license manager running on one of those ports. If you select a port that is in use, you will see something like the following in you license server debug log file:
18:23:28 (lmgrd) The TCP port number in the license, 1717, is already in use.
Edit your license file and try another port such as 1700 or 1718.
Common Licensing Problems,Before you get started,Best Practices,Configuring Licensing,Installation,PADS Install and Licensing,Tip of the WeekTags:
This week we'll explore a related topic of how to change the environment for a single program session on Windows, via a simple batch script.
Two examples of why you might want to tailor the environment for a single session, each followed by a sample two-line script:
You want to change the MGLS_LICENSE_FILE to point to a different license server (1717@MyDxDserver) when you launch only DxDesigner, and have all your other Mentor applications use the current value that is stored in the environment variable.
Batch script example (make sure the file ends in ".bat" otherwise it won't execute when you run it):
When you double-click on the .bat (batch) file the MGLS_LICENSE_FILE environment variable gets changed to 1717@MyDxDserver but ONLY for DxDesigner. No other applications are affected by this change.
- The "start" keyword means the DOS window goes away as soon as the application appears. You can remove the keyword but then the prompt stays up until you close the application.
- To get the path to "viewdraw.exe" you can right click on the DxDesigner shortcut and copy and paste the "target" field.
- If you want the script to work regardless of which version you are configured for, you can reference the %SDD_HOME% environment variable instead of using an absolute path. In this case you would substitute the second line with "start %SDD_HOME%\wv\win32\bin\viewdraw.exe". In the 2nd example below we use the %SDD_HOME%.
You're running into a DLL conflict between DxDesigner and an application from another software vendor. You want to reduce the PATH variable used by DxDesigner to only the system values plus the required Mentor Graphics folders, while keeping the PATH value the same for all other applications.
Batch script example (make sure the file ends in ".bat" otherwise it won't execute when you run it):
Whether you want to deifferentiate multiple processes of the same name or simply see which options were used to start a process, the Windows 7 Task Manager will let you view the command line. This may help in finding which process is using a file or differentiating sessions. The possiblitie are many.
To enable the Command Line column:
Open Task Manager
Pull-down View> Select Columns
Scoll down and check Command Line
Your Task Manager will now have a column that will show you the command line used to start the process.
This week we'll explore a couple of very useful commands that you can run in the DOS prompt (cmd.exe) -
This command lists all of the processes that are running in memory, similar to opening 'Task Manager' and navigating to the 'Processes' tab. For example:
Image Name PID Session Name Session# Mem Usage ========================= ======== ================ =========== ============ System Idle Process 0 Services 0 24 K System 4 Services 0 3,668 K smss.exe 284 Services 0 232 K csrss.exe 392 Services 0 2,248 K wininit.exe 452 Services 0 520 K csrss.exe 464 Console 1 128,664 K winlogon.exe 508 Console 1 2,508 K svchost.exe 876 Services 0 17,176 K svchost.exe 908 Services 0 130,312 K svchost.exe 956 Services 0 15,900 K svchost.exe 988 Services 0 63,404 K
Useful for finding content within files or filtering the output from another command (for example, from 'tasklist'!). For example, to find the string 'pcbexpedition' in any files in the current directory and all sub-directories:
We can combine both the 'tasklist' and 'findstr' commands as shown below. Here we're looking to see if the notepad.exe process is running, and as you can see it is! (the process ID (PID) is 16952 and memory usage is 6,204K)
If you have a recent version of Enterprise Expedition flow, then you have likely encountered the iCDB Project Backup tool. In this Tip of the Week, I’ll explain the different types of backups the tool supports.
These are periodic backups done at a fixed interval, which may be configured by the user. Note that this backup will only occur if the design has changed. You may also configure how many backups you want to keep. Older copies get marked for purge. See also Application below.
This backup gets created when a project (design) is opened. The number of backup copies is user configurable.
This backup is created when a project is (design) is closed. The number of backup copies is user configurable.
This is legacy functionality that has been replaced by AutoSave (above). Interval and number of backups is user configurable. You do not need both Application and AutoSave enabled.
This is a system backup that is automatically created before repairing the design with DxDesigner Diagnostics. It is not user configurable by default.
This is a system backup that is automatically created before repairing the design with CES Diagnostics. It is not user configurable by default.
This backup is automatically created before the design is upgraded to new software version. It is not user configurable by default.
These refer to backups that are manually launched by the user from iCDB Project Backup utility. The user may configure how many of these backups to keep before they are marked for purge.
There are a few other backup types, but these are the most common ones. You can see them all from the iCDB Project Backup tool when you select Backup > Settings from the pull down menu in the iCDB Project Backup utility.
Note that many of the backup types appear greyed out in the settings dialog. By design, only the user level backups are configurable. You can change this behavior by modifying the iCDB Project Backup tools configuration file.
More information about this tool is available in the Concurrent Design Administrator’s Guide.
We are constantly editing environment variables in customer support and we know many of our customers access them frequently as well. Normally, you have to go through Start> Computer, right-click, select Properties, click Advanced system settings, click Environment Variables. Fortunately, you can cut about half that with a keyboard shortcut.
Windows Key + Pause/Break
Yes, it's that key way over on the upper right of your keyboard.
Hopefully you find this helpful. Free free to share your tips and tricks for quick access to frequently used windows or utilities.
By default, a user on Windows Vista, Windows 7, or 2008 Server will be prompted to approve any program they attempt to run if the software is not on a local file system. This is an annoyance for anyone installing Mentor Graphics software in client/server configuration, assuming of course your security policy does not require a user to be prompted. You could disable UAC entirely, but then you will also disable security features you think desirable.
You can disable the feature of prompting to authorize program execution on your intranet without turning UAC completely off using the Group Policy Editor. Use this tool to configure the system not to prompt the user when they run an executable from a network drive.
Procedure (Note: You must have administrator rights to perform this operation)
From the DOS command shell or from the run dialog, enter the command gpedit.msc
Go to User Configuration >> Administrative Templates >> Windows Components >> Attachment Manager. Double click on "Inclusion list for moderate risk file types".
Select Enable, and add *.exe in the box that says ‘Specify moderate risk extensions’.
You may also add any other known types you want to avoid being prompted for (.pdf, .bat, etc).
When you grant this exception it allows you to run an application with a .exe extension from the Intranet zone without a prompt, even when UAC is on. You will still be warned before an application from the Internet zone is allowed to run.
The risk you assume is that you must trust that any executables sitting on a network drive (drives mapped to a drive letter or drives you connect through a UNC path) are safe to run without seeing the warning popup.
When starting or troubleshooting a license server, it's handy to have a way to verify a license checkout without having to run an application. We have two utilities to help you do just that.
On Linux we use the mgls_ok utility. Most applications have the mgls_ok utility located within the application tree's bin directory. However, you may need to set the MGLS_HOME variable to the application tree or the mgls package within it. For a standalone licensing tree, set MGLS_HOME to the top level folder (e.g.: mgls_v9-7_2-3-0.ixl). You'll also need to copy the mgc.pkginfo file to the lib directory. You can download that here. Make sure your MGLS_LICENSE_FILE variable is set to your license file or license server (port@host).
Once you have the the MGLS_HOME and MGLS_LICENSE_FILE variables set and the mgc.pkginfo file copied, the command to check out a license feature is simple:
$ $MGLS_HOME/bin/mgls_ok msimhdlsim
Checking availability of "msimhdlsim".
License granted through "msimhdlsim".
On Windows, we use the pcls_ok utility which provides a GUI. With the licensing software installed, you can access the pcls_ok utility from the Start Menu> All Programs> Mentor Graphics Licensing> pcls_ok. You can also navigate to C:\MentorGraphics\Licensing or possibly find pcls_ok in your applications start menu or tree. Here's an example of the pcls_ok interface:
The nice thing about the pcls_ok interface is it shows you the value of MGLS_LICENSE_FILE, which makes it easy to verify and know where you're attempting to get licenses from.
To check out a feature, just pick one from your license file and type or paste it into the Feature: field. Then, click Apply. A successful checkout will look like this:
If the checkout fails, A dialog will appear with an error message.
If you get a licensing error from one of your applications, aside from ensuring licenses are available and searching SupportNet for the error message, you can use our Mentor License Utility (MLU) to generate a detailed diagnostic report that may help you or one of our CAEs determine the root cause.
If you find that Windows is taking far too long to startup, or maybe you're getting some annoying system tray alerts from mysterious programs that you've never installed, a good place to start is by looking at the Windows startup programs. Here are some techniques that I like to use to find and disable those unwanted startup programs:
Note: Some startup programs may run as part of your company's corporate policy. If you're not sure whether to disable a startup program you should check with your local I.T. department.
Check the Startup folder in your Windows Start Menu:
Most of the other startup program entries can be found in the Windows Registry; better to use MSConfig
Given the risks of editing the Windows registry, it's safer to use the Microsoft MSConfig program to disable these entries. You even access the above mentioned startup entries at the same time
To start MSConfig just go to the Start>Run area and type in msconfig
Another option is a freeware utility from Microsoft called Autoruns
Be warned it is not for the novice user (there are MANY options!)
For most users the Logon tab is where you will go to find and disable startup entries
Troubleshooting a variety of networking problems typically involves frequent use of the ping command, which can quickly tell you whether or not there is a route between hosts. But what if ping returns with zero packet loss yet you still have problems? Those TCP/IP packets often have to travel through routers or switches and those points can create problems. Fortunately, there's a very handy utility on Windows called pathping that will trace the route between hosts and give you some data on performance or potential bottlenecks. This can be very helpful in diagnosing network problems, especially those related to latency.
Here's an example of using pathping:
Tracing route to sliver.company.com[188.8.131.52]