Trying to Deploy Novel Client 2 ADM

I am trying to use the Novell Client 2 ADM to limit what my users can do via the Novell Client (we are a public school district.) Specifically, I am trying to disable the Novell Utilities, the Browse To, and the Properties dialogs. When I used the ADM in my Group Policy, and applied it to my users, nothing changed. I then tried to create a bundle to push out the registry edits that would make the changes, I was able to see that the changes took effect, but they took effect on all users who logged in to the computer instead of just to the specific users I wanted.
I know that this is probably an easy fix, but I have been struggling over this for 2 weeks now, and I am no closer to a solution than I was before.
Thank you for any assistance you can provide me.

Billupp,
> I was able to see
> that the changes took effect, but they took effect on all users who
> logged in to the computer instead of just to the specific users I
> wanted.
They are global yes, so you must run the edit for every user that logs
in, always.
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)
Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

Similar Messages

Import Novell Client ADM to Zen 10

What is the secret to creating a Policy in Zenworks 10 that controls the Novell client? I do not see any place that I can import an ADM file and then create a policy using it.
Another question is will the client ADM file 4.9 work for the Vista 64 Novell client? If not, is or will there be one soon for Vista?
Thanks

There is demand...I hope at least. We are in the process of rolling our Vista 64 Business because of an CAD application, Revit, that just needs the extra resources. We held off as long as we could but were forced to move on. We have the Novell client loaded and all works fine, but we would just like to turn off some of the Novell options the client installs. We also had to upgrade to Zen 10 for the Vista support. If you do an update to the adm file, please let me know!
thanks.
Originally Posted by spond
Txrjohnson,
What Andrew said :)
> Another question is will the client ADM file 4.9 work for the Vista 64
> Novell client? If not, is or will there be one soon for Vista?
>
You could ask the author... oh wait, that's me - I hadn't planned to,
but I could try to find time if there was demand...
Shaun Pond

Deploy novell client

For a customer i've set up ZLM, OES and SLED.
- what is the easiest way to distribute the novell client?
currently i have created a rpm bundle, containing all rpm's on the novell client cd.

lowalcohol,
... but to be honest... I do not want the client, I want to use centrally managed login scripts, to map samba/ncp shares...
that is one of the things the Novell client allows you to do. You define the login scripts once in edirectory and the Novell clients, independent where they are, use them when they login. Okay it depends if you have logical structures in edirectory and different sites, then you might need them twice or more times, but it is a perfect solution you can manage from a central point.
So to your question ...
When I check as a sample the SLED 11 Novell client, I see that the installation media is already usable as a installation source.
So one option might be to use a remote execute policy to add it as a zypp source temporarily via "rug sa -t zypp <network path to the client> NWCL" on each client and trigger the installation. The problem is that it is not only a instalaltion of rpm packages, there is a yast module that does all the configuration for the novell client afterwards. I don't know if there is a console command that does all the same. In other cases the configu files must be collected that are touched by yast and then the remote execute policy should do the same.
A second option would be to put all rpms into a bundle and then use the post installation script to make all the additional system configurations that were done via yast.
So far this seem to be the two options you can choose from ...
What do you think ?
Rainer

Trying to deploy SCCM Client upgrade...

A few days ago I upgraded our SCCM 2007 R2 Site Server with SP2. I did this in preparation for Windows 7 support and deployment. Anyhow, I decided to release the client upgrade via software distribution using the same package that I include with my image deployment (data source is \\server\sms_001\client )
Yesterday, I created an advertisement to distribute the SCCM client upgrade to my entire network but today System Center Console is reporting that out of 1148, 996 have not yet started, 0 succeeded, and 149 have failed. We're a school so most of our computers are off. The issue is that of the computers that are on 149 have failed with 0 reporting a success....or so they say.
I checked a few of my clients and the ccmsetup.log indicates that installation has in fact succeeded. However, what the "status of a specific advertisement" report is telling me is that the client failed with the "last status message name" column indicating "Program Failed (unexpected restart)". It shows the same thing for all clients that have reported a failure.
The software package program function is configured to run the following and I'm not using any client options: "CCMSETUP.EXE /noservice SMSSITECODE=AUTO"
Any ideas why the client appears to have been upgraded but reporting a failure?
Below is the execmgr.log:
Policy arrived for parent package 00100006 program Advanced Client Silent Upgrade execmgr 12/22/2009 8:09:49 PM 3784 (0x0EC8)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramOfferReceivedEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223010949.649000+000";
MachineName = "ADMIN-OFF-TSEC";
ProcessID = 1976;
SiteCode = "001";
ThreadID = 3784;
execmgr 12/22/2009 8:09:49 PM 3784 (0x0EC8)
Requesting content from CAS for package 00100006 version 4 execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Successfully created a content request handle {36479D3C-24C9-4844-BED1-2AB2B0BDD0F1} for the package 00100006 version 4 execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Program Advanced Client Silent Upgrade change to state STATE_ADVANCED_DOWNLOAD content in progress execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from NotExist to AdvancedDownload execmgr 12/22/2009 8:09:50 PM 3144 (0x0C48)
Mandatory execution requested for program Advanced Client Silent Upgrade and advertisement 00120025 execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Creating mandatory request for advert 00120025, program Advanced Client Silent Upgrade, package 00100006 execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistWaitingContentEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223010950.555000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
PackageVersion = "4";
ProcessID = 1976;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 1348;
execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Successfully raised SoftDistWaitingContentEvent event for program Advanced Client Silent Upgrade execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from WaitingDependency to WaitingContent execmgr 12/22/2009 8:09:50 PM 1348 (0x0544)
Content is available for program Advanced Client Silent Upgrade. execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
CExecutionRequest::Overriding Service Windows as per policy. execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from WaitingContent to NotifyExecution execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Notify user mandatory program Advanced Client Silent Upgrade is about to run execmgr 12/22/2009 8:10:24 PM 2680 (0x0A78)
Execution Manager timer has been fired. execmgr 12/22/2009 8:15:25 PM 1736 (0x06C8)
Executing program CCMSETUP.EXE /noservice SMSSITECODE=AUTO in Admin context execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Execution Request for package 00100006 program Advanced Client Silent Upgrade state change from Running to NotifyExecution execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Checking content location C:\WINDOWS\system32\CCM\Cache\00100006.4.System for use execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Successfully selected content location C:\WINDOWS\system32\CCM\Cache\00100006.4.System execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Executing program as a script execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ccmsetup.exe" /noservice SMSSITECODE=AUTO execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Command line = "C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ccmsetup.exe" /noservice SMSSITECODE=AUTO, Working Directory = C:\WINDOWS\system32\CCM\Cache\00100006.4.System\ execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Created Process for the passed command line execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\00100006.4.System\\ccmsetup.exe\" /noservice SMSSITECODE=AUTO";
DateTime = "20091223011525.457000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
ProcessID = 1976;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 3500;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\00100006.4.System\\";
execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Raised Program Started Event for Ad:00120025, Package:00100006, Program: Advanced Client Silent Upgrade execmgr 12/22/2009 8:15:25 PM 3500 (0x0DAC)
Request in running or report status found for program Advanced Client Silent Upgrade package 00100006 execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Service stopped while program Advanced Client Silent Upgrade is running execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
OpenProcess failed for process 1396, error 80070057 execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Can not continue monitoring the program after service restart because the process exited. Assume failed execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Looking for MIF file to get program status execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramUnexpectedRebootEvent
AdvertisementId = "00120025";
ClientID = "GUID:4AC789F0-1D9C-49A0-BFD2-23D950A6307A";
DateTime = "20091223011911.783000+000";
MachineName = "ADMIN-OFF-TSEC";
PackageName = "00100006";
ProcessID = 3636;
ProgramName = "Advanced Client Silent Upgrade";
SiteCode = "001";
ThreadID = 1700;
execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)
Raised Program Unexpected Reboot Event for Ad:00120025, Package:00100006, Program: Advanced Client Silent Upgrade execmgr 12/22/2009 8:19:11 PM 1700 (0x06A4)

This KB article covers the upgrade of the client via hotfixes:
http://support.microsoft.com/kb/2477182
An important thing to note is that the Program needs the following set:
After Running: Program Restarts Computer; this is needed to ensure that any status MIF files are collected after a restart of the client service (ccmexec.exe). No actual restart of the computer should occur.
This enables the SCCM client to detect that it re-started and to process the MIF files for status messages.
Installing the following updates one at a time normally is sucessful:
KB2761938
KB2516517
KB2815223
Other updates such as KB2276865 fail with the Unexpected Reboot Event error (possibly because the MIF is not written correctly) but it has been superseeded by KB2815223 wich is OK.

Installing Novell Client fails due to 'untrusted signer'

I am trying to update Novell Client on our Windows 7 workstations, using a Zenworks bundle. This method has worked in the past: copy the installation files to c:\temp\zeninstall\clnt2sp3ir5 (including appropriately modified NovellClientProperties.txt and install.ini) and then just launch "setup.exe /ncpf" as secure system user.
This time I noticed that the new client was only partially installed. When viewing Novell Client properties it shows the new version, however, some files are definitely from the previous client version (for example C:\Windows\System32\lgnwnt32.dll).
I dug up c:\windows\inf\setupapi.dev.log and it seems that installation was aborted due to "unsigned driver package":
Code:
sto: Validating driver package files against catalog 'netnvcli.cat'.
!!! sto: Driver package signer is unknown. Assuming untrusted signer. Error = 0x800F0242
!!! ndv: Driver package failed signature validation. Error = 0xE0000242
sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0xe0000242)} 12:37:47.960
!!! sto: Driver package failed signature verification. Error = 0xE0000242
!!! sto: Failed to import driver package into Driver Store. Error = 0xE0000242
sto: {Stage Driver Package: exit(0xe0000242)} 12:37:48.225
!!! sto: Failed to stage driver package to Driver Store. Error = 0xE0000242, Time = 6521 ms
sto: {Import Driver Package: exit(0xe0000242)} 12:37:49.973
inf: Opened INF: 'c:\temp\zeninstall\novell_client\c2sp3ir5\netnvcli.inf' ([strings])
! inf: Add to Driver Store unsuccessful
! inf: Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
!!! inf: returning failure to SetupCopyOEMInf
<<< Section end 2014/02/11 12:37:51.439
<<< [Exit status: FAILURE(0xe0000242)]
If I run the installation manually, I am prompted at one point about unsigned driver and whether I want to install it. If I answer "yes", the installation is successful.
Looking at Windows' certificate store on our computers, I see under "Trusted Publishers" a certificate issued to Novell, Inc by "Verisign Class 3 Code Signing 2009-2 CA", but that certificate expired on 27.04.2013.
How can I obtain and deploy the certificate that would allow the silent installation of Novell Client 2 SP3 IR5 to proceed? Or am I going about this in an entirely wrong way?

Originally Posted by vatson
I am trying to update Novell Client on our Windows 7 workstations, using a Zenworks bundle. This method has worked in the past: copy the installation files to c:\temp\zeninstall\clnt2sp3ir5 (including appropriately modified NovellClientProperties.txt and install.ini) and then just launch "setup.exe /ncpf" as secure system user.
This time I noticed that the new client was only partially installed. When viewing Novell Client properties it shows the new version, however, some files are definitely from the previous client version (for example C:\Windows\System32\lgnwnt32.dll).
I dug up c:\windows\inf\setupapi.dev.log and it seems that installation was aborted due to "unsigned driver package":
Code:
sto: Validating driver package files against catalog 'netnvcli.cat'.
!!! sto: Driver package signer is unknown. Assuming untrusted signer. Error = 0x800F0242
!!! ndv: Driver package failed signature validation. Error = 0xE0000242
sto: {DRIVERSTORE_IMPORT_NOTIFY_VALIDATE exit(0xe0000242)} 12:37:47.960
!!! sto: Driver package failed signature verification. Error = 0xE0000242
!!! sto: Failed to import driver package into Driver Store. Error = 0xE0000242
sto: {Stage Driver Package: exit(0xe0000242)} 12:37:48.225
!!! sto: Failed to stage driver package to Driver Store. Error = 0xE0000242, Time = 6521 ms
sto: {Import Driver Package: exit(0xe0000242)} 12:37:49.973
inf: Opened INF: 'c:\temp\zeninstall\novell_client\c2sp3ir5\netnvcli.inf' ([strings])
! inf: Add to Driver Store unsuccessful
! inf: Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
!!! inf: returning failure to SetupCopyOEMInf
<<< Section end 2014/02/11 12:37:51.439
<<< [Exit status: FAILURE(0xe0000242)]
If I run the installation manually, I am prompted at one point about unsigned driver and whether I want to install it. If I answer "yes", the installation is successful.
Looking at Windows' certificate store on our computers, I see under "Trusted Publishers" a certificate issued to Novell, Inc by "Verisign Class 3 Code Signing 2009-2 CA", but that certificate expired on 27.04.2013.
How can I obtain and deploy the certificate that would allow the silent installation of Novell Client 2 SP3 IR5 to proceed? Or am I going about this in an entirely wrong way?
You need to install the newest client (that have a never certificate) on a device and then export it from that machine, after that you import it on the devices you want to install the client before running setup.exe.
Thomas

Novell Client 2 upgrade fails to install NICI (error 1603)

I have configured the automatic update agent to specifically use Administrator Privileges according to the documentation: http://www.novell.com/documentation/...ient_admin.pdf
When I run the update from "Novell Services" in system tray as a normal user the update completes with errors: fails to install NICI (error 1603).
When I do the exact same thing as an admin, everything works fine.
I'm am trying to update Novell Client 2 SP 1 (IR7) to Novell Client 2 SP 2 (IR2) on all of our workstations.
And I am seeing the exact same error when trying to upgrade:
Novell Client 2 SP 1 (IR7) to Novell Client 2 SP 2
Novell Client 2 SP 1 (IR7) to Novell Client 2 SP 2 (IR1)
What is going on here, is the update agent broken or am I doing something wrong?
I don't want all of my users getting errors when their Novell Client gets updated.

Originally Posted by jimbjorklund
I think I'm getting closer to the actual issue, after enabling Novell Client Debugging by setting this registry value:
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Authentication\ NCCredProvider]
"Debug"=dword:00000003
This error is found in "C:\ProgramData\Novell\Client\Log\NICIInst64.l og": Error 2103.Could not resolve path for shell folder 26
I think this has something to do with the MSI-setup (NICI_wx64.msi) not being able to find certain keys in the registry for some reason
Recently we had problem with an MSI-based Java-installation running with admin-privileges where it would fail if "Folder Redirection" was enabled. We had set My Documents to point to H:\ which was mapped via Novell as the home folder.
the registry settings for that are found under: [HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Explorer\User Shell Folders]. This however is NOT the problem here so the root cause for the error is still unclear to me.
Indeed, but remember we are troubleshooting the client here- it may be possible that there was some corruption in the first failed update. So thus removing any components and with a clean install of the Novell client, to try the update process again to ascertain were exactly the process may have failed by examining any logs and/or dumps.
Leroy Joseph
Visual Click Software
eDirectory Management and Reporting | DSRAZOR for eDirectory

Novell Client 2/Win 7 ADM files

Does anyone have a custom GPO ADM created for Novell Client 2?
Shaun, I heard you might have created it?

Originally Posted by Michael_Fleming
Does anyone have a custom GPO ADM created for Novell Client 2?
Shaun, I heard you might have created it?
Two recent/new resources are available for the Novell Client 2 SP3 for Windows:
Cool Solutions AppNote: Novell Client 2 SP3 for Windows: Registry Settings
Novell Client 2 SP3 for Windows: Registry Settings | Novell User Communities
Cool Solutions Tool: Group Policy Administrative Template for Novell Client 2 SP3 for Windows
Group Policy Administrative Template for Novell Client 2 SP3 for Windows | Novell User Communities

Firewall rule for Novell Client

My company recently purchased McAfee Desktop Firewall and I'm trying to
configure the rules prior to deployment but I'm having trouble getting
the Novell Client to cooperate. I've tried having the firewall "learn"
the client, addresses, ports, protocols, etc. but have had no luck.
My company is running a mix of Win2k/XP computers as well as Win95/98
computers so any assistance in creating a firewall rule to allow the
clients to log in is greatly apprecaited.
Thanks!
Ash

Excellent, thanks!!
> For NetWare connectivity over IP, you need ports TCP,UDP 524 and 427
> which are NCP over IP and SLP.
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)

Hi Experts, when i am trying to deploy the application error is coming

Hi Experts,
when i am trying to deploy the webdynpro java pplication error is coming.but before up to 2 days every thing is working fine.
from two days onwards i cant run any webdynpro applications even which are sap provided applications also.and also can not come properly http://hostname:portno/sld page. i can not moving to more to do anything.
every browser saying javavoid(0); and java applet can not be run like.
only the opera browser shoeing the error toatlly . here i paste the error . please give reply why i can not doing any thing more. But my server and every thing is showing up and good.
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
This page was created by SAP NetWeaver. All rights reserved.
Web Dynpro client:
Nokia Series 80 Client
Web Dynpro client capabilities:
User agent: Opera/9.80 (Windows NT 5.2; U; en) Presto/2.2.15 Version/10.00, client type: op6, client type profile: op6, ActiveX: disabled, Cookies: enabled, Frames: enabled, Java applets: disabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Accessibility mode: false
Web Dynpro runtime:
Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-05:15:08:24[UTC], changelist=413534, host=pwdfm101), build date: Thu Aug 13 23:44:29 GMT+05:30 2009
Web Dynpro code generators of DC sap.com/tcsldwd~main:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcsldwd~landscape:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwddispwda: No information available!
Web Dynpro code generators of DC sap.com/tcsldwd~businesssystem:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcsldwd~technicalsystem:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwdcorecomp: No information available!
Web Dynpro code generators of DC sap.com/tcsldwd~softwarecatalog:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcsldwd~namereservation:
SapDictionaryGenerationCore: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:07:52[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:10:47[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:02[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:32:04[UTC], changelist=413534, host=pwdfm101)
SapGenerationFrameworkCore: 7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:54:14[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:20[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:05:18[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-20:04:55:10[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:14:30[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-20:05:08:00[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
J2EE Engine:
7.00 patchlevel
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_12-b03, vendor: Sun Microsystems Inc.
O

HI surya,
Restart the SDM and try again...
regards,
viswa

I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but th

I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

If you are searching the registry, check for the "Senforce" string. It should be at HKLM\Software\Senforce
Try running the install program for the ZSC with the following command line:
setup.exe /V"STUNINSTALL=1"
If you've specified an uninstall password, try this one instead:
setup.exe /V"STUNINSTALL=1 STUIP=password"" (please note the double quote at the end)
Let me know if that helped you.
Daniel
>>>
From: Andy_DeWees<[email protected] du>
To:novell.support.zenworks.endpoint-security-management
Date: 2/5/2009 12:52 PM
Subject: I have installed the agent 10 or 15 times and one installation hasfailed, no error appeared during the installation but I am havinginconsistent issues with my ethernet card not working here and there. Werebooted and can log into Novell client but the login prompt did not appearfor ESM client or the icon was not in the systray. Everything seems towork, besides at times (a couple times today) it terminates his ethernetcard/connection. I would re-image his computer but he has severalapplications and
I have installed the agent 10 or 15 times and one installation has failed, no error appeared during the installation but I am having inconsistent issues with my ethernet card not working here and there. We rebooted and can log into Novell client but the login prompt did not appear for ESM client or the icon was not in the systray. Everything seems to work, besides at times (a couple times today) it terminates his ethernet card/connection. I would re-image his computer but he has several applications and it would take several hours, so I am hoping someone has an idea to fix this issue. So I was trying to figure out why he did not get the prompt to login and why it's not in the systray and it appears to not have completed the install? I checked the add/remove programs, its not listed within their, I also checked the registry and found nothing for endpoint within their, but the files are within c:\program files\novell\zenworks endpoint security.
I have also tried uninstalling it but that fails due to it "not being installed", and it will not reinstall over itself either.
I did notice that stuninstdrv.exe is running in task manager. Any help would be great...
Windows xp sp3
ESM 3.5.154
Thanks,
Andy

Error while trying to deploy a cube

I am getting an error message while trying to deploy a cube. OWB Client version is 10.2.0.1.31 and the repository version is 10.2.0.1.0
Below is the piece of code that generates the error:
BEGIN
CWM2_OLAP_CUBE.ADD_DIMENSION_TO_CUBE('EXPENSE_WH', 'REL_EXPENSE', 'EXPENSE_WH', 'REL_CATEGORY');
END;
Error report:
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "OLAPSYS.CWM2_OLAP_UTILITY", line 1660
ORA-01403: no data found
ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 33
ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 55
ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 386
ORA-06512: at line 2
I would appreciate any help.

Is the dependent dimension deployed to the catalog? Generally the no data found error indicates some dependent object is missing; either an implementing table or a dependent dimension.
Cheers
David

Error while deploying Java Client Proxy

Hi Experts,
I developed a java client proxy.Since i do not have access to visual administrator, i uploaded the ear file to a folder in the XI box and asked the basis folks to deploy it.
On trying to deploy it on to the server they got the following error.
Details:
========
1) Error loading archive
    /usr/sap/XS1/put/R3Ear.ear
    (server side name is: /usr/sap/XS1/put/R3Ear.ear)
    com.sap.sdm.util.sduread.IllFormattedSduFileException: Error during attribute reading: received exception: invalid stored block lengths
What could be the reason for the error?

Hi
recreate your ear file and try to redeploy it.
it could be a zipping problem
Regards
Vishnu

Trying to Deploy from JDeveloper to Oracale AS -- Urgent

I am trying to deploy a Web Application to a remote Oracle AS instead of the Standalone Embedded OC4J server. I get the following message when I attempt
---- Deployment started. ---- Mar 12, 2012 1:54:36 PM
Target platform is Oracle Application Server 10g 10.1.2 (Windows) (bantest).
Wrote WAR file to C:\jdev\jdev\mywork\NJTransit\NJTransit\deploy\webapp.war
Wrote EAR file to C:\jdev\jdev\mywork\NJTransit\NJTransit\deploy\webapp.ear
Invoking DCM servlet client...
C:\j2sdk1.4.2_14\bin\javaw.exe -Djava.protocol.handler.pkgs=HTTPClient -jar C:\jdev\jdev\lib\oc4j_remote_deploy.jar http://207.200.160.20:18100/Oc4jDcmServletAPI/ ias_admin *** redeploy D:\oracle\FRHome_1 C:\jdev\jdev\mywork\NJTransit\NJTransit\deploy\webapp.ear webapp*
Initializing log
Servlet interface for OC4J DCM commands
Command timeout defined at 600 seconds
Executing DCM command...
Executing command redeploy D:\oracle\FRHome_1 C:\jdev\jdev\mywork\NJTransit\NJTransit\deploy\webapp.ear webapp UNDEFINED
Command = REDEPLOY
Reading application's ear file
Ear file was successfully read
Opening connection to Oc4jDcmServlet
Setting userName to ias_admin
Sending command to DCM servlet
HTTP response code = 200, HTTP response msg = OK
Command was successfully sent to Oc4jDcmServlet
Receiving session id from servlet to check command status
Session id = 2e195050061f346870503dc4b73ab6e4bb736e798c496ab3b54227294f8ae9ea
Please, wait for command to finish...
Checking command status...
Setting userName to ias_admin
Setting Cookie to JSESSIONID=2e195050061f346870503dc4b73ab6e4bb736e798c496ab3b54227294f8ae9ea
Checking command status
HTTP response code = 200, HTTP response msg = OK
Command has finished
Receiving command exit value
Receiving command output
***** No output was received from command*
Closing connection to Oc4jDcmServlet
*#### DCM command did not complete successfully (-8)*
*#### HTTP return code was -8*
Exit status of DCM servlet client: -8
Elapsed time for deployment: 11 seconds
*#### Deployment incomplete. #### Mar 12, 2012 1:54:48 PM*
can anyone offer help

Thanks what they suggested seemed to work

Windows 7 with MDT - Novell Client / Zen Agent?

Been creating my Windows 7 reference image using Microsoft Deployment Toolkit (MDT - pretty cool). I'm wondering if any of you do the same, and if you do, do you include the Novell Client in the image? what about the zenworks agent? If so, what techniques are you using to install.. etc.
Thanks!

Originally Posted by joebrug
Been creating my Windows 7 reference image using Microsoft Deployment Toolkit (MDT - pretty cool). I'm wondering if any of you do the same, and if you do, do you include the Novell Client in the image? what about the zenworks agent? If so, what techniques are you using to install.. etc.
Thanks!
You can use this during your sysprep process that way it does not matter if it is installed or not.
zac fsg -d
:: THIS WILL ALLOW A NEW GUID TO BE CREATED IN ZEN AFTER REIMAGING
del "C:\Program Files (x86)\Novell\ZENworks\conf\deviceguid"
del "C:\Program Files (x86)\Novell\ZENworks\conf\devicedata"
del "C:\Program Files (x86)\Novell\ZENworks\conf\*.sav"
del "C:\Program Files (x86)\Novell\ZENworks\conf\Guid.txt"

Error when trying to deploy ADF application in Java Cloud Service - SaaS Extension

Hello guys,
I'm trying to deploy a simple ADF application in "Oracle Java Cloud Service - SaaS Extension" and i'm still having the error below
The job turns to Failed at "Deploy Application" step:
Did someone already got this error ?
Thanks at advance
Sid
2014-12-10 11:06:20 PST: Starting action "Deploy Application"
2014-12-10 11:06:20 PST: Deploy Application started
2014-12-10 11:06:28 PST: weblogic.application.ModuleException: weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1531)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:488)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:671)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:44)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:573)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:327)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.security.AccessControlException: access denied ("java.net.NetPermission" "specifyStreamHandler")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:372)
at java.security.AccessController.checkPermission(AccessController.java:559)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.net.URL.checkSpecifyHandler(URL.java:649)
at java.net.URL.<init>(URL.java:373)
at weblogic.application.io.MergedDescriptorFinder.getSource(MergedDescriptorFinder.java:46)
at weblogic.application.io.DescriptorFinder.getSource(DescriptorFinder.java:44)
at weblogic.utils.classloaders.MultiClassFinder.getSource(MultiClassFinder.java:67)
at weblogic.application.utils.CompositeWebAppFinder.getSource(CompositeWebAppFinder.java:71)
at weblogic.servlet.internal.War$ResourceFinder.getSource(War.java:1213)
at weblogic.servlet.internal.War$ResourceFinder.getSource(War.java:1203)
at weblogic.servlet.internal.War.getResourceAsSource(War.java:512)
at weblogic.servlet.internal.WebAppServletContext.getResourceAsSource(WebAppServletContext.java:3436)
at weblogic.servlet.internal.WebAppServletContext.getResourceAsSource(WebAppServletContext.java:3427)
at weblogic.servlet.internal.WebAppServletContext.getResourceAsStream(WebAppServletContext.java:872)
at com.sun.faces.config.ConfigureListener$WebXmlProcessor.scanForFacesServlet(ConfigureListener.java:805)
at com.sun.faces.config.ConfigureListener$WebXmlProcessor.<init>(ConfigureListener.java:768)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:178)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1871)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3173)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1529)
2014-12-10 11:06:28 PST: WL action state: failed
2014-12-10 11:06:28 PST: Action FAILED with WL action state: failed
2014-12-10 11:06:28 PST: Check the server log of your Java cloud service for more info about the failure.
2014-12-10 11:06:28 PST: Application deployment failed.
2014-12-10 11:06:28 PST: "Deploy Application" complete: status FAILED

The Application does nothing, it's just a simple page (the button does nothing too) the aim is to deploy a jsf page with ADF forms.
The deployment log is on the first message.
I'm using Jdeveloper and i note the Jdev inserts some servlets into the web.xml file ! is it possible that the probleme is related to this ? (below the web.xml file)
Sid
<?xml version = '1.0' encoding = 'windows-1252'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
         version="2.5">
<servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>
<servlet>
    <servlet-name>resources</servlet-name>
    <servlet-class>org.apache.myfaces.trinidad.webapp.ResourceServlet</servlet-class>
</servlet>
<servlet>
    <servlet-name>BIGRAPHSERVLET</servlet-name>
    <servlet-class>oracle.adf.view.faces.bi.webapp.GraphServlet</servlet-class>
</servlet>
<servlet>
    <servlet-name>BIGAUGESERVLET</servlet-name>
    <servlet-class>oracle.adf.view.faces.bi.webapp.GaugeServlet</servlet-class>
</servlet>
<servlet>
    <servlet-name>MapProxyServlet</servlet-name>
    <servlet-class>oracle.adf.view.faces.bi.webapp.MapProxyServlet</servlet-class>
</servlet>
<servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>resources</servlet-name>
    <url-pattern>/adf/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>resources</servlet-name>
    <url-pattern>/afr/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>BIGRAPHSERVLET</servlet-name>
    <url-pattern>/servlet/GraphServlet/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>BIGAUGESERVLET</servlet-name>
    <url-pattern>/servlet/GaugeServlet/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>MapProxyServlet</servlet-name>
    <url-pattern>/servlet/mapproxy/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
    <servlet-name>resources</servlet-name>
    <url-pattern>/bi/*</url-pattern>
</servlet-mapping>
<filter>
    <filter-name>trinidad</filter-name>
    <filter-class>org.apache.myfaces.trinidad.webapp.TrinidadFilter</filter-class>
</filter>
<filter>
    <filter-name>ServletADFFilter</filter-name>
    <filter-class>oracle.adf.share.http.ServletADFFilter</filter-class>
</filter>
<filter-mapping>
    <filter-name>trinidad</filter-name>
    <servlet-name>Faces Servlet</servlet-name>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>ERROR</dispatcher>
</filter-mapping>
<filter-mapping>
    <filter-name>ServletADFFilter</filter-name>
    <servlet-name>Faces Servlet</servlet-name>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>REQUEST</dispatcher>
</filter-mapping>
<context-param>
    <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
    <param-value>client</param-value>
</context-param>
<context-param>
    <param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
    <param-value>false</param-value>
</context-param>
<context-param>
    <description>If this parameter is true, there will be an automatic check of the modification date of your JSPs, and saved state will be discarded when JSP's change. It will also automatically check if your skinning css files have changed without you having to restart the server. This makes development easier, but adds overhead. For this reason this parameter should be set to false when your application is deployed.</description>
    <param-name>org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION</param-name>
    <param-value>false</param-value>
</context-param>
<context-param>
    <description>Whether the 'Generated by...' comment at the bottom of ADF Faces HTML pages should contain version number information.</description>
    <param-name>oracle.adf.view.rich.versionString.HIDDEN</param-name>
    <param-value>true</param-value>
</context-param>
<context-param>
    <description>Security precaution to prevent clickjacking: bust frames if the ancestor window domain(protocol, host, and port) and the frame domain are different. Another options for this parameter are always and never.</description>
    <param-name>org.apache.myfaces.trinidad.security.FRAME_BUSTING</param-name>
    <param-value>differentOrigin</param-value>
</context-param>
<context-param>
    <param-name>javax.faces.VALIDATE_EMPTY_FIELDS</param-name>
    <param-value>true</param-value>
</context-param>
<context-param>
    <param-name>oracle.adf.view.rich.geometry.DEFAULT_DIMENSIONS</param-name>
    <param-value>auto</param-value>
</context-param>
<context-param>
    <param-name>oracle.adf.view.rich.SYNCROWS</param-name>
    <param-value>enable</param-value>
</context-param>
<context-param>
    <param-name>javax.faces.FACELETS_SKIP_COMMENTS</param-name>
    <param-value>true</param-value>
</context-param>
<context-param>
    <param-name>javax.faces.FACELETS_DECORATORS</param-name>
    <param-value>oracle.adfinternal.view.faces.facelets.rich.AdfTagDecorator</param-value>
</context-param>
<context-param>
    <param-name>javax.faces.FACELETS_RESOURCE_RESOLVER</param-name>
    <param-value>oracle.adfinternal.view.faces.facelets.rich.AdfFaceletsResourceResolver</param-value>
</context-param>
<context-param>
    <param-name>javax.faces.FACELETS_VIEW_MAPPINGS</param-name>
    <param-value>*.jsf;*.xhtml</param-value>
</context-param>
<mime-mapping>
    <extension>swf</extension>
    <mime-type>application/x-shockwave-flash</mime-type>
</mime-mapping>
<mime-mapping>
    <extension>amf</extension>
    <mime-type>application/x-amf</mime-type>
</mime-mapping>
<listener>
    <listener-class>oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack</listener-class>
</listener>
<login-config />
</web-app>

Trying to Deploy Novel Client 2 ADM

Similar Messages

Maybe you are looking for