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

Similar Messages

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 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

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

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

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.

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

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.

Why does my LabVIEW Run-time server return the message "source does not exist Last UI message: Start Execution"?

I am trying to build a stand-alone application on a target pc for which I have built a LabVIEW server that TestStand can use as an adapter.
In order to do this, I searched this site and found the topic: "How do I build and Use the LabVIEW Operator Interface as a LabVIEW ActiveX Run-time server?" After following the procedure to the letter, I ran the testexec.exe file as instructed and loaded my sequence file. As soon as I try to "Single Pass" or "Test UUT" I get an error which says "source does not existLast UI message: Start Execution". This error appears when running the testexec.exe file on the target pc or the development pc.
I have found though, th
at if I open the Operator interface through the Start: Programs>National Instruments>TestStand>Operator Interfaces>LabVIEW then the sequence file runs without these errors.
Any ideas why this is happening?

Hello Robroy,
The KB you mentioned explaines how to build the LV Operator Interface (OI). So, I assumed you built the LV OI and also configured the LV adapter to use the TestStandGUILVRTS server without problems.
The error you are getting may be due to missing VIs. In other words, the LabVIEW OI may not be finding all the VIs your sequence is calling.
In order to deploy sequences that call VIs, you need to first run Tools >> Assemble VIs for Runtime Distribution. This tool gets all the VIs your sequence needs and saves in a separate directory.
For more information, you may check the TestStand User Manual chapter 17, it describes how to distribute TestStand and sequences.
Regards,
Roberto Piacentini
Applications Engineer
National Inst
ruments
www.ni.com/ask

While creating Update rules -"Error Info source does not exist"

While creating an update rule I am getting an error that Info source doesnot exist though the inf source is active.
here is error:
No communication structure exists in version abc... A
Message no. RSAU251
Diagnosis
In order to be able to maintain the update rules an active communication structure must be available.
Procedure
This error message can have two causes.
No active communication structure exists.
Activate the communication structure in the Data Warehousing Workbench.
No communication structure exists for the InfoSource.
Create a communication structure in the Data Warehousing Workbench for the InfoSource.
<<text removed>>
Thanks,
Vasu
Edited by: Matt on Apr 26, 2010 9:31 AM

Hi Vasu,
as it clearly shows below message
No communication structure exists for the InfoSource.
Create a communication structure in the Data Warehousing Workbench for the InfoSource.
Create an info source first and assign it to your datasource and map the fileds in transfer rules and activate it.
Then try to create the update rules between your target and info source.
Hope this helps.
Regards,
Reddy

Error 7 goopsup - source does not exist

The test sequence works fine on the development machine, but I get the error, mentioned above, when I try to assemble the test sequence VIs for run time distribution.

Shannon,
It was pretty hard to locate the vi that had caused the problem because the error message did not contain any information that could help, such as step or vi name. When I narrowed the problem to a particular test sequence I saved it into a separate sequence file by copy/paste the sequence. Then I opened the VI from the new sequence file by Edit code and saved the vi because it showed that it was changed.
I tried to assemble the VI of the new sequence and I did not get any errors: the problem disappeared. Now I can assemble the VIs of the original test sequence.
I think the problem was caused by a bad subVI path that was fixed when the VI was opened, then saved.
To summarize, I would say the following: the major problem was to understa
nd and locate the problem.
An appropriate error message with the step and vi names could help to fix it sooner.
Peter

Error 7 occured at Advapi32.dll-source does not exist.

I'm using LV 6.02 and W2k Sp2. I'm trying to build an application that worked fine with Sp1. Any idea?
Andras Ferencz

Are you trying with the correct path? If your vi is included in a llb, you must know that current path function gives the name of the llb too, and if an executable, current path gives the exe name in the path, so you must handle this.
Hope this helps

Configured diectory does not exist

Hi All.
I have a File to rfc scenario.. where I have to read the file from location 10.100.10.20 from the directory data\source.
I have given the path in the sender channel as 10.100.10.20\data\source .
The comm channel results with error configured diectory
10.100.10.20\data\source does not exist
Any idea on this??
I am using NFS protocol...

Hi Ravindra,
Suppose, if you use Transport protocol is FTP,
Then, you have to specify like this in Sender Communication Channel.
Transport Protocol : FTP
Message Protocol: File
Source Directory: \data\
File Name : your file name
See the below link, it might be helpful to you.
http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/content.htm
Hope this helps to you.
Regards,
P.Rajesh
Edited by: Rajesh_1113 on Apr 24, 2011 7:06 PM

Creation of Remote Partition DB: datasource with ID does not exist in the collection

Hi,
I tried to create remote partitioned DB. Followed the below link to create it.
http://msdn.microsoft.com/en-us/library/ms174751.aspx
In 'partition Type selection' wizard, I selected the remote data source and landed in below error.
'datasource' with 'ID' = 'XXXX' doesn't exist in the collection
Can some one help me to resolve it?

Hi Hsadham,
According to your description, you are creating a remote partition with the error "'datasource' with 'ID' = 'XXXX' doesn't exist in the collection“,
right?
As you can see on that link,
If you get an error indicating the data source does not exist in the collection, you must open the project of the storage database, db-storage, and create a data source that points to the master database, db-master.
So in your scenario, please open the project of the storage database, db-storage, and create a data source that points to the master database, db-master. And then check if this issue persists or not. Besides, please ensure that all the prerequisites had
been done in your environment and the configuration steps are correct.
Regards,
Charlie Liao
TechNet Community Support

Source Does not exists

Similar Messages

Maybe you are looking for