Error building installer with additional traditiona ni-daq

I get an internal error 40 when I try to build an installeur with the additional traditional ni-daq installer
This is what I get: Hard to decript
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_Open.vi
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
Building deployment
Copying setup files
Setting merged database information
Setting product information
Setting developer part information
Starting final build
Validating...
Copying files...
Updating files...
Creating merged database...
Creating installer files...
Build complete successfully.
Copying additional setup files
Done building deployment
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
Done adding files
Preparing to build deployment
Copying products from distributions
*** Error: Internal error. (Error code -40)
*** End Error Report
Done building deployment

Champlain:
I hope all is well. I am sorry you are experiencing such issues with the application builder. Does this issue occur consistently or it was just a one-time occurence? You may try to do the following:
1. Delete the "Application" folder which was created after the unsuccessful builds.
2. Uncach the folder in the Build Specs
3. Copy your driver CDs to your hard driver and point to the newly created folder.
Please feel free to try this at your own convenience and let me know what you find.
Regards,
Rudi N.

Similar Messages

Runtime Error building Installer with NI-VISA Runtime

Greetings, I'm getting this error whenever I check the "NI-VISA Runtime" option in the installer app builder.
Everything builds fine when I check only the Runtime Engine. Shown below is what causes the RUNTIME ERROR and closes Labview Unexpectedly.
Any help you could provide would be very much appreciated.
Regards,
JD

Hi JD,
This is a relatively common error with the Application Builder that can happen for several different reasons, namely registry keys pointing to installations that no longer exist. The easiest way to identify the problem is to get detailed information about the installer build. Here are directions:
LabVIEW has the
ability to create a very detailed log of the events that occur when
building an application or installer. To enable this feature, open up
the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom
of the file. Save the changes and close the ini file. The LabVIEW.ini
file is usually located in C:\Program Files\National
Instruments\LabVIEW X.X
Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) .
To
find out where this temp directory is located, go to Start>>Run.
Type in "cmd". Then type "set". This will return all of your computer's
variable names.
Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
Navigate to this directory using Windows Explorer.
You
should see a file named "Name.log" where "name" is the name of your
build specification. For example, you might see "My Installer.log" if
the name of your build specification is "My Installer".
This will give you a more detailed log of the attempted build and, if I'm correct about why this particular build failed, show you which installer is expected at that registry. If the registry points to a directory without the necessary installer (i.e. VISA), simply delete the registry and allow the App Builder to prompt you to to point to the correct location.
Michael K.
| Michael K | Project Manager | LabVIEW R&D | National Instruments |

Error in installation with NW04S

Hi,
error : CJS-30196. SAPBC JSF Communication role is not assigned to the user SAPJSF.
i am getting the fallowing error in installation with NW04S. while trying to assign the above role to the user.any body help me with the solution.
Thanks & Regards
kiran.B

Hi,
Assign the Role <b>SAP_BC_JSF_COMMUNICATION_RO</b> to the profile of SAPJSF user in production client and restart the installation.
Regards,
Siddhesh

Error when building Installer with USI 1.5.0 with Labview 8.5

I used to build an installer with Labview 8.2 and included this additional installer USI 1.5.0 but now with labview 8.5 it gives me an error:
"Locate the "NI LabVIEW" distribution. LabVIEW needs to copy a component installed or updated by the distribuiton to conitnue building the installer"
Any advice

Hi reza_sed,
Thank you for contacting National Instruments. When you get this message, are you prompted for a location of this installer (CD drive or something)? Sometimes if components are installed together, certain dependencies are created. You might be able to add the installer to a LabVIEW 8.2 installer with no problem, but the installer cannot be found when using a different version of LabVIEW. You might try uninstalling USI, then copying the install files from the CD or from our website to your hard drive and then installing from there. Then, you should be able to include the additional installer.
Another thing that may be happening is that the LabVIEW Run-Time Engine you have for 8.5 does not support NI-USI. The full version of the Run-Time Engine supports NI-USI, but the web browser only version does not. Make sure you select the full version when installing.
Donovan

Cannot build Installer with NI-DAQmx Configuration Support 9.6.1

Running labview 2011 SP1 f2
All SW/Device Drivers are up to date. error code -21, see attached for more details.
Things tried:
Updated just about all NI software
repaired Labview, device drivers, OPC and DSC as individuals.
Running out of options, its something specific to my machiene, other developers can build this given the same setup.
Ideas?
Certified LabVIEW Architect
Attachments:
NI Build Error.docx ‏79 KB

-          The following are possible reasons and solutions for this error:
#1. Installer specifications file is corrupted. For example, an old version of an installer specifications file could have been copied into the project.
-Go to Tools>>Advanced>>Mass Compile and mass compile the directory where the error is located. Mass compiling is necessary for VI compatibility with a particular version of LabVIEW. If this does not work then delete the saved installer settings from the project window and create a new one with the same settings.
#2. Additional installer components have been overwritten
-Referring to the knowledge base Why do I get a Missing Distribution Error when trying to build an installer from LV 8.0, an installer build always refers to the original installer source. For example, if you are using the NI-DAQmx driver (with additional component MAX 4.0) and later install Measurement Studio (With additional component MAX 4.1) this will cause an error because the installer is still referring to MAX 4.0. Point the installer to the original content on the driver-cd or the hard drive.
#3. Installing drivers before you installed LabVIEW or Updating your drivers
-The same driver and LabVIEW version, which the VI was written in, must be used to build a functioning installer. If an upgrade has occurred then make sure to include updated versions of the run time engine and driver. The driver and LabVIEW versions can be upgraded , in which case you can include the updated version of the driver and run time engine when you try to include additional installers. Make sure that the driver is properly installed for the specified version of LabVIEW in order to upgrade code for new drivers and software. Make a back up of your current project for reference. Open the project in the specified version of LabVIEW and go to Tools>>Advanced>>Mass Compile and mass compile your code

Building installer with 8.5

I have built an application with Labview 8.5 and am trying to build an installer with the 8.5 runtime engine for a stand alone program. However the exe builds okay, but when I try to build the installer I get a message saying some components need to be load from real-time module 8.6.1 and it asks for the directory of the nist.id. I am not using any real time in my application. It seems as though this started popping up after I installed Labview 8.6. Anyone have any Ideas.
Regards,
Wade

Thanks for the Reply and link. I just placed the Labview disk in the disk drive and selected that directory so the installer builder could locate the file it was looking for, and then cached it. However I am curious as to why all of the sudden it needs the real time module 8.6.1. If my only additional installer is RT engine 8.5. Before I upgrade to NI DAQ 8.8 that came with LV 8.6 I hadn't gotten this request for the RT Module components while only requesting the RT engine for an additional installer. Anyways its no big deal now that I have the file cached. It doesn't ask anymore. Thanks.
Wade

Error building installer: this application has requested the runtime to terminate it in an unusual way

Hi,
I build an appliction using LabView 8.2 with Report Generation Toolkit for MS Office V1.1.1 on a WinXP SP3 system without any errors. When I try to build a coresponding Installer, I got the following error message:
This application has requested the runtime to terminate it in an unusual way.
Can anyone help me????
Solved!
Go to Solution.

Hi Gunnar,
Good Morning and I hope your well today. Thanks for your post onto the NI Discussion Forums.
There are several considerations and potential causes of the error. I will try my best to cover some of the potential causes.
Firstly, you've suggested that the Report Generation Toolkit is being used:
When building applications with Report Generation Toolkit VIs, you must complete the following additional steps:
1. From the Source Files tab of the Build Application or Shared Library (DLL) dialog box, click the Add Dynamic VI button to add the following two VIs to the application:
– _Excel Dynamic VIs.vi in vi.lib\addons\_office\_exclsub.llb
– _Word Dynamic VIs.vi in vi.lib\addons\
_office\_wordsub.llb
2. If the application you are building contains the MS Office Report Express VI, you must add any Word or Excel templates that you use to the built application. From the Source Files tab, click the Add Support File button to add the template files to the application. By default, the custom destination for the templates is the same as the path that appears in the Destination directory field on the Target tab with a data subdirectory appended. Do not change the custom destination for the files you add.
For example, if you are using the basic Excel template with the MS Office Report Express VI, add MSOffice_RGT_Template.xlt to the application. The basic template files are located in the templates\Report directory.
Have you done this?
Could you please send an image of your project and your installer options?
The problem was that I use Office toolkit and it was not compiled with LabVIEW 8.2:
I found a forum where the toolkit wasn't complied for LabVIEW 8.2. Could this be an issue I wonder?
I mass compiled the complete directory c:\program files\National
Instruments\LabVIEW 8.2 (it took quite a long time) and afterwards the
directory lvjpeg disapeared.
Have you tried this?
Runtime to Terminate Error:
1. Have you been having any trouble with LabVIEW - crashes or bug installation?
I would suggest repairing your installation of LabVIEW and the toolkit(s) using the Add/Remove Programs.
2. Also would it be possible to try building an installer on another machine?
3. I have seen that not enough Hard-disk space can cause this error - what is the status of yours?
4. Are you using any other drivers such as DAQmx or VISA?
I hope this information starts to help us locate the root cause of the trouble your having, and if you could answer the questions above and try my suggestions that would be great! if you could also gather the extra information about your installer options that would also really help supporting the issue further.
*edit:
5. Also the runtime error would suggest you've selected to include a runtime in your installer options - have you tried de-selecting this and see if it installer builds correctly? If it does, then we could then work on how to add the additional installer to your build.
Message Edited by Hillman on 04-01-2009 10:01 AM
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Build installer with NI-RFSA

Trying to build a LabVIEW 8.0.1 installer with
NI-RFSA 2.0.7 as one of the "additional installers". The installer builds fine, but when I run
the installer, I get "Fatal Error!! Required NIPathsDir property
LV85DIR is undefined" and the installer exits.
What,
exactly, needs to be included in an RFSA installer (e.g., the
documentation for NI-RFSA says it includes DAQmx, NI-SCOPE and MAX
already). Do I also need to include the LV 8.5 runtime engine?
JoeG
Joe Gerhardstein
Averna Test Systems
Certified LabVIEW Architect
http://www.averna.com
Attachments:
installererror.gif ‏2 KB

Figured it out. Some additional digging led to the use of the "setup.exe /log logfile.txt" command, which can be run from the command line (shell). This generates a log file which I used to find my problem.
See attached image.
In the Shortcuts section of my installer, I specified a subdirectory with the forward slash (/) instead of the normal windows backward slash (\).
NI: Please please please add this to your KB article on this problem. Also please please please consider flagging this error in the installer builder. There are many illegal characters for Windows that are well documented. I know this builder is probably cross-platform, but we know what the target platform is here!
Joe Gerhardstein
Averna Test Systems
Certified LabVIEW Architect
http://www.averna.com
Attachments:
slashslash.gif ‏12 KB

LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

I'm having a problem building an installer in LabVIEW 2011SP1.
It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
Now when I try to build the installer I get "The build was unsuccessful."
Possible reasons: Error generating preview for My Application 3.1.7.
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
*** Error Details:
Error in MDF API function: _MDFCommon_GetNextLogMessage
Error in MDF::GetInstance - MDF static instance is not initialized!
*** End Error Report
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.

I do have the LabVIEW 2013 discs but didn't install it.
I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
So now I need to distribute 2 runtimes with my application?!?!
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

Sld started giving error after installation of additional usage type.....

Hi Experts,
I had a BW server with dual stack (AS ABAP + AS Java only base u2013 No BI u2013 Java server). Everything was running fine and I have checked that http://server:port/nwa, http://server:port/useradmin and http://server:port/sld was browsable although I didn't configured SLD.
My BW developer team wanted to use BEX web reports and for the same I have installed following add on usage type as per note 883948 as I had only upto SPS9 as a default installation.
u201C
Components of EPC (UT_NAME = EPC) SAP NetWeaver 7.0 (2004s) >= SPS09 < SPS11:
|FILE NAME |DESCRIPTION
|EPBC*_.SCA |PORTAL CORE SERVICES 7.00
|EPBC2*_.SCA |PORTAL FRAMEWORK 7.00
|EPPSERV*_.SCA |PORTAL 7.00
|EPWDC*_.SCA |PORTAL WEB DYNPRO 7.00u201D
And
UTs of SAP NetWeaver 7.00 (2004s):
Components of BI (UT_NAME = BI):
|FILE NAME |DESCRIPTION
|BIIBC*_.SCA |BI INFORM. BROADCASTING 7.00
|BIWEBAPP*_.SCA |BI WEB APPLICATIONS 7.00 (SP <current
version>)
|BIBASES*_.SCA |BI BASE SERVICES 7.00 (SP <current version>)
|BIREPPLAN*_.SCA |BI REPORTING AND PLANNING 7.00
|BIWDALV*_.SCA |BI WEBDYNPRO ALV 7.00
|VCKITBI*_.SCA |VCKITBI
But after this I checked and found that browsing SLD (http://server:port/sld ) started giving erroru2026. The error says something like belowu2026.
The initial exception that caused the request to fail, was:
com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application ''sap.com/tcsldwd~main'' for
startup. Reason= Clusterwide exception: Failed to start application ''sap.com/tcsldwd~main'': The referenced application ''sap.
com/tcsldwd~businesssystem'' can''t be started. Check the causing exception for details. Hint: Is the referenced application deployed correctly on the server?
at at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
at at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
at at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
... 8 more
See full exception chain for details.
The Full exception chain is like belowu2026.
System Environment
Client
Web Dynpro Client Type HTML Client
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:39:25[UTC], changelist=413534,
host=pwdfm101), build date: Tue Dec 23 13:37:24 IST 2008
J2EE Engine No information available
Java VM IBM J9SE VM, version:2.2, vendor: IBM Corporation
Operating system Linux, version: 2.6.16.60-0.39.3-smp, architecture: amd64
Session & Other
Session Locale en_US
Time of Failure Wed Jul 29 08:53:29 IST 2009 (Java Time: 1248837809764)
Web Dynpro Code Generation Infos
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.sal.core.DispatcherException: Failed to start deployable object sap.com/tcsldwd~main.
at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.
java:404)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:317)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:143)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
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:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
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:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.services.sal.deployment.core.StartStopException: Failed to start the deployable object
'sap.com/tcsldwd~main'.
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.start(DeployableObject.java:184)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.
java:399)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:317)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:143)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
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:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
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:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: Failed to start application 'sap.com/tcsldwd~main'.
Check if all defined references are deployed on the engine.
at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.start(WebDynproRuntimeServiceImpl.java:270)
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObject.start(DeployableObject.java:182)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.getApplicationDeployableObjectPart(RequestManager.
java:399)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:317)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:143)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
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:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
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:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare
application ''sap.com/tcsldwd~main'' for startup. Reason=
Clusterwide exception: Failed to start application ''sap.com/tcsldwd~main'': The referenced application ''sap.com/
tcsldwd~businesssystem'' can''t be started. Check the causing exception for details. Hint: Is the referenced
application deployed correctly on the server?
at com.sap.engine.services.webdynpro.WebDynproContainer.prepareStart(WebDynproContainer.java:1490)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal
(ApplicationTransaction.java:365)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.
java:132)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.
java:250)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.
java:4504)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationLocalAndWait
(DeployCommunicatorImpl.java:609)
at com.sap.engine.services.webdynpro.WebDynproContainer.startExternal(WebDynproContainer.java:646)
at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl$ApplicationStarter.run
(WebDynproRuntimeServiceImpl.java:460)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
http://
Edited by: Soumen Chattopadhyay on Aug 2, 2009 10:49 AM

Dear Rishi,
Thanks for your reply...Here are the answers to your query....Any help?
Query:
"As you said that you dint configure the SLD but the link was working fine before.ou would have given the detailsduring the time of installation."
Ans: As I remember I didn't ....But cant say surely...Yes I remember I executed 2/3 times RZ70 but there was some issue regarding the transfer of data thru RFC SLD_UC ...saying program no resistered etc...
Query:
After the application of the patch is the Url comming up did you check that server node is up.
Ans: Server node is up and running, able to login and work thru SAPGUI and also the urls for java instances e.g, http://server:port/nwa,http://server:port/useradmin,http://server:port/irj are working...ie. I mean able to browse ar see some content inside. but http://server:port/sld gave the error I posted earlier in this message.
Query:
Plese let me know that have you configured the Local SLD of Central SLD.
Did you addd the Bi system as technical system in the SLD.
Ans: Nope..Anything came is came by default.

Itunes 10 errors during installation with ipodservice error message

I have been trying to get itunes 10 installed for weeks. The upgrade would not work normally, so I removed itunes/quicktime/safari and decided try installing fresh.
I still get a error during the installation process saying that ipodservice.exe cannot execute instruction at 0x7c91b21a referenced at 0x0000000010. memory could not be 'written'
does anyone know how to fix this?

i'm getting a similar message. running Windows XP with Symantec AV

The Building Installer with Robohelp

I am using RoboHelp for HTML version 8
So, the build engineers and others are wondering if there is not some way to cut down on the number of files or reduce the compiled help to a single file. Apparently, with chm files they just had to account for a single file. But they regard the current process as quite complicated, since they have to put lines in the installer for each of the Robohelp files, of which there may be over a 100 depending on the number of topics, etc. Is there some way I can help them out?

Hi there
If you are generating WebHelp, you really do need to consider ALL the output files to be needed. But that's only if you really want your help to function under all circumstances.
Note that it should be possible for your developers to use wildcards to specify files. This means that instead of painfully adding entry after entry of this.htm and that.htm and theother.htm, they specify *.htm and all files in the folder would be included.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

Error during installation with xp sp3 ie8

message error is registation is not possible. i have administrative permission. i have correct with subinacl and reset_fp11.bat. but i have the same error.

Can you try installing from the stand alone installer? If it still fails, please let us know the exact error message.
http://helpx.adobe.com/flash-player/kb/installation-problems-flash-player-windows.html#mai n-pars_header

Build Installer with include file 2009

Does LV 2009 let you include files, i.e. *.doc or *.txt, in the installer build? I almost certain this was possible in LV 8.*. I don't see where I can add files outside of source code. I can only add directories...
Solved!
Go to Solution.

Oh gee thanks, stupid me. I'll try that....
Thanks

Error building procedure with CTX_DDL.SYNC_INDEX

I am getting the following error when I try to compile a procedure with a call to CTX_DDL.SYNC_INDEX:
PLS-00201: identifier 'CTX_DDL' must be declared
The public synonym for CTX_DDL exists and I can run ctx_ddl.sync_index from an anonymous block within SQL*PLUS. I also have other instances where the procedure will compile. The only real difference I can see between the 2 is the one where it will compile has the QUERY REWRITE privilege whereas the one where it will not compile does not. Is there some reason this privilege is required? Or is there something else I need to get this to compile?
Thank you for any information.

Hi,
to see if some records are waiting to be indexed you can query the view CTX_USER_PENDING:
select * from ctx_user_pending
where pnd_index_name = 'NOTES_DETAIL4_INDX';If this gives rows, then you need to Synchronize the index. If it give no rows, then all the records are indexed.
Herald ten Dam
http://htendam.wordpress.com

Error building installer with additional traditiona ni-daq

Similar Messages

Maybe you are looking for