[jbosstools-issues] [JBoss JIRA] (JBDS-2901) TEIID70026 RAR file name supplied on operation is wrong or no such RAR file is currently deployed.

[CDW Engine (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

CDW Engine updated JBDS-2901:
-----------------------------

    CDW devel_ack: ?
       CDW pm_ack: +
      CDW blocker: +
       CDW qa_ack: ?
      CDW release: ?

    
> TEIID70026 RAR file name supplied on operation is wrong or no such RAR file is currently deployed.
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-2901
>                 URL: https://issues.jboss.org/browse/JBDS-2901
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: installer
>    Affects Versions: 7.1.0.GA
>         Environment: Windows 7 64 bit,ram 4gb,jdk 1.6 update 31
>            Reporter: Pachaimuthu S
>            Priority: Critical
>
> Dear sir/madam,
> After installed  Data Virtualization v 6 GA i tried to connect DB2 10.1,mysql 5.1 and mssql server 2008 database i was getting error message: 
>   TEIID70026 RAR file name supplied on operation is wrong or no such RAR file is currently deployed.
> at org.teiid.adminapi.AdminFactory$AdminImpl$BuildPropertyDefinitions.onFailure(AdminFactory.java:1191)
> 	at org.teiid.adminapi.AdminFactory$AdminImpl.cliCall(AdminFactory.java:1475)
> 	at org.teiid.adminapi.AdminFactory$AdminImpl.getTemplatePropertyDefinitions(AdminFactory.java:1156)
> 	at org.teiid84.runtime.ExecutionAdmin.refreshTranslators(ExecutionAdmin.java:659)
> 	at org.teiid84.runtime.ExecutionAdmin.refresh(ExecutionAdmin.java:618)
> 	at org.teiid84.runtime.ExecutionAdmin.connect(ExecutionAdmin.java:607)
> 	at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:192)
> 	at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:221)
> 	at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:165)
> 	at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125)
> 	at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742)
> 	at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650)
> 	at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143)
> 	at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:210)
> 	at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:100)
> 	at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.handleAlreadyStartedScenario(AbstractJBossStartLaunchConfiguration.java:132)
> 	at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossStartLaunchConfiguration.preLaunchCheck(AbstractJBossStartLaunchConfiguration.java:103)
> 	at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7StartLaunchDelegate.preLaunchCheck(LocalJBoss7StartLaunchDelegate.java:39)
> 	at org.jboss.ide.eclipse.as.core.server.internal.launch.DelegatingStartLaunchConfiguration.preLaunchCheck(DelegatingStartLaunchConfiguration.java:67)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:813)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
> 	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3537)
> 	at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3473)
> 	at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira