Problem Note 65264: Importing SAS®9 internal groups into SAS® Viya® might complete with unexpected results
When you use the sas-admin transfer Command Line Interface (CLI) in SAS Viya to import a SAS®9 package containing users and groups, the import might produce incorrect and inconsistent results such as the following:
- A group from SAS®9 is not created in SAS Viya on the first import. A second import might then create the group successfully.
- Members of the SAS®9 group are not added to the SAS Viya custom group that is created by the import.
- The transfer service log file might contain the following message: "skipping User because it does not support V9 Promotion”
To work around this issue, manually create the custom group in SAS Viya, and then add the desired memberships to the group.
The problem occurs with the SAS Viya identities service versions prior to 2.17.15.
You can determine the version of the identities service by running the following rpm command from the SAS Viya microservices host machine:
rpm -q sas-identities
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
To verify that the fix is installed, run the following command: rpm -q sas-identities. The identities microservice version returned from the rpm command should be 2.17.15 or later.
Operating System and Release Information
SAS System | SAS Viya | Microsoft® Windows® for x64 | 3.4 | | | |
Microsoft Windows 8 Enterprise 32-bit | 3.4 | | | |
Microsoft Windows 8 Enterprise x64 | 3.4 | | | |
Microsoft Windows 8 Pro 32-bit | 3.4 | | | |
Microsoft Windows 8 Pro x64 | 3.4 | | | |
Microsoft Windows 8.1 Enterprise 32-bit | 3.4 | | | |
Microsoft Windows 8.1 Enterprise x64 | 3.4 | | | |
Microsoft Windows 8.1 Pro 32-bit | 3.4 | | | |
Microsoft Windows 8.1 Pro x64 | 3.4 | | | |
Microsoft Windows 10 | 3.4 | | | |
Microsoft Windows 95/98 | 3.4 | | | |
Microsoft Windows 2000 Advanced Server | 3.4 | | | |
Microsoft Windows 2000 Datacenter Server | 3.4 | | | |
Microsoft Windows 2000 Server | 3.4 | | | |
Microsoft Windows 2000 Professional | 3.4 | | | |
Microsoft Windows NT Workstation | 3.4 | | | |
Microsoft Windows Server 2003 Datacenter Edition | 3.4 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 3.4 | | | |
Microsoft Windows Server 2003 Standard Edition | 3.4 | | | |
Microsoft Windows Server 2003 for x64 | 3.4 | | | |
Microsoft Windows Server 2008 | 3.4 | | | |
Microsoft Windows Server 2008 R2 | 3.4 | | | |
Microsoft Windows Server 2008 for x64 | 3.4 | | | |
Microsoft Windows Server 2012 Datacenter | 3.4 | | | |
Microsoft Windows Server 2012 R2 Datacenter | 3.4 | | | |
Microsoft Windows Server 2012 R2 Std | 3.4 | | | |
Microsoft Windows Server 2012 Std | 3.4 | | | |
Microsoft Windows Server 2016 | 3.4 | | | |
Microsoft Windows Server 2019 | 3.4 | | | |
Microsoft Windows XP Professional | 3.4 | | | |
Windows 7 Enterprise 32 bit | 3.4 | | | |
Windows 7 Enterprise x64 | 3.4 | | | |
Windows 7 Home Premium 32 bit | 3.4 | | | |
Windows 7 Home Premium x64 | 3.4 | | | |
Windows 7 Professional 32 bit | 3.4 | | | |
Windows 7 Professional x64 | 3.4 | | | |
Windows 7 Ultimate 32 bit | 3.4 | | | |
Windows 7 Ultimate x64 | 3.4 | | | |
Windows Millennium Edition (Me) | 3.4 | | | |
Windows Vista | 3.4 | | | |
Windows Vista for x64 | 3.4 | | | |
Linux for x64 | 3.4 | 3.4 | | Viya |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2019-12-23 08:50:12 |
Date Created: | 2019-12-17 12:52:40 |