Discovery Failed: VD-4564 error

Hi,
I have installed Oracle 9i Server in my machine. While installing, I checked the option to create a database using database configuration assistant, and to create a separate new repository for management server.
The installations were successful, and here are the database details:
=== Database created using database configuration assistant details ===
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=incdw2k062)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ORCL)))
=== Management Repository database details ===
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=incdw2k062)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=OEMREP.systechin.com))
The problem i am facing is described here:
I was able to view both the databases in the Oracle Enterprise Manager Console, Standalone.
However, I am not able to view the same in the Oracle Enterprise Manager Console, Administrator:SYSMAN, Management Server:incdw2k062.systechin.com
I tried to add the database through discover node option. But, it failed. I am getting the error: "Discovery Failed: VD-4564"
Please help me in resolving this issue. I am a newbie to ORACLE.
Thanks and Regards,
Deepak Natarajan.

Hi,
I couldn't get it. I am not pretty sure of how I configured it.
All I know is, it took my system name in the network as my host id. Once again I am giving the configuration details below:
=== Database created using database configuration assistant details ===
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=incdw2k062)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ORCL)))
=== Management Repository database details ===
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=incdw2k062)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=OEMREP.systechin.com))
Please tell me in steps to resolve the problem.
Regards,
Deepak Natarajan.

Similar Messages

"Discovery failed to null" error message when starting up Oracle Management

hey folks,
i am trying to get the Oracle Enterprise Manager to work and i get an error message. Here is what i've done so far.
1. Installed Oracle service. It is started (under Start>...>Services it says "Started").
2. Created a Listener for the Oracle service via Net8 Assistant. It is also started.
3. Created a Service Name in Net8 Assistant listening to the above mentioned Listener. When i tested it, it said "test successfull".
4. Created an ODBC Data Source via the ODBC Administrator.
5. Created a repository for the Oracle service using the Enterprise Configuration Assistant.
so now i am trying to start the Oracle Management Server and when i click on "start service", a command window opens and the following is on it:
"OEMCTRL for Windows NT: Version 2.1.0.1.0
Copyright (c) 1998, 1999 Oracle Corporation. All rights reserved.
Starting the Oracle Management Server...VXA-3008 : Starting OMS Services, Wait.
[xxxxxxxxxx.ou.edu-DiscoveryThread][2003-11-20:11:9:26:765] Discovery of xxxxxxxxxxxx.ou.edu failed due to null
The OMS is now started and ready."
where xxxxxxxxxxxxxxx is the name of my machine. The status for the OracleManagementServer under Services is "Started", but when i go to the Oracle Enterprise Manager console and try to log in, it just locks up.
any ideas?
Thanks.

if you are getting connection to the OEM you have to choose if you get connect in STANDALONE MODE or OMS MODE.
if you choose the first you have to get connection as a
user that has granted sysdba role
if you choose the second you have to get connection as a
user called sysman or another user stablished for the repository.
Joel P�rez

Discovery Failed: VNI-4026: Discovery failed: Error while transfer**URGENT*

Hi Fellows,
I had a server with one database only. It was discovered and running fine in OEM using Oracle Management Server. I created one more database in this server and created a service. Now I can see this database when I use OEM with stand alone option. But when I try OEM Oracle Management Server and I try to discover new database, it gives me the following error:
Discovery Failed: VNI-4026: Discovery failed: Error while transferring services.ora
I ping agent and it is okay. I checked the status of Listner which is fine too. If listner is not fine I should not be able to connect.
Note: the database which I already had on the server is working absolutely fine.
Any help will be highly appreciated.
Thanks
Ghulam Mustafa Butt

Hi,
I was out of office yesterday. Sorry for the link.
Here is the content of that link:
goal: How to confirm DNS hostname resolution
fact: Generic Platform
fix:
1. Find the hostname of the box:
     % hostname
2. Perform nslookup on hostname
     % nslookup <hostname>
     Type in the hostname exactly as it is displayed in step 1
     nslookup returns 4 or more lines of information in this format:
          Server: <hostname.domain of the dns server>
          Address: <ip address for the dns server>
          Name: <hostname.domain for this box>
          Address: <ip address for this box>
3. Perform nslookup on host IP address
     % nslookup <ip addr>
     Use the ip address found on the 4th line in step 2
     Exactly the same lines of info as in step 2 should be returned
4. Perform nslookup on host name of target system
     % nslookup <hostname>
     Exactly the same 4 lines should be returned as though nslookup were done on
the other box
5. Perform nslookup on IP address of target system
     % nslookup <ip addr>
     Exactly the same 4 lines should be returned as though nslookup were done on
the other box
NOTE ROLE:
The Network Administrator is responsible for adding servers to DNS

SCOM Linux discovery failed with "The user name or password is incorrect" error

Hi every one .
In our test environment when I want to discover a new linux computer system , discovery process fails with this error message :
Unexpected DiscoveryResult.ErrorData type. Please file bug report.
ErrorData: Microsoft.SystemCenter.CrossPlatform.ClientLibrary.Common.SDKAbstraction.TaskInvocationException
Task invocation failed with error code 1326. Error message was: The user name or password is incorrect.
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.SystemCenter.CrossPlatform.ClientActions.DefaultDiscovery.InvokeWorkflow(IManagedObject managementActionPoint, DiscoveryTargetEndpoint criteria, IInstallableAgents installableAgents)
But I m sure that this username and password is correct and I can logon to this computer with this credential.
how do I find root cause of this issue ?

I have been enabled logging before doscovery process .
in temp directory :
0: 02/10/15 20:03:22 : Enter SCXNameResolverProbe constructor
0: 02/10/15 20:03:22 : Leave SCXNameResolverProbe constructor
1: 02/10/15 20:03:22 : Enter SCXNameResolverProbe::DoInit
1: 02/10/15 20:03:22 : XML_INIT_CALL
1: 02/10/15 20:03:22 : Check WSAStartup
1: 02/10/15 20:03:22 : Exit SCXNameResolverProbe::DoInit
2: 02/10/15 20:03:22 : Enter SCXNameResolverProbe::DoProcess()
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess passed initial arguments checking
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess input: 192.168.7.62
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess - Input is an IP-address
3: 02/10/15 20:03:22 : Enter SCXNameResolverProbe::GetName(): 192.168.7.62
3: 02/10/15 20:03:22 : Resolve IPv4 address to host name
3: 02/10/15 20:03:22 : Leave SCXNameResolverProbe::GetName(): SUSE11
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns name: SUSE11
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns ip: 192.168.7.62
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns errorcode: 0
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns errortext:
2: 02/10/15 20:03:22 : SCXNameResolverProbe::DoProcess returns xml: <NetworkName>SUSE11</NetworkName><IPAddress>192.168.7.62</IPAddress><StatusCode>0</StatusCode><StatusMessage></StatusMessage>
2: 02/10/15 20:03:22 : Enter initDataHolder
2: 02/10/15 20:03:22 : Enter initDataType
2: 02/10/15 20:03:22 : initDataType initializing output datatype
2: 02/10/15 20:03:22 : Leave initDataType
2: 02/10/15 20:03:22 : Leave initDataHolder
2: 02/10/15 20:03:22 : Leave SCXNameResolverProbe::DoProcess
4: 02/10/15 20:03:22 : Enter SCXNameResolverProbe destructor
4: 02/10/15 20:03:22 : SCXNameResolverProbe destructor - FreeLibrary failed: 0
4: 02/10/15 20:03:22 : Leave SCXNameResolverProbe destructor
with debug viewer I have this message after discovery :
[7448] A management object with display name SUSE11 could not be found.

Untrusted Forest Discovery failed

I'm having a issue with remote untrusted forest. Forest Discovery fails, but I can publish site server information to this forest.
ERROR: [ForestDiscoveryAgent]: Failed to connect to forest domain.com. This can be because of disjoint DNS namespaces, network connectivity or server availibility issue. Error Information The specified forest does not exist or cannot be contacted.
Entering function ReportForestConnectionFailureStatusMessage()
Calling ReportStatus, keys= SMS_AD_FOREST_DISCOVERY_MANAGER, -2147474744, 2
I have configured conditional forwarders between forests and name resolution works. There shouldn't be any firewall issues either and I tested SRV records via nslookup with this method
Type nslookup, and then press ENTER.
Type set type=all, and then press ENTER.
Type _ldap._tcp.dc._msdcs.<var>Domain_Name</var>, where <var>Domain_Name</var> is the name of your domain, and then press ENTER.
Nslookup lists correct domain controllers from remote forest.
Any ideas what could be causing this? I think it's AD related problem.

LDAP://DCNAME.domain.com/OU=Computers,DC=domain,DC=com
I tested this last week and this works. Now I can discover computer objects from untrusted forest. There must be something wrong with the ad/dns infrastructure becasue
normally you dont need to specify domain controller directly because it should find it with srvlookup.

Exadata Discovery - Failed to launch process: Algorithm negotiation fail

Trying to discover an Exadata box. We’ve installed the latest EM (BP1) and deployed the agents successfully to the compute nodes. When we come to use the discovery wizard, it fails on the monitoring credential page. We input the cell root passwords and click test connection which fails with the error messages:
sxa1cel01 - Failed to launch process: Algorithm negotiation fail
sxa1cel02 - Failed to launch process: Algorithm negotiation fail
sxa1cel03 - Failed to launch process: Algorithm negotiation fail
Not much info available about this. Looking at the agent log just shows the same error message coupled with a Java error and not much else. Googling around, it seems it might be something to do with JSch.
Any help or pointers would be greatly appreciated.

The root cause of this issue are additional security changes made in the latest Exadata release. Enterprise Manager Cloud Control 12c will be moving to this standard as well in an upcoming patchset.
Workaround to the problem:
The current workaround for existing installations is to add the ciphers listed in the step below back to the sshd_config files on all cells and compute nodes if the customer is running Exadata Storage Server version 11.2.3.1.0. The work around steps for this situation are listed below. For each storage cell and compute node, edit the /etc/ssh/sshd_config file as listed below:
1) ssh to the cell node as root
2) cd /etc/ssh/
3) back up sshd_config
4) add aes128-cbc,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc,blowfish-cbc to the Cipher line in sshd_config
5) Restart the ssh daemon (as the root user):
# service sshd restart
Edited by: user484103 on Apr 23, 2012 11:45 PM
Edited by: user484103 on Apr 23, 2012 11:50 PM

Device discovery failed in ANM

Hi,
I've got the following error message when I want to import a 6506 in 12.2(33)SXI2 with an ACE module.
I've tried in ANM 2.2 and 3.0 = same problem.
Can someone help me ?
Device discovery failed: Exception occured for model:VlanModel
Exception occured for model:InterfaceModel
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort.
Thanks,
Greg.

Hi Greg,
The error message you are seeing is likely triggered by some un-expected configuration on the cat6k.
It is likely your cat6k configuration has an interface defined as a switchport which has a subinterface defined on it.
This is usually not allowed on most sup versions that we have seen and hence is not modeled/ cannot be discovered in ANM.
We have bug id CSCtd94658 opened for this issue.
You could try to have your customer remove the subinterface indicated above and then try the import into ANM.
Also, they could maybe add back that interface if really required after the initial import.
Since Cat6k configs are not auto-sync'ed in ANM, they will be okay until they do a manual sync.
This workaround in also documented in the release notes of CSCtd94658.
Thanks
Sujatha
========

Active Directory service discovery failed

Hi forum user,
I have integrated my SGD with AD.
I saw the following error in jserver log file:
# more jserver2698_error.log
2007/07/24 15:25:22.626 (pid 2698) server/ldap/error #1185261922626
Sun Secure Global Desktop Software (4.31) ERROR:
Active Directory service discovery failed: Failed to find any valid Site objects.
Looking up Global Catalog DNS name: gc.tcp.telbru.com.bn. - HIT
Looking for GC on server: Active Directory:ts1.telbru.com.bn:/172.25.11.96:3268:Up - HIT
Checking for CN=Configuration: DC=telbru,DC=com,DC=bn - MISS
Checking for CN=Configuration: CN=Configuration,DC=telbru,DC=com,DC=bn - HIT
Looking up domain root context: DC=telbru,DC=com,DC=bn - HIT
Looking up site context: CN=Sites,CN=Configuration
Searching for sites: (&(objectClass=site)(siteObjectBL=*)) - HIT
Looking up addresses for peer DNS: portal.telbru.com.bn - HIT
Failed to discover Active Directory Site, Domain and server data.
This might mean LDAP users cannot log in.
Make sure the DNS server contains the Active Directory service
records for the forest. Make sure a Global Catalog server is available.
Why the error occurred ?
What is the resolution to this error ?
Appreciate any help. Thanks.

This error message is telling you that SGD failed to find any site objects in your AD tree. This should not stop users from logging in, it will just mean that SGD will not be able to work out which AD site is local to the SGD server.
If you are not using sites in your AD setup, then you do not need to worry about this.
Hope this helps,
DD

VIN 2 - Access failed. Unknown error...

Hi all,
I made the deployment of VIN 2.0. Apparently all is well. I entered the license and enabled the discovery. After the first moments when VIN shows the message "First Discovery pending ..." then I get out of all VMs, including the same VIN, the message "Access failed. Unknown error while retrieving data from Infrastructure Navigator".
Any suggestions? I tried to restart it several times.
Matrix

Hi Matrix,
There could be many reasons for this.
Please check for the following:
1. Does the VIN VA have access to the VC?
2. Is the above VC configured to use non standard ports for HTTP/HTTPS communication (not 80/443)?
3. Does the VIN VA have access to the ESX hosts that host those VMs?
Have you contacted your sales engineer / PSO regarding this issue?
Is there an SR open on this?
It will be very helpful to get a support package from the VA to analyze what happened, as this is a very general error.
Regards,
Boris

Target Auto Discovery fails

Hi,
I have EMC12 installed on WinServer2008 R2 SP1. Cygwin ssh deamon started and configured. Agent is running on local account (LA) with administrative privileges and additional setting configured according to docs. OMS is running on local system account.
When I start target auto discovery I get following error:
Status          Failed
     Exit Code          4
     Step ID          1022
     Started          01-Jun-2012 11:06:54 GMT+02:00
     Ended          01-Jun-2012 11:06:54 GMT+02:00
     Step Elapsed Time          0 seconds
     Management Service          OracleEM.Myhost:4889_Management_Service
Output Log
Host discovery job failed. Exception: Unable to create directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst
Even I had created such directory manually it stills shows the same error. I have also verified that LA account has full control to C:/MiddlewareHome/agent/agent_inst directory.
Cygwin doesnt have sudo option installed (not needed according to docs on Windows, although job credentials require sudo delegation - what for?).
Any ideas?
Thanks,
JP

Logs show following:
[2012-06-04T15:40:46.267+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.Util.class] [tid: [ACTIVE].ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: SYSMAN] [ecid: d70f67283c055146:772f8397:137b7b1143f:-8000-0000000000000252,0] [APP: emgc] oracle.sysman.core.discovery.uimodel: MissingResourceException: nlsid=OSB_DISCOVERY_TEXT, rb=oracle.sysman.db.rsc.ob
[2012-06-04T15:41:27.281+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand] [tid: RemoteJobWorker 1931] [userId: SYSMAN] [ecid: 0000JUrgIZnFKA05zzK6yW1FnBYO000001,1:26629:3] [APP: emgc] Exception occurred while creating discovery directory under:C:/MiddlewareHome/agent/agent_inst:java.security.PrivilegedActionException: oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: Cannot run program "mkdir": CreateProcess error=2, The system cannot find the file specified
[2012-06-04T15:41:27.281+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand] [tid: RemoteJobWorker 1931] [userId: SYSMAN] [ecid: 0000JUrgIZnFKA05zzK6yW1FnBYO000001,1:26629:3] [APP: emgc] Unable to create discovery directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst
[2012-06-04T15:41:27.312+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand] [tid: RemoteJobWorker 1931] [userId: SYSMAN] [ecid: 0000JUrgIZnFKA05zzK6yW1FnBYO000001,1:26629:3] [APP: emgc] executeNMapCommand: Exception: Unable to create directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst[[
java.lang.Exception: Unable to create directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst
     at oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand.executeNMapCommand(RunNMapCommand.java:633)
     at oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand.executeCommand(RunNMapCommand.java:337)
     at oracle.sysman.emdrep.jobs.CommandStepExecutor.execute(CommandStepExecutor.java:153)
     at oracle.sysman.emWebservices.inbound.jobs.worker.ConsoleJobStepExecutor.execute(ConsoleJobStepExecutor.java:316)
     at oracle.sysman.emWebservices.inbound.jobs.worker.ConsoleJobStepExecutor.executeStep(ConsoleJobStepExecutor.java:182)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:369)
     at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:201)
     at oracle.j2ee.ws.server.jaxws.JAXWSRuntimeDelegate.processMessage(JAXWSRuntimeDelegate.java:479)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
     at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:1089)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.security.Security.runAs(Security.java:61)
     at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
     at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
     at oracle.security.jps.internal.jaas.AbstractSubjectSecurity.executeAs(AbstractSubjectSecurity.java:138)
     at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:304)
     at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1096)
     at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:581)
     at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:232)
     at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:192)
     at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:484)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:315)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:555)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.caching.filter.AdfFacesCachingFilter.doFilter(AdfFacesCachingFilter.java:129)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
That seems strange as mkdir is WinSrvr system command.
JP

IDS discovery fails

I have a small number of IDS's that fail discovery.
The fail description is:
"Fail to discover policy for signatureDefinition component. Detail: Error encountered while generating
policy IpsSignaturefor instance sig0."
I have scaled down the polices to discover from the default ones of Inventory/ Platform settings/ and IPS
and still no luck. Devices have also been rebooted multiple times with no luck. Any quick fix or is a reimage in
order?
Thanks...

I think you are hitting a bug
may be
CSCtg23806
CSM discovery fail when Signature ID 50000 or later is modified
Please open a case with cisco TAC to get the right support.
Sachin

Sign in failed - Unknown server error (-2) when trying to sign in to new playbook

I get the message "Sign in failed - Unknown server error (-2)" when I try to login to the Blackberry ID page of a new playbook during initial setup. This prevents me from continuing and using my device. A similar error message appears when I tap "Forgot password?" which is An unknown error has occured. Please try again (-2)
I have tried what others have done when they have unknown error (-6) which is turn off playbook and plug into desktop manager then update to reflash, but I continue to get the same error.
I know my BB ID username and password are correct because I can login to the web with them. Not sure what to do next.

Just to test the simple things first, did you try to sign in using another credential?
If only yours fails, then is a RIM issue, otherwise is indeed your Playbook failure.
--- Catalonia, next state in Europe ----
Use the "solved" or "Like" icons if my answer helped you.
BES10 administrator for several customers.
"SMPTE Calculator" timecode APP developer for BB10

The system failed to merge, error code : General Access denied

The system failed to merge, error code : General Access denied. Could anyone help me on this

Hi,
It could be several things, I think it could be a good start with the following page:
https://blogs.technet.com/b/chrad/archive/2009/10/02/differencing-disks-merging-80070005-error-just-one-persons-lesson-learned.aspx
If that doesn't help you could check out the following technet page to see if it is a permission problem. (it is not exactly the same problem but one of our customers once had the same problem and we solved it with the follwing KB:http://support.microsoft.com/kb/2249906/en-us
Hope this helps you out.

Executable build failing with no error message with smtp email VIs

I have a VI which I want to build into a .exe which will be used as an HMI for a real-time system. I am using the SMTP VIs to text/email me various notifications about the system state. The main VI works fine if run but will not build into an .exe. The error message comes back blank so no help there (LabView 2010). If I just simply disable the portion of the code in the HMI.VI which contains the email VI code, the application builds. I searched for anwers and was unable to resolve the problem. Any ideas? Do I need to include anything in the build that is specific to the LabView SMTP VIs? I'm new to building .exe's so I appologize for any rookie mistakes I may have made.
Thanks.

mikeporter wrote:
You said you searched for answers (on the forum?).
Yes.
What did you find?
I found a bunch of topics on email send errors after the application was built but nothing related to .exe building failures (related to the SMTP/email VIs). I also found topics dicussing the bug that fails to report an (any) error during the .exe build (for 2011). The solution was to install the service pack. if that's my problem then I will have to go through the motions to get that done (corporate computers / lack of persmissons and such).
What have you tried? This question has been answered many, many, many times.
I tried what I stated in the OP. If I disable the portion of the code which contains the email SMTP VIs, the application builds, otherwise, the build fails and no error code or description is given.
PS: probably has nothing to do with the SMTP drivers, per se.
If the answer has been given many, many times, then I appologize for not being able to find it before posting. Trust me, the last thing I want to is waste my time fishing for answers on the forum, especially when I get a response from forum members who would rather point out that my mis-identified problem has been answered many, many times, rather then just helping me out.

Payables Open Interface Pgm fails without any error(Very urgent)

All,
I'm into an integration project where in I'm pushing Invoice doc from a third party appln to Oracle apps (11.5.10.2) thru payables open interface. The integration is smooth till today. We pushed a record today, but the concurrent neither picks up the data but failed with 'completed error' status. When I delete the same record from the interface, the concurrent runs fine. So we are sure there is some issue with the data in my record. Since concurrent is failed without any reason, from where I can get the log to know what is the actual problem with that record? Pls help me with your inputs.
Thanks,
Sen

Sen,
To enable trace, please refer to this document (skip the part about generating TKPROF, just check the concurrent request output file if more details about the error are logged after enabling trace and setting the profile option).
Note: 453527.1 - How To Trace a Concurrent Request And Generate TKPROF File
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=453527.1
The database log file can be usually found under $ORACLE_HOME/admin/<SID>_<hostname>/bdump directory (or from SQL*Plus, issue "show parameter background_dump_dest").
Regards,
Hussein

Discovery Failed: VD-4564 error

Similar Messages

Maybe you are looking for