Error Building Source Distribution

Hello group,
I'm trying to build a Source Distribution in LV8.6.
The application is used to drive a LV USB NI-8451 SPI adapter (among other things), so I have installed the SPI drivers in the default folder "C:\Progran Files\National Instruments\Labview 8.6\resource\objmgr\"
The source files for the project are located on our company's network drive, mapped as "S:\Machine_Plant-Eng\".
But when I try to build the source distribution, it is looking for the files to drive the SPI at "S:\Machine_Plant-Eng\ Progran Files\National Instruments\Labview 8.6\resource\objmgr\"
I don't know how to repoint the Project so it finds the correct files in the correct places.
Thanks,
Mike

check the "installer source location" under "additional Installers" in the "installer properites" and browse to cate the "S:\" drive (the complete path)
Regards
Guru (CLA)

Similar Messages

Error building source distribution of a project containing real-time utility VIs

I'm using Labview 8.0.
When building the source distribution of a project I get the following message:
An error occurred while building the following file:
C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\real-time\rtutility.llb\FPC pad/strip string to size.vi
I'm using "RT reboot controller.vi" and "RT ping controllers.vi" in the project.
Anyone can tell me how to solve the problem?
Is it correct that the filename of a VI contains the character "/"? (FPC pad/strip string to size.vi)

Hi!
You fall in a LabView library error..sorry.
As you have imagined the problem is the slash in the filename and to solve you have to remove it. Go to ..\National Instruments\LabVIEW 8.0\vi.lib\real-time\rtutility.llb and rename the file.
Let me know if this solve.
Ciao
Clara
AE Manager
NI Italy

Error 7 occurred while building source distribution in labview 8

I can build exe file and installer for my project. But while trying to build source distribution i got an error. Error description is as follows:
Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine.vi -> SDBUIP_Build_Invoke.vi -> SDBUIP_Build_Invoke.vi.ProxyCaller
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 Linux.

Hi Andy,
FYI, initially part of this project was developed in LabVIEW 7.1 and now I have
converted all the project files to LabVIEW 8.0. This was done by mass compiling and
saving all the VIs.
It is possible for me to build source distribution for some other programs. But I got the error while building source distribution for my current project. Same error was generated even while previewing the source distribution. This project contains some dynamic VIs. I had included them under the dynamic VIs and support files while creating EXE file. While building source distribution, i got an error message saying that :
"Unable to generate preview. An included VI or one of its dependencies does not exist. Open all Startup/Exported/Dynamically called VIs, recompile them (Ctrl-Shift Click the run arrow), and save them to update their dependencies.
\\Source code\Controls\Tests\Battery Current Calibration\Battery Current Calibration1.ctl
<Call Chain>Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine_Preview.vi -> SDBUIP_Build_Rule_Editor.vi -> SDBUIP_Item_OnDoProperties.vi -> SDBUIP_Item_OnDoProperties.vi.ProxyCaller
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 Linux."
For this error I rename the control, relink it in the code, and save the VI. Now I got an error message indicating different control. I was totally confused by this behaviour. What is the problem? Why the problem occured? What procedure to follow to avoid these kind of errors in future? I would be thankful, if I can get answers for my questions.
Thanks in advance.
Ramasamy.

Getting error in building source distribution

While building source distribution, I am getting an error
Error copying files.
Source: ..\Program Files\National Instruments\LabVIEW 8.6\resource\visarc
Destination: D:\Chirag\builds\Arduino LLB\Arduino LLB\data\data\visarc
Librarian Path Location.vi
Error 1 occurred at AB_Destination.lvclass:Copy_File.vi -> AB_Source.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
can someone please help me with this ??

Do you have multiple job servers in your environment? Did all the Job servers configured SMTP settings?

Error 1 occurred while building source distribution in labview 8.2.1

I can build exe file and installer for my project. But while trying to build source distribution on RT i got an error. Error description is as follows:
Error -1 occurred at Invoke Node in SDBUIP_Build_Invoke.vi->SDBUIP_Build_Rule_Editor.vi->SDBUIP_CreateNewWizard_Invoke.vi->SDBUIP_CreateNewWizard_Invoke.vi.ProxyCaller
When i click generate preview, i got an error.
Unable to generate preview. Invoke Node in ABAPI Dist read linkages.vi->ABAPI Dist Cmp Settings to Disk Hier.vi->ABAPI Get Settings From File2.vi->SDBEP_Invoke_Build_Engine_Preview.vi->SDBUIP_Build_Rule_Editor.vi->SDBUIP_Item_OnDoProperties.vi->SDBUIP_Item_OnDoProperties.vi.ProxyCaller
Thanks in advance.
Poolsak T.
Attachments:
rt_deploy2.zip ‏34 KB

Hi,
I would first try mass compiling the vi's within your project to ensure there aren't any unresolved conflicts. Moreover, it's intersting that you can create an application without problems but upon building a distribution, things go awry.
Do the vi's run on the RT target without error? Does the application run on the target without error? Or do they run on your host just fine and its when you attempt to deploy on to your RT target that this error occurs?
Let's see where this gets us.
Cheers,
Emilie K | National Instruments

Error building source distribution

I get an error when building source distribution saying:
"LabVIEW cannot find a file that is a dependency of a Startup, Exported, or Always Included VI.
File Not Found: The file at 'C:\Program Files (x86)\National Instruments\LabVIEW 2011\vi.lib\utf\common\conversion\utf_string_to_tag.vi' was expected to have the qualified name 'NI_UnitTestFramework.lvlib:utf_string_to_tag.vi', but has the qualified name 'utf_string_to_tag.vi'.
The missing file might be referenced by one of the libraries included in the build or by the file - OpenData.vi. To fix this issue:
- Open all Startup, Exported, or Always Included VIs, recompile them (CTRL+SHIFT Click the Run arrow) and save them to update their dependencies.
- Open all libraries included in the build and verify the existence and locations of referenced files. Also, try building with the additional exclusion option, "Remove unused members of project libraries", checked."
Any ideas why this happens?
Solved!
Go to Solution.

Obvious question, but have your tried the recommendations?
Reese, (former CLAD, future CLD)
Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home

Error 6 during Build Specification of My Source Distribution in Project explorer

While trying to convert a LV 8.0 application into a project file I get an Error 6. Message as Follows:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 6 occurred at ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> SDBEP_Invoke_Build_Engine.vi -> SDBUIP_Build_Invoke.vi -> SDBUIP_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Generic file I/O error.
NI-488: I/O operation aborted.
The error referenced a vi from a third-party labview driver for Iotech hardware.
Could the path be too long?

JT1958,
These types of errors are a bit tricky to diagnose. I would try the following, in order of easiness:
1) Mass compile your project by doing a <Ctrl-Shift-Run> on your top level VI to make sure your project is linked correctly. Sometimes if there is a bad VI reference somewhere you can have these types of problems.
2) The path being to long most likely isn't the issue, but if you suspect the IOTech driver, you may try taking it out of your code and see if that allows you to build a source distribution. If that works, try creating a simple project that contains VIs from the driver and see if you can get it to build. The point is to narrow down what specifically is causing the build to fail.
3) You can try to build this in LabVIEW 8.2 as some improvements to the source distribution builder were made.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Error Building LW 2010 Distribution Kit

I get the following error when trying to build my distribution kit on a factory test set PC. The same kit will build on my work laptop.
I have found various posts of similar problems building distributions with LW, LV, Test Stand, etc. but none are exactly like this and none of the other solutions has worked.
Ray

Hi rayt52,
Looking at a similar report of this error, found here
http://digital.ni.com/public.nsf/allkb/460D3470477CD3A486256D7100744A4B?OpenDocument
I am wondering if there is a difference in software installed on your machine from your laptop to your test machine. Specifically it looks like the NI Security Update has not been included. There were a couple of knowledgebase articles specific to this particular update indicating its importance, especially for pre CVI 2010 SP1 runtimes.
I am guessing this update is missing on your factory test machine. You can find more information on the mentioned update with these two articles:
http://digital.ni.com/public.nsf/allkb/E42DE5929616F5A08625792100766272?OpenDocument
http://digital.ni.com/public.nsf/allkb/C8EFBD23AFEA96F9862579210077D784
Hopefully that may help get things moving along for you
Regards,
James W.
Applications Engineer
National Instruments

LabVIEW 2013: Source distribution, destination path for post build VI changed?

Hi,
In a source distribution for an embedded target (Real-Time for instance) you specify both "Local destination directory" and "Target destination directory". Let's say the local directory is "C:\MyProject\MyModules\", and the target directory is "C:\" for instance. Then on my build machine my source distribution will end up in "C:\MyProject\MyModules\c\<source distrib files>", and I can then FTP everything from <source distrib files> to the root of my target's c-drive (or in some cases I can just deploy directly after the build, and LabVIEW will move the files to the target for me).
You can also specify a Post Build VI that can do stuff to your source distribution after the build has completed. Such a Post Build VI has an input named "Destination Path" for use inside your Post Build VI, so you can find your files to operate on :-)
In LabVIEW versions prior to 2013 this destination path would be "C:\MyProject\MyModules\c\", but in LabVIEW 2013 the destination path is only "C:\MyProject\MyModules\" thus missing the target destination directory part. Now my Post Build VI can no longer find my source distribution files, unless I inside that VI hardcode the target destination directory - and that isn't a good solution.
Is this changed by design in LabVIEW 2013, or is it a bug?
Cheers,
Steen
CLA, CTA, CLED & LabVIEW Champion

I don't do a lot of (actually any) source distributions of embedded files, but I can tell you that there was a bug in earlier versions where during an application build, the destination path was reported incorrectly. Perhaps this is related.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Error building Erlang/OTP

I'm building Erlang/OTP R12B-4(*) on a T1000 server and seeing this error:
gcc: Internal error: Segmentation Fault (program cg)
Please submit a full bug report to
<URL:http://forum.java.sun.com/forum.jspa?forumID=905>.
I had the same error with the 4.0.3 which came installed on the system.
The context of the error is:
gcc -g -O3 -fomit-frame-pointer -I/usr/local/src/otp_src_R12B-4/erts/sparc-sun-solaris2.10 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DERTS_SMP -DHAVE_CONFIG_H -Wall -Wstrict-prototypes -Wmissing-prototypes -Wdeclaration-after-statement -DUSE_THREADS -D_THREAD_SAFE -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wa,-xarch=v8plusa -Ibeam -Isys/unix -Isys/common -Isparc-sun-solaris2.10/opt/smp -Isparc-sun-solaris2.10 -Izlib -Ipcre -Ihipe -I../include/internal -I../include/internal/sparc-sun-solaris2.10 -c beam/erl_bif_info.c -o obj/sparc-sun-solaris2.10/opt/smp/erl_bif_info.o
gcc: Internal error: Segmentation Fault (program cg)
Please submit a full bug report to
<URL:http://forum.java.sun.com/forum.jspa?forumID=905>.
make[3]: *** [obj/sparc-sun-solaris2.10/opt/smp/erl_bif_info.o] Error 1
make[3]: Leaving directory `/usr/local/src/otp_src_R12B-4/erts/emulator'
make[2]: *** [opt] Error 2
make[2]: Leaving directory `/usr/local/src/otp_src_R12B-4/erts/emulator'
make[1]: *** [smp] Error 2
make[1]: Leaving directory `/usr/local/src/otp_src_R12B-4/erts'
gmake: *** [emulator] Error 2
(*) http://erlang.org/download/otp_src_R12B-4.tar.gz

$ gcc --version
sparc-sun-solaris2.10-gcc (GCC) 4.0.3 (gccfss)
This is the version installed with the latest Solaris 10 5/09:
vances@earl$ pkginfo -l SUNW0gccfss
PKGINST: SUNW0gccfss
NAME: GCC for SPARC(R) Systems
CATEGORY: application
ARCH: sparc
VERSION: 4.0.3
BASEDIR: /opt
PSTAMP: sacrum20061020151241
INSTDATE: Jan 13 2009 22:10
STATUS: completely installed
FILES: 538 installed pathnames
7 linked files
62 directories
31 executables
354905 blocks used (approx)
The Erlang/OTP source distribution is available here:
http://erlang.org/download.html

Problem Building Source Distro

I can build my project into an EXE and Installer without problem but when I try to build a Source Distribution I get the following error:
As you can see the source file C:\Documents and Settings\Program Files\National Instruments\LabVIEW 8.6\resource\objmgr\daqmx.rc
does not exist. Of course not, you can't get to Program Files from Documents and Settings. Has anyone else seen this problem and/or found a workaround?
Message Edited by jmcbee on 12-16-2008 01:03 PM
CLA, CLED, CTD,CPI, LabVIEW Champion
Platinum Alliance Partner
Senior Engineer
Using LV 2013, 2012
Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
Solved!
Go to Solution.
Attachments:
SD Error.PNG ‏31 KB

Hi Stephen,
You are correct, I am programmatically registering NI-DAQmx events. The project seems to be too large to attach to this post, do you have another way I can get it to you?
CLA, CLED, CTD,CPI, LabVIEW Champion
Platinum Alliance Partner
Senior Engineer
Using LV 2013, 2012
Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.

Can not create source distribution from project

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 1 occurred at AB_Destination.lvclass:Copy_File.vi -> AB_Source.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller in Charge.

Hi JoshSat,
This error message can be confusing. Error code 1 is defined by both LabVIEW and GPIB and has a different meaning based on what software component gave the error. Since you receive the error when building a source distribution, it is most likely the LabVIEW error and not the GPIB error.
First, we will need to know more about your application – what it's doing, the version of LabVIEW, the OS version, use of GPIB, use of Shared Variables, etc. This KnowledgeBase may also provide some insight into the cause of this issue.
You might want to start out building a much smaller source distribution that can reproduce the same problem. You’re welcome to post that project after you've shrunk it down as much as possible, and I can try to build it over here.
Please let me know if you can provide any additional information on your program, and whether the suggestions provided above fix the problem.
Message Edited by lion-o on 01-10-2008 10:58 AM
Mike Lyons
National Instruments
http://www.ni.com/devzone

Locate 8.5 source distribution

I am building a standalone application in LV 8.5
When I try to build the installer, I get a screen which asks me to loacate the source distribution for 8.5. I am not sure where to find this.
Does anyone have an idea?
Thanks
PR

Find the attched screen
Attachments:
Installer error.JPG ‏160 KB

Error 1308.Source file not found with 9.4.2 Admin Install point

I'm including as much information in this post as possible to help narrow down my problem, so if it's too wordy I appologize.
I've created an Admin install point for Acrobat 9 patching it up to Acrobat 9.4.2 using the following commands in a batch file:
D:
cd \Adobe\Acrobat\AcrobatPro9
md \Adobe\Acrobat\AcrobatPro9AIP
start /wait msiexec /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP /Liv D:\Adobe\Acrobat\AcrobatPro9AIP\install900.log /qn
cd \Adobe\Acrobat\AcrobatPro9AIP
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcroProStdUpd910_T1T2_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install910.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd912_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install912.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd920_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install920.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd930_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install930.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd932_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install932.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd933_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install933.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd940_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install940.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd941_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install941.log /qn
start /wait msiexec /p D:\Adobe\Acrobat\AcrobatPro9\AcrobatUpd942_all_incr.msp /a AcroPro.msi TARGETDIR=D:\Adobe\Acrobat\AcrobatPro9AIP PATCHAIP=1 /Liv install942.log /qn
I rename the folder "AcrobatPro9AIP" to reflect the current version (e.g. "Acrobat9.4.2"), copy the folder to my DFS, create an MST with the Customization Wizard, and then deploy with Group Policy.
Before I deploy I always run a few test installations on two Windows XP 32-bit machines, and two Windows 7 64-bit workstations. I've been using this method to build my install point for the last 5 Adobe patches without a problem, but suddenly with version 9.4.2 my test workstations pop up with the following error during the installation via the standard installation method "msiexec /i acropro.msi TRANSFORMS=acropro.mst":
I built my installation package for acrobat9.4.1, 9.4.0 and 9.3.3 exactly the same way and the installations did not have this error. The file in question "Adobe.Acrobat.Dependencies.manifest" does not exist in my 9.4.1, or 9.4.0 package folders, nor does it exist in the 9.4.2 folder. Any suggestions?

I am having the same problem, all the relevant info was already covered in the "thewaker" post above.   I too have made a script to make a Admin install with patches up to 9.4.2. The script worked for 9.3.3 but when I remade the AdobeAIP for 9.4.2, I too got this error when installing it, even manually. (Error 1308.Source file not found. Adobe.Acrobat.Dependencies.manifest ) Running on Windows 7 32bit.
Here is my Script.
C:
cd\AcroBatPro9
md \AcrobatPro9AIP
start /wait msiexec /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP /Liv c:\AcrobatPro9AIP\install900.log /qn
cd \AcrobatPro9AIP
start /wait msiexec /p c:\AcrobatPro9\AcroProStdUpd910_T1T2_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install910.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd912_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install912.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd920_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install920.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd930_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install930.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd932_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install932.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd933_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install933.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd940_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install940.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd942_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install942.log /qn
I did notice though that the "thewaker" has added AcrobatUpd941_all_incr.msp to his script, which is a security update. Which may be "a" problem, but I don’t think this is related to the problem we are having.
Administrative deployment
Administration Installation Point (AIP) deployments must not apply a quarterly update AIP in which a security update was the most recently applied update. Because a quarterly update includes the changes implemented in all recent security updates, the quarterly update forcibly bypasses those updates entirely. To deploy a quarterly update from an AIP, create a AIP which includes only quarterly updates as follows:
    Acceptable:      Acrobat 9.0.0 -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) -> 9.2.0 (Quarterly) -> 9.3.0 (Quarterly) -> 9.3.2 (Quarterly) -> 9.3.3 (Quarterly) -> 9.4.0 (Quarterly) -> 9.4.1 (Security)
    Acceptable:      Acrobat 9.0.0 -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) -> 9.2.0 (Quarterly) -> 9.3.0 (Quarterly) -> 9.3.2 (Quarterly) -> 9.3.3 (Quarterly) -> 9.4.0 (Quarterly) -> 9.4.2 (Quarterly)
    Unacceptable: Acrobat 9.0.0 -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) -> 9.2.0 (Quarterly) -> 9.3.0 (Quarterly) -> 9.3.2 (Quarterly) -> 9.3.3 (Quarterly) -> 9.4.0 (Quarterly) -> 9.4.1 (Security) -> 9.4.2 (Quarterly)
Anyway.. Any help with this would be helpful as I would like to deploy it soon.
Thanks.

Error in source system in BI 7.0...

Hi,
When creating a source system in Bi 7.0, when i am going to t code- rsa1- client-right click and then check,it's giving an error like:
EDI- partner profile not available and then detail for this error is-- a partner profile cannot be found with this key- /DBICLNT300/LS
THIS INVLOVES THE KEY FIELD OF THE TABLE EDPP1-
PARNUM-PARTNER NUMBER
PARTYP-PARTNER TYPE
Please help me in solving this. Thank You.

Hello,
Try a restore on your source system (rightclick -> restore) This way idoc ports and agreements are regenerated between BW and R/3. If this does not solve the problem ceck this:
Hi,
Did you do a system copy for BW ?
Try a restore (rightclick on your source system) in most cases this will solve the problem.
If not check the notes below:
184322 Procedure after DB copy of BW source systems
886102 System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
325470 Activities after client copy in BW source systems
325525 Copying and renaming systems in a BW environment
184754 Procedure after BW database copy
184447 Building a BW-system landscape
184971 Notes on BW source system connections
140276 Error in source system assignment
524554 Storing destinations in the BW environment
538052 Maintenance of Myself destination in BW
Regards, Patrick Rieken

Error Building Source Distribution

Similar Messages

Maybe you are looking for