With previous versions of Petrel with a basic developer licence, the application could be started from the command line with
petrel.exe -licensePackage Package1
That works just fine for Petrel 2011, 12 and 13. However with Petrel 2014, this approach fails with a message that the licence doesn’t exist or has expired.
Starting Petrel without parameters results in a new licence dialogue appearing, which lists the package as Bundle 1. specifying Bundle 1 and Bundle1 after -licensePackage makes no difference when trying to start from the command line though.
Does anyone know what I’m doing wrong or how licence packages are now specified for Petrel 2014?
asked Jun 9, 2015 at 14:13
David ArnoDavid Arno
42.4k15 gold badges85 silver badges131 bronze badges
At the command line, you pass the name of a profile, not a license or bundle.
You need to save a profile first: At the «License selection» dialog, select the licenses you need in the license profile, click the «Save selection as profile» button, and name your new profile (without spaces). Then pass this name as the -licensePackage argument.
answered Jun 10, 2015 at 6:55
0
The license stack was reengineered in Petrel 2014 and the notion of a default license packaged, e.g. Package1, is no longer supported.
«Bundle 1» fails because it is just a display name. You can, however, find the actual bundle id to use by right-clicking the bundle in the license dialog and select List users…. Look for the License id in the License users dialog that appears. The bundle id should look something like
Petrel_123456789_MAMAMAMA/aUA and use this as the -licensePackage argument.
petrel.exe -licensePackage Petrel_123456789_MAMAMAMA/aUA
Alternatively, you can create a profile in the license dialog and name it Package1, and use this as the -licensePackage argument.
petrel.exe -licensePackage Package1
answered Jun 10, 2015 at 9:23
1
Перейти к содержимому раздела
TechnologiCS
Форумы TechnologiCS
Вы не вошли. Пожалуйста, войдите или зарегистрируйтесь.
Дерево сообщений Активные темы Темы без ответов
[Закрыто] Проблемы с менеджером лицензий и Расшифровка Кодов ошибок
Страницы 1
Чтобы отправить ответ, вы должны войти или зарегистрироваться
#1 16 января 2009 13:54:41
- Елена Кузнецова
- Участник
- Неактивен
- На форуме с 2 декабря 2008
- Сообщений: 97
Тема: Проблемы с менеджером лицензий и Расшифровка Кодов ошибок
Уважаемые пользователи!
Если у вас возникли проблемы с менеджером лицензий, пожалуйста используйте следующую последовательность действий.
-
Внимательно прочитайте сообщение менеджера лицензий. Возможно у вас просто исчерпан лимит подключений или нет связи с сервером лицензий CSoft Development.
-
Если сообщение отсутствует, но есть код ошибки, поищите его среди приложенных ниже описаний. Возможно это подскажет вам путь решения проблемы.
-
Внимательно просмотрите лог файл менеджера лицензий, там содержится подробная информация о ходе его работы. По умолчанию лог файл находится в файле C:Program FilesCSoftCS License Serverflex.log или C:Program Files (x86)CSoftCS License Serverflex.log для x64 ОС.
-
Если выше перечисленные шаги не помогли разобраться вам самостоятельно, отправьте запрос с подробным описание ошибки на адрес soft@csoft.ru не забыв приложить лог файл и файл лицензий.
С уважением, служба технической поддержки TechnologiCS.
Коды ошибок менеджера лицензий
Errors marked with an ‘*’ indicates errors which should not appear in shipping software. These are errors intended to help the programmer incorporate FLEXlm in their product, and should be fixed before shipping.
Errors marked with ‘+’ indicate errors due to an operating system failure.
Error Description
-1 Cannot find license file
-2 Invalid license file syntax
-3 No server for this feature
-4 Licensed number of users already reached
-5 No such feature exists
-6 No port number in license file and FLEXlm service does not exist [pre-v6only]
-7 No socket connection to license manager server
-8 Invalid (inconsistent) license key.
The license-key and data for the feature do no match.
This usually happens when a license file has been altered
-9 Invalid host.
The hostid of this system does not match the hostid
specified in the license file
-10 Feature has expired
-11 Invalid date format in license file
-12 Invalid returned data from license server
-13 No SERVER lines in license file
-14 Cannot find SERVER hostname in network database.
The lookup for the hostname on the SERVER line in the
license file failed. This often happens when NIS or DNS
or the hosts file is incorrect. Workaround: Use IP-Address
(e.g., 123.456.789.123) instead of hostname
-15 Cannot connect to license server.
The server (lmgrd) has not been started yet, or
the wrong port@host or license file is being used, or the
port or hostname in the license file has been changed.
-16 Cannot read data from license server
-17 Cannot write data to license server
-18 License server does not support this feature
-19 Error in select system call
-20 [Obsolete]
-21 License file does not support this version
-22 Feature checkin failure detected at license server
-23 License server temporarily busy (new server connecting)
-24 Users are queued for this feature
-25 License server does not support this version of this feature
-26 Request for more licenses than this feature supports
-27 [Obsolete]
-28 [Obsolete]
-29 Cannot find ethernet device
-30 Cannot read license file
-31 Feature start date is in the future
-32 No such attribute
-33 Bad encryption handshake with daemon
-34 Clock difference too large between client and server
-35 In the queue for this feature
-36 Feature database corrupted in daemon
-37 Duplicate selection mismatch for this feature
-38 User/host on EXCLUDE list for feature
-39 User/host not on INCLUDE list for feature
-40 Cannot allocate dynamic memory
-41 Feature was never checked out
-42 Invalid parameter
-43 *No FLEXlm key data supplied in initializing call
-44 *Invalid FLEXlm key data supplied
-45 *FLEXlm function not available in this version
-46 [Obsolete]
-47 Clock setting check not available in daemon
-48 *FLEXlm platform not enabled
-49 *Date invalid for binary format
-50 *FLEXlm key data has expired
-51 *FLEXlm not initialized
-52 FLEXlm vendor daemon did not respond within timeout interval
-53 Checkout request rejected by vendor-defined checkout filter
-54 No FEATURESET line in license file
-55 Incorrect FEATURESET line in license file
-56 Cannot compute FEATURESET data from license file
-57 +socket() call failed
-58 [Obsolete]
-59 Message checksum failure
-60 Server message checksum failure
-61 Cannot read license file data from server
-62 Network software (tcp/ip) not available
-63 You are not a license administrator
-64 lmremove request before the minimum lmremove interval
-65 *Unknown VENDORCODE struct type passed to lm_init()
-66 *FLEXlm include file/library version mismatch
-67 [Obsolete]
-68 [Obsolete]
-69 [Obsolete]
-70 [Obsolete]
-71 Invalid TZ environment variable
-72 *Old VENDORCODE (3-word) struct type passed to lm_init()
-73 Local checkout filter rejected request
-74 Attempt to read beyond end of license file path
-75 +SYS$SETIMR call failed (VMS)
-76 Internal FLEXlm Error — Please report to Globetrotter Software
-77 Bad version number — must be floating point number, with no letters
-78 *FLEXadmin API functions not available
-79 FLEXlm internal error -79
-80 FLEXlm internal error -80
-81 FLEXlm internal error -81
-82 Invalid PACKAGE line in license file
-83 FLEXlm version of client newer than server
-84 USER_BASED license has no specified users — see server log
-85 License server doesn’t support this request
-86 License object already in use (Java only)
-87 Checkout exceeds MAX specified in options file
-88 System clock has been set back
-89 This platform not authorized by license
-90 Future license file format or misspelling in license file.
The file was issued for a later version of FLEXlm than this
program understands.
-91 ENCRYPTION_SEEDs are non-unique
-92 feature removed during lmreread, or wrong SERVER line hostid
-93 This feature is available in a different license pool.
This is a warning condition. The server has pooled one or more
INCREMENT lines into a single pool, and the request was made on
an INCREMENT line that has been pooled.
-94 Attempt to generate license with incompatible attributes
-95 Network connect to THIS_HOST failed.
The license file indicates THIS_HOST, and the server is
not running on this host. If it’s running on a different host,
THIS_HOST should be changed to the correct host.
-96 Server node is down or not responding.
See the system administrator about starting the server, or make
sure the you’re referring to the right host (see LM_LICENSE_FILE).
-97 The desired vendor daemon is down.
1) Check the lmgrd log file, or 2) Try lmreread.
-98 This FEATURE line can’t be converted to decimal format
-99 The decimal format license is typed incorrectly
-100 Cannot remove a linger license
-101 All licenses are reserved for others.
The system administrator has reserved all the licenses for others. Reservations are made in the options file. The server must be restarted for options file changes to take effect.
Сообщения 1
Тему читают: 2 гостей
Страницы 1
Чтобы отправить ответ, вы должны войти или зарегистрироваться
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| package petrel | |
| // Copyright (c) 2014-2022 Shawn Boyette <shawn@firepear.net>. All | |
| // rights reserved. Use of this source code is governed by a | |
| // BSD-style license that can be found in the LICENSE file. | |
| import ( | |
| «fmt» | |
| ) | |
| // Message levels control which messages will be sent to h.Msgr | |
| const ( | |
| Debug = iota | |
| Conn | |
| Error | |
| Fatal | |
| ) | |
| var ( | |
| // Errs is the map of Perr instances. It is used by Msg | |
| // handling code throughout the Petrel packages. | |
| Errs = map[string]*Perr{ | |
| «connect»: { | |
| 100, | |
| Conn, | |
| «client connected», | |
| nil}, | |
| «dispatch»: { | |
| 101, | |
| Debug, | |
| «dispatching», | |
| nil}, | |
| «netreaderr»: { | |
| 196, | |
| Conn, | |
| «network read error», | |
| nil}, | |
| «netwriteerr»: { | |
| 197, | |
| Conn, | |
| «network write error», | |
| nil}, | |
| «disconnect»: { | |
| 198, | |
| Conn, | |
| «client disconnected», | |
| nil}, | |
| «quit»: { | |
| 199, | |
| Debug, | |
| «Quit called: closing listener socket», | |
| nil}, | |
| «success»: { | |
| 200, | |
| Debug, | |
| «reply sent», | |
| nil}, | |
| «badreq»: { | |
| 400, | |
| Debug, | |
| «bad command», | |
| []byte(«PERRPERR400»)}, | |
| «nilreq»: { | |
| 401, | |
| Debug, | |
| «nil request», | |
| []byte(«PERRPERR401»)}, | |
| «plenex»: { | |
| 402, | |
| Error, | |
| «payload size limit exceeded; closing conn», | |
| []byte(«PERRPERR402»)}, | |
| «reqerr»: { | |
| 500, | |
| Error, | |
| «request failed», | |
| []byte(«PERRPERR500»)}, | |
| «internalerr»: { | |
| 501, | |
| Error, | |
| «internal error», | |
| nil}, | |
| «badmac»: { | |
| 502, | |
| Error, | |
| «HMAC verification failed; closing conn», | |
| []byte(«PERRPERR502»)}, | |
| «listenerfail»: { | |
| 599, | |
| Fatal, | |
| «read from listener socket failed», | |
| nil}, | |
| } | |
| // Errmap lets you go the other way, from a numeric status to | |
| // the name of a Perr | |
| Errmap = map[int]string{ | |
| 100: «connect», | |
| 101: «dispatch», | |
| 196: «netreaderr», | |
| 197: «netwriteerr», | |
| 198: «disconnect», | |
| 199: «quit», | |
| 200: «success», | |
| 400: «badreq», | |
| 401: «nilreq», | |
| 402: «plenex», | |
| 403: «badmac», | |
| 500: «reqerr», | |
| 501: «internalerr», | |
| 599: «listenerfail»} | |
| // Loglvl maps string logging levels (from configurations) to | |
| // their int equivalents (actually used in code) | |
| Loglvl = map[string]int{ | |
| «debug»: Debug, | |
| «conn»: Conn, | |
| «error»: Error, | |
| «fatal»: Fatal} | |
| ) | |
| // Perr is a Petrel error — though perhaps a better name would have | |
| // been Pstatus. The data which is used to generate internal and | |
| // external informational and error messages are stored as Perrs. | |
| type Perr struct { | |
| Code int | |
| Lvl int | |
| Txt string | |
| Xmit []byte | |
| } | |
| // Error implements the error interface for Perr. | |
| func (p Perr) Error() string { | |
| return fmt.Sprintf(«%s (%d)», p.Txt, p.Code) | |
| } |
2260
16
Ноя 16
#1
Несколько месяцев назад сохранял проект 2014-й версии в 2015-ю, таких ошибок не было…
«Save as»-ом сохранялся?
Попробуй открыть 2014, сохранить Save As его с новым именем, затем открой этот проект в 2015 и еще раз Save As-ом сохрани с другим именем
1659
16
Ноя 16
#2
Единственный работающий способ победить на текущий момент — это перетащить данные в новый проект через «reference tool». Остальные танцы с бубнами не помогают.
Но поскольку с этой ошибкой сталкиваюсь уже не первый раз, должно быть что-то в 2015 версии, что портит проекты.
10
15
Ноя 16
#3
А в проекте есть растровый каротаж?
Должно помочь открытие проекта с зажатым контрлом (с принудительным закрытием всех окон).
1659
16
Ноя 16
#4
iEU пишет:
А в проекте есть растровый каротаж?
Должно помочь открытие проекта с зажатым контрлом (с принудительным закрытием всех окон).
Растрового каротажа нет, но есть растровые карты. Открытие «без окон» не спасает.
692
2260
16
Ноя 16
#5
Unknown пишет:
Единственный работающий способ победить на текущий момент — это перетащить данные в новый проект через «reference tool». Остальные танцы с бубнами не помогают.
Но поскольку с этой ошибкой сталкиваюсь уже не первый раз, должно быть что-то в 2015 версии, что портит проекты.
Я стараюсь использовать копирование с reference tool в самом крайнем случае. У нас это напрочь убивает настройки геомеханической модели и приходится все создавать с нуля
10
15
Дек 16
#6
1659
16
Дек 16
#7
Home
Hackintosh
[Solved] Error: could not get license agreement- Quick Fix
With High Sierra, Apple introduced its new file system APFS (Apple File System) which is much faster and is more secure. However, the speed and security do not work well with macOS High Sierra Hackintosh due to hardware limitations. When you install macOS High Sierra on a Windows PC or Laptop and if you using SSD (since APFS only supports SSDs) as installation drive, the installer automatically converts the SSD format to APFS format even if you have formatted it HFS+ or JHFS+.
![[Solved] Error: could not get license agreement](https://techposts.org/wp-content/uploads/2018/08/Solved-Error-could-not-get-license-agreement.png)
Now to fix this, there is a command that is revolving on the internet promising it prevents APFS conversion,
/Applications/"Install macOS High Sierra.app"/Contents/Resources/startosinstall --converttoapfs NO --agreetolicense
However, many people when trying to use this command, ended up with error: could not get license agreement (see the above screenshot). Therefore, today in this guide, we have mentioned an easier way of preventing APFS conversion as well as avoid Error: could not get license agreement that occurs when you run the command in order to avoid APFS conversion.
Why Avoid APFS Conversion
APFS is a modern file system and as I said, it’s more secure and offers improved read and write speed on SSDs but on Apple’s own hardware found in MacBook’s, iMac, and so forth. However, for all other hardware and Intel-powered PC or laptops, this is more of an issue. Here is a list of issues that you may face after installing High Sierra with APFS on a Windows PC or Laptop
- Slow boot Time
- Slower read/write speeds
- Kernel Panic
How to Fix Error: Could not get License Agreement
1. Disable APFS Conversion while High Sierra & Mojave Installation
The process of solving error: could not get license agreement is an easy process and I will explain it in much more easier language than what other blogs and sites have explained it. Additionally, I will soon upload a video guide showing the effective way of avoiding APFS conversion during macOS High Sierra or Mojave installation.
- Plug in the macOS High Sierra or Mojave Installer
- Turn On system and choose the High Sierra or Mojave installer as a boot drive
- Continue boot from USB installer that says Install macOS from Install macOS High Sierra/Mojave disk
- Click ‘Install macOS’ and choose the drive. Let it install the required installation files in the SSD drive
- The system will reboot itself and after reboot, from clover screen, again select the USB installer; Install macOS from Install macOS High Sierra/Mojave NOT the SSD
- This time, go to Utilities and open Terminal window
- Here type following command followed by the ‘Enter’ key
ls -l /Volumes
- From the volume lists, note down the name of SSD volume where you are installing the macOS
- Type
cd /Volumes/SSD_Drive_NAME and press ‘Enter’
Replace SSD_Drive_Name with the name of your real SSD volume where macOS is being installed
- Now type
cd “macos install data”
Vi minstallconfig.xml
- Press ‘I’ letter on keyboard and then move the cursor to ‘ConvertToAPFS’. Below this, the value is true, move the cursor to ‘true‘ and use delete key to remove it
- Now type ‘false‘
- Press letter ‘I’ and then type :wq to quit vi editor after saving the edits. In case you messed up things, type :q and Enter to quit without saving and restart again by typing the above-mentioned commands
- Once you successfully changed true to false, close the Terminal Window and restart the system
- Now this time, from clover boot loader screen, choose the SSD as the boot drive and this will begin the macOS High Sierra or Mojave installation without converting the SSD file system to APFS
For guides on complete macOS installation and required files, please visit following blog posts: Install macOS 10.13.5 on 8th Gen PC or Laptop- CoffeeLake Hackintosh
Now restart the system and this time select the SSD drive from the clover bootloader and continue the installation process.
After installation and setup are complete, go to About System, System report and click Storage. It shows HFS+ Journaled partition. This means your attempt to avoid APFS conversion was successful and without dealing with error: could not get license agreement.
About The Author
Ravi Singh
An Avid learner, a Tech Enthusiast and the founder of TechPosts Guides, Ravi is a Raspberry Pi fan and an open-source lover. He spends most of his weekends working with IoT devices and playing games on the Xbox. He is also a solo-traveler who loves hiking and exploring new trails.
Follow him on .Twitter, Facebook, and YouTube.
There are a few reasons why this error can occur:
- The DAEMON line in your license.dat file is incorrect or missing.
- The SERVER line in the license.dat file on a client does not match the license.dat file on the server.
- The TCP port number used to communicate with the license server is already being used by another application.
The DAEMON line in your license.dat file is incorrect or missing.
For license server, the DAEMON line should read:
Windows
DAEMON MLM $MATLABetcwin{32|64}mlm.exe ($MATLABflexlmmlm.exe for releases prior to R2010b on Windows)n(where $MATLAB is the MATLAB installation directory)
Linux/Mac
DAEMON MLM $MATLAB/etc/glnx{86|a64}/MLMn(where $MATLAB is the MATLAB installation directory)
(NOTE: prior to R2011a, the DAEMON line on Linux/Mac was «DAEMON MLM $MATLAB/etc/glnx{86|a64}/lm_matlab»)
NOTE:
Once you have made changes to your license file, be sure to restart the network license manager for these changes to take effect.
The SERVER line in the license.dat file on a client does not match the license.dat file on the server.
If you are running MATLAB using a concurrent license and you are on a client machine, make sure the SERVER line in your license.dat file matches that of the license.dat file on your license server.
The license file on the client machine varies depending upon operating system and version. For R2008a and above, the license file is generally called network.lic and is located in $MATLABlicenses (where $MATLAB is the MATLAB installation directory). For versions prior to R2008a, the license file will generally be the following:
Windows
$MATLABbinwin32 (for 32-bit MATLAB)n$MATLABbinwin64 (for 64-bit MATLAB)
Linux/Unix/Mac
(where $MATLAB is the MATLAB installation directory)
The license.dat file on the server machine is located in:
$MATLABROOT/etc ($MATLABflexlm for releases prior to R2010b on Windows)
(where $MATLAB is the MATLAB installation directory)
The TCP port number used to communicate with the license server is already being used by another application.
Make sure that the ports set are not being taken by another program. You can usually find this information by running the «netstat» command.