Data Source does not exist in version A.

Dear Experts,
I have created Data Source in R/3 ( ECC ) by t. code rso2. If am trying to display Data source by t.code RSA2 . It gives message
Data Source does not exist in version A.
Regrads,
Anand Mehrotra.

Hi Anand
RSO2--->Put DataSource name -
>Change button -
>Save -
>It should open a new screen with DS header data -
> From Menu ( DataSource -
>Generate).
Now you should be able to see your datasource.

Similar Messages

Data source does not exist

Dear all,
am extracting the data from Vistex datasource,IRM/LIS_RM_IPCRASP IP CR Agreement Conditions
after activating in RSA5 i can able to see in RSA6
but while activating the data source after the extract structure has successfully generated,
the system showing data source does not exist
plz help me

hi,
when i click the maintain button save button will appear,
but in my case this save button not highlighting...
when i check in ST22 the system proposed error mesage is table illegal statement,
i found this error in many forums but its not related to datasource actvation,
plz anyone giv me solution as soon as possible...
regards
Edited by: gadhatharan thirunavukkarasu on Oct 15, 2011 7:57 AM

Compiling a vi with link to an external non NI dll = error 7 "source does not exist""

I'm trying to compile a vi using Application Builder. The vi contains a number of links to drdaq32.dll (a dll to give access to Picotech�s DrDAQ data aquisitiion unit. This is connected via the parallel port and comes with a BNC connector and a high impedance input suitable for pH probes). Communication with the dll is via code interface nodes).
System:
LabVIEW v. 6i
Windows NT4
DrDAQ and DrDAQ.dll via parallel port (lpt 1) www.picotech.com
Code interface node calls to the dll use a standard (WINAPI) calling convention and �run in UI thread�
When I try to build, I get the error
"Error 7 occured at ......drdaq32.dll - source does not exist"
The source does exist. I hav
e got the same error with the dll in the same directory as my vi and in a sub directory data.
Why does Application builder refuse to see this file ??

I don't believe that this is the case.
Application builder is really very specific about what files are available and in what state. Though it is not really documented anywhere to my knowledge, the proper steps to building an application are as follows:
Before doing this, LabVIEW should be closed, and all other VIs out of memory.
1. Open your top level VI.
2. Click the run button to recompile
3. Choose "Save All" from the file menu
4. Close your top level VI and ensure that all VIs are saved properly.
5. Quit LabVIEW
6. Open LabVIEW - DO NOT open any of your VIs. Open LabVIEW from labview.exe via the start menu or other shortcut!
7. Open a new VI.
8. Open the application builder (tip, I went into the projects folder and
pulled a shortcut of the app builder out and onto my start menu, this opens the app builder fresh after LabVIEW has been exited.
9. Proceed with your build as normal.
The problem is that LabVIEW retains VIs in memory, even after they are all closed. If there is anything incomplete about these VIs, this will affect the build process. Unsaved VIs do not show up as being valid files (or something like that) to the app builder, thus if you didn't save even one single VI and try to build the application, you will get an error 7.
Step 1 is specific to your case, as recompiling ensures that all external connections are properly made.
If you still have the problem, post here and let us know.

Build Question: error 7 occurred at source does not exist

I have VIs built in LabVIEW 6.1. It works and built well. In LabVIEW
7, It works well. But when I try to build it. I got error.
I first use the mass conpile to compile VIs and then build the exe
with default settings. I got:
Error 7 occurred at source does not exist
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted,
or the file path might be incorrectly formatted for the operating
system. For example, use \ as path separators on Windows, : on Mac OS,
and / on UNIX.
NI-488: Non-existent board.
But It does not point out which file does not exist.
Anyone can help me out?

Hello yqin,
Here are some more KnowledgeBases that may pertain to your issue.
Error 7 When Building Applications and DLLs That Use the LabVIEW Report Generation Toolkit
Why Do I Get Error 7 When Building an Executable from a Build Script?
Error 7 at Invoke Node When Building a LabVIEW Executable
If the above KnowledgeBases do not work, we will want to try the following procedure.
1. Open your Main VI.
2. Hold + a
nd click the run arrow (forces recompile).
3. Close the VI and mass compile it.
4. Keep the VI closed and build the application from scratch (do not use a script).
5. Ensure that all VIs called dynamically are included as support files before building.
Please let me know if you have any questions,
Matt
Keep up to date on the latest PXI news at twitter.com/pxi

Error 7 occurred at source does not exist

I have VIs written in LabVIEW 6.1 and works fine. I try to use LabVIEW 7 to build it. But I got error:
Error 7 occurred at source does not exist
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on UNIX.
NI-488: Non-existent board.
Application Builder: Error copying files.
It does not point out which file is not exsisted? Why?

Hello �
From your question, I understand that you are trying to build an executable for LabVIEW 7.0 of some VIs that were built in LabVIEW 6.1.
You need to save all the VIs and subVIs that will be contained in the executable (or DLL) in LabVIEW 7.0 first. For this, the only thing you need to do is to open them in LabVIEW 7.0 and re-save them. If you want to keep copies for both versions of LabVIEW, you could even create a different folder for the version 7.0 ones. When re-saving your VIs just go to File >> Save As and browse to the directory you just created.
Then, you will be able to build the executable for LabVIEW 7.0.
Another possible solution to the problem is what is mentioned in this 5F09C86256745006E4494?OpenDocument>Knowledgebase.
Hope this helps!
S Vences
Applications Engineer
National Instruments

Source Does not exists

Hi Friends!
Please, I need your help with this issue!!
I generate 'Export Datasource' in development server.
When I replicate them in Testing server, I replicate these as RSDS, and NOT as 3.x datasources (yes, was not a good idea)
Now in testing server, I can see the datasource, but when I try to 'access to 'Display' in the context menu, give me the error msg:
"The DataSource 8CRN_PPP (QBICLN00) does not exist"
The rules (RSDS from datasource to infocube), are inactive too, and when I try to display or activate this, give me the error msg:
"Source does not exists"
How can I solve this?
PLEASE, I NEED YOUR HELP!!
Edited by: SSap on Aug 14, 2009 2:12 PM

Hi,
Seems that your export datasource is having the problem. 1st check it the activate mode of your export datasource in dev n transport to testing.
whiloe transporting the dataflow yiou need to transport your export data source also. i hope you missed this object in your transport request.
Thanks
Aravinda

The DataSource 0CRM_LEAD_H does not exist in version A

Hi,
I am not getting any records on to BW side by any of the load(full,init/delta)
When checked RSA3 in source system(CRM) there are 5 records.
When checked RSA3 in source system(BW) it gives an error.
error:
DataSource 0CRM_LEAD_H is not defined in the source system
in (BW)Tcode RSA2 - for the DS 0CRM_LEAD_H
DataSource 0CRM_LEAD_H does not exist in version A
I checked RSA5 in crm and the DS is activated once again
Please suggest

No Nilesh,
Basis did some work around and was able to remote logon from SM59. But still the problem exist.
Now while installing business content I am getting an error (Logical system)
Error: Rule (target: 0GN_PAR_LSY, group: 01 Standard Group): Syntax error in routine
GN_PAR_LSY is an infoobject for Logical system.
Stuck up over here

Visual Composer 7.0: system (data source) does not appear

Hi...
There is a problem: system (data source) does not appear in Visual Composer 7.0
1. There is a connector MDM. It is made by PCD. It has been tested. The test is ok.
2. However, as the data source in Visual Composer a connector MDM does not appear.
3. This problem affects all types of connectors, but the Web Service Connector. Connector Web Service is always there.
What the .....?
P.S. The role of the creator of the connector is the same user of Visual Composer
Thanks...

Hi...
There is a problem: system (data source) does not appear in Visual Composer 7.0
1. There is a connector MDM. It is made by PCD. It has been tested. The test is ok.
2. However, as the data source in Visual Composer a connector MDM does not appear.
3. This problem affects all types of connectors, but the Web Service Connector. Connector Web Service is always there.
What the .....?
P.S. The role of the creator of the connector is the same user of Visual Composer
Thanks...

LV 8.5.1 AppBuilder error source does not exist

Hi,
I have a rather strange problem:
Every time I try to to build a VI that was converted from LV 7.1.1 to LV 8.5.1 I get an error that the source does not exist,
although the VI is there and the Preview-build does not throw an error :-/
When trying to build a VI created with LV 8.5.1 the build succeeds of course.
Does anybody have faced similar problems?
The VI and the project should be attached...
thx a lot,
Leo
Attachments:
SourceNotExisting4.zip ‏5 KB
SourceNotExisting5.zip ‏5 KB

Hi Johannes,
I have already converted and saved the VI to LV8.5.1.
Anyway, here are the steps to reproduce the problem:
1. Open the LV7.1.1-VI using LV8.5.1
2. Save it with LV 8.5.1
3. Create a new project containing the VI and having it as startup VI in an Application
4. Trying to build the application --> leads to the "source does not exist" error
Attached is the source VI (vers. 7.1.1) causing the problem.
thanks in advance,
Leo
Attachments:
Check_Pfad.vi ‏44 KB

Compiling a vi with link to dll = error 7 "source does not exist"

I'm trying to compile a vi using Application Builder. The vi contains a link to imaq.dll (a part of the NI vision pack).
When I try to build, I get the error
"Error 7 occured at Imaq.dll - source does not exist"
But the source does exist, and it is not hidden, read-only or blocked by security policies.
Why does Application builder refuse to see this file ??
I tried copying the file to the base dir of the vi, and added it to the build from there => same problem.
System:
LabView v. 6i
Imaq v. 2.5
Windows NT4

Hi Angelo,
If the vi is working properly under LV, then you can try to register the IMAQ.DLL
Execute the following command:
REGSVR32 "the complete path of IMAQ.DLL"
You should get a message that it has been registered; then try again.
Good luck,
Alberto

RFC destination R/3 Source does not exist., error key: RFC_ERROR_SYSTEM_FAI

Hi All,
I am getting the error "RFC destination R/3 Source does not exist., error key: RFC_ERROR_SYSTEM_FAILURE" when planning sequence (IP) is executed. Can some one help me please asap.
Regards
Kiran

Hi,
Please go to sm59 and check if the RFC connection exists for this source system. If its there, please double click on it and on next screen, go to Menu bar and click on Test-> Connection and then test -> authorisation.
If you get any error, thats the reason. If you dont find the RFC at all, thats the reason why you got error.
You may also check WE20 for partner profile, whether it exists or not.

Unexpected error;Primary key does not exist:CmscdomPK version=2,name=J2E

Hi I am getting the following error when i try to access the CMS related WebDynpro application.
First time i am able to access the CMS.I created the domain and track.after that i edited the Domain tab with new domain name J2E.During that time i tried to save the domain,its throughing the Primary key does n't exist error.I closed the application.Again when i tried to access the CMS.Its throughing the following error.
<b>Error stacktrace:
com.sap.tc.webdynpro.progmodel.controller.MessageManager$AbortMessageManagerException: Unexpected error; inform your system administrator - Primary key does not exist: CmscdomPK version=2,name=J2E
     at com.sap.tc.webdynpro.progmodel.controller.MessageManager.raiseMessageInternal(MessageManager.java:254)
     at com.sap.tc.webdynpro.progmodel.controller.MessageManager.raiseMessage(MessageManager.java:964)
     at com.sap.cms.ui.wl.Custom1.hasTracks(Custom1.java:860)
     at com.sap.cms.ui.wl.Custom1.wdDoInit(Custom1.java:277)
     at com.sap.cms.ui.wl.wdp.InternalCustom1.wdDoInit(InternalCustom1.java:990)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.doInit(DelegatingCustomController.java:73)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)
     at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.initAttributeMapping(AttributeInfo.java:596)
     at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:456)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:41)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:373)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:252)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:392)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)</b>
What causing the problem.I am not finding the way,where can i rectifything problem
Regards
Usman

Hi Usman,
Domain ID and CMS Server ID are also stored in the SLD when you create these for the first time. As of now you can just create one Domain and One CMS Server id.
If you have to edit it you may have to do the following.
1. Delete all the tracks under the domain id and the CMS server id.
2. Then in SLD. go to HOME -> CONTENT BROWSER -> SUBSET = LANDSCAPE DESCRIPTION
In the CLASS dropdown please select Change Management Domain. Select the domain that you had created and delete it.
Again in the CLASS dropdown select Change management Server. Select it and delete.
Note: Please ensure that all the tracks have been deleted before you delete SLD entries.
Now login to CMS again and create the Domain and CMS server again.
If possible please try this some where on a test machine if possible and then try in actual scenario.
Hope this helps.
Regards
Sidharth

Process Variant does not exist in version A:

Good day
I have changed an existing process chain by removing an InfoPackage that had no link to any other process but the 'start'. When I 'test' the chain the message: "Process Variant AND .... does not exist in version A" is displayed. I have not even touched the 'AND' process.
As a result the chain does not want to activate.
What am I missing here?
Thanks
Cornelius Faurie

Thanks for your quick response. Sorry, I did not give you all the information. The 'AND' process was still connected between two Ioad processes (One IP loads Mdata from a flat file, then the AND process, then the second IP load from CRM (0BPARTNER)) BUT there were two AND's with the same name. I think I removed the process of the one AND at one stage, but the second remained (Copy of the same AND).
I have removed the AND process in totality and created a new one and it is activating now.
Sorry, my stupidity.
Thanks anyway
C

Target data source does not support the AGO operation

Hi,
In BI Admin Tool, I join Essbase cube and relational source. Then I apply Ago function to Essbase measures. In BI Answer, I try to run query that includes Essbase Ago measures and relational columns(non measures), error message shows the following detail:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 22001] Target data source does not support the AGO operation. (HY000)
When I remove the relational columns or run Essbase current-date messures, the result is fine.
So, what's exact meaning of this error message? and does the relational columns (non-measure) support Essbase measures' Ago function?

to clarify:
fail case:
criteria
YEAR | YTD,gen03 | MONTH_NAME | SALES(YEAR_AGO)
cube dimension: year, ytd,gen03
relational source: month_name
cube measure using AGO(): sales(year_ago)
result: error messageSuccess case:
criteria
YEAR | YTD,gen03 | SALES(YEAR_AGO)
cube dimension: year, ytd,gen03
cube measure using AGO(): sales(year_ago)
result: success~! how can i solve it? thx

Layouts - Variant &1 does not exist for version &2 of layout module &3

Hi Sap All.
when i am trying to create IDOC's of type LAYMOD01 using LSMW with IDOC Object type ,there were some IDOC;s failing in SAP With status 51 saying as "Layouts - Variant &1 does not exist for version &2 of layout module &3".
the following below text explain you the error message related to one particular IDOC of type LAYMOD 01 which was failed in sap with status 51 :
Variant 6325 does not exist for version 0000 of layout module EC-83-0214
can any one explain me the reason on why the IDOC's were failed.
regards.
Varma

not required any more

Data Source does not exist in version A.

Similar Messages

Maybe you are looking for