Problem Note 39509: A no PostgreSQL user name specified in startup packet error occurs when synchronizing users on unix
In the SAS® OpRisk Monitor web application, you synchronize users in metadata by logging on to the web application as "admin", going to the administration tab, and selecting the link "synchronize users". However, the synchronize users activity might fail if you installed your server tier on unix, and you are using ODBC with a Postgres database.
In your stored process server log, you will see an error like the following:
2010-04-08T11:04:13,996 INFO [00000161] 4:admin - MPRINT(INSERT_USERS):
connect to ODBC as SASOPRSK_CONN (dsn="SASOPRSK");
2010-04-08T11:04:13,996 INFO [00000161] 4:admin - ERROR: CLI error trying to
establish connection: [DataDirect][ODBC PostgreSQL Wire Protocol
driver][PostgreSQL]FATAL: no PostgreSQL user name specified in startup
packet(File postmaster.c;Line
To work around the problem, add user, password, connection, and autocommit parameters to the postgres connection call in file ucmacros\orm_shr_mac_buildsasconnect.sas. The corrected code will look like the following:
%let xEPConnectSQL = connect to ODBC as &xEPConnectAlias.
dsn="&xDBIdentifier" user="&xDBUserID" password="&xDBPassword"
connection=global autocommit=no);
Operating System and Release Information
| SAS System | SAS OpRisk Monitor | Microsoft® Windows® for x64 | 4.1 | 4.2 | | 9.2 TS2M2 |
| Microsoft Windows 95/98 | 4.1 | | | |
| Microsoft Windows 2000 Advanced Server | 4.1 | | | |
| Microsoft Windows 2000 Datacenter Server | 4.1 | | | |
| Microsoft Windows 2000 Server | 4.1 | | | |
| Microsoft Windows 2000 Professional | 4.1 | | | |
| Microsoft Windows NT Workstation | 4.1 | | | |
| Microsoft Windows Server 2003 Datacenter Edition | 4.1 | 4.2 | | 9.2 TS2M2 |
| Microsoft Windows Server 2003 Enterprise Edition | 4.1 | 4.2 | | 9.2 TS2M2 |
| Microsoft Windows Server 2003 Standard Edition | 4.1 | 4.2 | | 9.2 TS2M2 |
| Microsoft Windows Server 2008 | 4.1 | 4.2 | | 9.2 TS2M2 |
| Microsoft Windows XP Professional | 4.1 | 4.2 | | 9.2 TS2M2 |
| Windows 7 Enterprise 32 bit | 4.1 | 4.2 | | 9.2 TS2M2 |
| Windows 7 Enterprise x64 | 4.1 | 4.2 | | 9.2 TS2M2 |
| Windows 7 Home Premium 32 bit | 4.1 | 4.2 | | 9.2 TS2M2 |
| Windows 7 Home Premium x64 | 4.1 | 4.2 | | 9.2 TS2M2 |
| Windows 7 Professional 32 bit | 4.1 | 4.2 | | 9.2 TS2M2 |
| Windows 7 Professional x64 | 4.1 | 4.2 | | 9.2 TS2M2 |
| Windows 7 Ultimate 32 bit | 4.1 | 4.2 | | 9.2 TS2M2 |
| Windows 7 Ultimate x64 | 4.1 | 4.2 | | 9.2 TS2M2 |
| Windows Millennium Edition (Me) | 4.1 | | | |
| Windows Vista | 4.1 | 4.2 | | 9.2 TS2M2 |
| 64-bit Enabled AIX | 4.1 | 4.2 | | 9.2 TS2M2 |
| 64-bit Enabled Solaris | 4.1 | 4.2 | | 9.2 TS2M2 |
| HP-UX IPF | 4.1 | 4.2 | | 9.2 TS2M2 |
| Linux for x64 | 4.1 | 4.2 | | 9.2 TS2M2 |
*
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: | 2010-05-26 14:44:54 |
| Date Created: | 2010-04-30 15:58:47 |
