Problem Note 46776: Error exporting a dimension in SAS® Financial Management Studio
Exporting a dimension from SAS®
Financial Management might fail if the SASMeta - Workspace server is selected
before the SASAPP pooled workspace, workspace, and stored process servers in SAS
Management Console Object Spawner Server properties.
In this case, the following error is displayed in the SAS Financial
Management client.log:
02-15 15:23:18,089 [main][ERRORExportDimensionWizard] -
com.sas.solutions.etl.client.ETLException:
at
com.sas.solutions.etl.metadata.client.JMSDelegate.sendToServer(JMSDelegate.java:120)
at
com.sas.solutions.etl.metadata.client.JMSDelegate.export(JMSDelegate.java:131)
at
com.sas.solutions.etl.metadata.client.DimensionExportManagerDelegate.export(DimensionExportManagerDelegate.java:48)
at
com.sas.solutions.rcp.dimensions.internal.ui.wizards.ExportDimensionWizard.finish(ExportDimensionWizard.java:123)
at
com.sas.solutions.rcp.dimensions.internal.ui.wizards.ExportDimensionWizard$1.run(ExportDimensionWizard.java:88)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: com.sas.solutions.etl.client.ETLException: export() - u:sasadmfin
- Error during export of Dimensional Metadata.
at
com.sas.solutions.etl.metadata.ejb.DimensionExportManagerBean.handleAndRethrow(DimensionExportManagerBean.java:1955)
at
com.sas.solutions.etl.metadata.ejb.DimensionExportManagerBean.export(DimensionExportManagerBean.java:283)
at
com.sas.solutions.etl.metadata.ejb.DimensionExportManager_30r3sm_ELOImpl.export(DimensionExportManager_30r3sm_ELOImpl.java:63)
at
com.sas.solutions.etl.metadata.ejb.ExecuteMessageDrivenBean.onMessage(ExecuteMessageDrivenBean.java:191)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at
weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4547)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5058)
at
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.sql.SQLException: Unable to establish a connection: Unable
to return workspace. The application could not log on to the server
"SASCWA:8591".
at
com.sas.rio.MVALocalizedError.throwLocalizedException(MVALocalizedError.java:196)
To correct this problem:
- Log in to SAS Management Console as the unrestricted user, typically
sasadm@saspw.
- Expand Server Manager.
- Right-click Object Spawner and select Properties.
- Select the Server tab.
- Using the left arrow de-select SASMeta - Workspace Server to move it to
the Available Servers list.
- Using the right arrow select SASMeta - Workspace Server to move it to
the bottom of the Selected Servers list.
- Re-start the SAS Object Spawner.
Operating System and Release Information
| SAS System | SAS Financial Management | Microsoft® Windows® for x64 | 5.2 | | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Datacenter Edition | 5.2 | | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Enterprise Edition | 5.2 | | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 Standard Edition | 5.2 | | 9.2 TS2M0 | |
| Microsoft Windows Server 2003 for x64 | 5.2 | | 9.2 TS2M0 | |
| Microsoft Windows Server 2008 for x64 | 5.2 | | 9.2 TS2M0 | |
| Microsoft Windows XP Professional | 5.2 | | 9.2 TS2M0 | |
| Windows Vista | 5.2 | | 9.2 TS2M0 | |
| Windows Vista for x64 | 5.2 | | 9.2 TS2M0 | |
| 64-bit Enabled AIX | 5.2 | | 9.2 TS2M0 | |
| 64-bit Enabled Solaris | 5.2 | | 9.2 TS2M0 | |
| Linux for x64 | 5.2 | | 9.2 TS2M0 | |
*
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: | medium |
| Date Modified: | 2012-06-11 09:42:39 |
| Date Created: | 2012-06-09 08:47:41 |