"An occurred while creating a domain log handler"

I'm trying to deploy a war file to Weblogic 9.2, but after restarting the server, I get the following error and the Administration Console no longer works:
####<Apr 18, 2008 1:59:25 PM EDT> <Info> <Diagnostics> <ivory13> <examplesServer> <[ACTIVE] ExecuteThread: '0' for queue:
'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1208541565719>
<BEA-320000>
<The Diagnostics subsystem is initializing on Server examplesServer.>
####<Apr 18, 2008 1:59:26 PM EDT> <Error> <Diagnostics> <ivory13> <examplesServer> <[ACTIVE] ExecuteThread:
'0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1208541566780>
<BEA-320134>
<An occurred while creating a domain log handler: weblogic.management.logging.DomainLogHandlerException:
The domain logger does is only available on an Admin Server..
weblogic.management.logging.DomainLogHandlerException: The domain logger does is only available on an Admin Server.
     at weblogic.management.logging.DomainLogHandlerImpl.getInstance(DomainLogHandlerImpl.java:72)
     at weblogic.diagnostics.lifecycle.LoggingLifecycleImpl.initialize(LoggingLifecycleImpl.java:71)
     at weblogic.diagnostics.lifecycle.DiagnosticSystemService.start(DiagnosticSystemService.java:123)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException:
Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused: connect]
     at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
     at javax.naming.InitialContext.bind(InitialContext.java:363)
     at org.objectweb.carol.jndi.spi.AbsContext.bind(AbsContext.java:157)
     at org.objectweb.carol.jndi.spi.AbsContext.bind(AbsContext.java:167)
     at javax.naming.InitialContext.bind(InitialContext.java:359)
     at org.objectweb.carol.jndi.spi.MultiContext.bind(MultiContext.java:141)
     at javax.naming.InitialContext.bind(InitialContext.java:359)
     at weblogic.management.logging.DomainLogHandlerImpl.<init>(DomainLogHandlerImpl.java:102)
     at weblogic.management.logging.DomainLogHandlerImpl.getInstance(DomainLogHandlerImpl.java:70)
     at weblogic.diagnostics.lifecycle.LoggingLifecycleImpl.initialize(LoggingLifecycleImpl.java:71)
     at weblogic.diagnostics.lifecycle.DiagnosticSystemService.start(DiagnosticSystemService.java:123)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
     at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
     at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
     at javax.naming.InitialContext.bind(InitialContext.java:363)
     at org.objectweb.carol.jndi.spi.AbsContext.bind(AbsContext.java:157)
     at org.objectweb.carol.jndi.spi.AbsContext.bind(AbsContext.java:167)
     at javax.naming.InitialContext.bind(InitialContext.java:359)
     at org.objectweb.carol.jndi.spi.MultiContext.bind(MultiContext.java:141)
     at javax.naming.InitialContext.bind(InitialContext.java:359)
     at weblogic.management.logging.DomainLogHandlerImpl.<init>(DomainLogHandlerImpl.java:102)
     at weblogic.management.logging.DomainLogHandlerImpl.getInstance(DomainLogHandlerImpl.java:70)
     at weblogic.diagnostics.lifecycle.LoggingLifecycleImpl.initialize(LoggingLifecycleImpl.java:71)
     at weblogic.diagnostics.lifecycle.DiagnosticSystemService.start(DiagnosticSystemService.java:123)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:519)
     at java.net.Socket.connect(Socket.java:469)
     at java.net.Socket.<init>(Socket.java:366)
     at java.net.Socket.<init>(Socket.java:179)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
     at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
     at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
     at javax.naming.InitialContext.bind(InitialContext.java:363)
     at org.objectweb.carol.jndi.spi.AbsContext.bind(AbsContext.java:157)
     at org.objectweb.carol.jndi.spi.AbsContext.bind(AbsContext.java:167)
     at javax.naming.InitialContext.bind(InitialContext.java:359)
     at org.objectweb.carol.jndi.spi.MultiContext.bind(MultiContext.java:141)
     at javax.naming.InitialContext.bind(InitialContext.java:359)
     at weblogic.management.logging.DomainLogHandlerImpl.<init>(DomainLogHandlerImpl.java:102)
     at weblogic.management.logging.DomainLogHandlerImpl.getInstance(DomainLogHandlerImpl.java:70)
     at weblogic.diagnostics.lifecycle.LoggingLifecycleImpl.initialize(LoggingLifecycleImpl.java:71)
     at weblogic.diagnostics.lifecycle.DiagnosticSystemService.start(DiagnosticSystemService.java:123)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
####<Apr 18, 2008 1:59:26 PM EDT> <Warning> <Log Management> <ivory13> <examplesServer> <[ACTIVE] ExecuteThread:
'0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1208541566796>
<BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server.
The Admin server may not be running. Message broadcasts to the admin server will be disabled.> Any help would be greatly appreciated.

Anyone?

Similar Messages

A fatal error occurred while creating an SSL client credential. The internal error state is 10011.

Need help. I have my pilot lync 2013 pool up (in coexistence with 2010 production environment) and can log into Lync 2013 environment with a lync 2010 client but am not able to with a lync 2013 client. It just prompts for password but will not
take it. I'm sseeing this on my front end server multiple times:
A fatal error occurred while creating an SSL client credential. The internal error state is 10011.
Came across this http://www.logicspot.net/index.php?id=50 and tried disabling TLS 1.2, which I did and verified but yet the issue still exists.
All my certs are good coming from internal CA. My signin logs show below but keep in mind, this works just fine if using a 2010 lync client to my lync 2013 servers. Issue only occurs when trying to connect using a lync 2013 client.
1 Login: FAIL (hr = 0x1)
this request needs authentication, trying webticket from: https://domain.com/WebTicket/WebTicketService.svc
1.1 Get-NewWebTicket: FAIL (hr = 0x1)
CLogonCredentialManager::QueryForSpecificCreds() Credential user 0x069B64A0 id=15 querying for specific credentials, credSuccess=2, targetName=Microsoft_OC1:[email protected]:specific:LAD:1
1.1.1 ExecuteWithMetadataInternal: FAIL (hr = 0x3d0000)
Executing wws method with windows auth auth, asyncContext=0A4FC348,
context: WebRequest context@ :173931816
MethodType:4
ExecutionComplete? :1
Callback@ :0A5A1864
AsyncHResult:80f10041
TargetUri:https://domain.com/WebTicket/WebTicketService.svc
OperationName:http://tempuri.org/:IWebTicketService
Error:
There was an error communicating with the endpoint at 'https://domain.com/WebTicket/WebTicketService.svc'.
The server returned HTTP status code '401 (0x191)' with text 'Unauthorized'.
The requested resource requires user authentication.
1.1.2 ExecuteWithWindowsOrNoAuthInternal: PASS
1.1.3 ExecuteWithWindowsOrNoAuthInternal: FAIL (hr = 0x3d0000)
Executing wws method with windows auth auth, asyncContext=0A4FC348,
context: WebRequest context@ :173931816
MethodType:4
ExecutionComplete? :1
Callback@ :0A5A1864
AsyncHResult:80f10041
TargetUri:https://domain.com/WebTicket/WebTicketService.svc
OperationName:http://tempuri.org/:IWebTicketService
Error:
There was an error communicating with the endpoint at 'https://domain.com/WebTicket/WebTicketService.svc'.
The server returned HTTP status code '401 (0x191)' with text 'Unauthorized'.
The requested resource requires user authentication.
1.1.4 ExecuteWithWindowsOrNoAuthInternal: FAIL (hr = 0x3d0000)
Discovery task(0A4FF830) sent to URL http://domain.com completed with hr=0x80f10045
1.1.5 ExecuteWithWindowsOrNoAuthInternal: FAIL (hr = 0x3d0000)
Executing wws method with windows auth auth, asyncContext=0A4FC348,
context: WebRequest context@ :173931816
MethodType:4
ExecutionComplete? :1
Callback@ :0A5A1864
AsyncHResult:80f10041
TargetUri:https://domain.com/WebTicket/WebTicketService.svc
OperationName:http://tempuri.org/:IWebTicketService
Error:
There was an error communicating with the endpoint at 'https://domain.com/WebTicket/WebTicketService.svc'.
The server returned HTTP status code '401 (0x191)' with text 'Unauthorized'.
The requested resource requires user authentication.
1.1.6 ExecuteWithWindowsOrNoAuthInternal: FAIL (hr = 0x3d0000)
CLogonCredentialManager::QueryForSpecificCreds() Credential user 0x069B64A0 id=15 querying for specific credentials, credSuccess=2, targetName=Microsoft_OC1:[email protected]:specific:LAD:1
Rich

Hi,
Please check the server role and Web Services for Internet Information Services (IIS) are set correctly.
For the detailed IIS configuration, please check:
http://technet.microsoft.com/en-us/library/gg412871.aspx
As Lync client 2013 attempt to query in order to perform autodiscover of the Lync registration server. First
lyncdiscoverinternal.<sipdomain> Host (A) record and then
lyncdiscover.<sipdomain> Host (A) record. If neither of these records are resolvable then the legacy DNS SRV and A record fall-back process is used. So make sure you have add the two A record in DNS server.
More details:
http://blog.schertz.name/2012/12/lync-2013-client-autodiscover/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Time Machine: Error occurred while creating the backup folder

Mac Mini 2.53 GHz, 8 GB DDR3
OS X 10.8.4
Time Capsule 1 TB, connected via ethernet
Airport Utility 6.3.1 (631.4)
"Time Machine Error. Unable to complete backup. An error occurred while creating the backup folder."
I believe my Time Capsule is out of space and isn't removing older backups to create space for itself. Time Machine preferences says only 98 MB available on the 1 TB volume. I have used Pondini's superb troubleshooting page with the following results:
A1: Time Machine Buddy Widget. Partial log from backup attempt:
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Failed to create progress log file at path:/Volumes/Time Machine Backups/Backups.backupdb/Macmini-34159E18D208 (4)/2013-04-04-223516.inProgress/.Backup.400571203.603238.log.
Event store UUIDs don't match for volume: Macintosh HD
Error: (Error Domain=NSCocoaErrorDomain Code=640 "You can’t save the file “598C5622-100E-456A-89AF-DEBC87A6CA89” because the volume “Time Machine Backups” is out of space." UserInfo=0x7f88a330cef0 {NSFilePath=/Volumes/Time Machine Backups/Backups.backupdb/Macmini-34159E18D208 (4)/2013-04-04-223516.inProgress/598C5622-100E-456A-89AF-DEBC87A6CA89, NSUnderlyingError=0x7f88a33056a0 "The operation couldn’t be completed. No space left on device"}) Creating directory 598C5622-100E-456A-89AF-DEBC87A6CA89
Failed to make snapshot.
Backup failed with error: 2
Ejected Time Machine disk image: /Volumes/Data/Macmini-34159E18D208 (4).sparsebundle
Ejected Time Machine network volume.
A4: Full reset of Time Machine. Done, did not change error from occurring on next backup attempt.
A5b: Verify backups on Time Machine. Done, successful (no problems).
C10: Also attempted switching out ethernet cable and tried different ports on the Time Capsule, to no effect.
I have no exceptions listed in Time Machine preferences (under Options) and the box for "notify when deleting old backups" is UNchecked.
Any suggestions would be most appreciated!!

grifftastic wrote:
I believe my Time Capsule is out of space and isn't removing older backups to create space for itself. Time Machine preferences says only 98 MB available on the 1 TB volume.
"You can’t save the file “598C5622-100E-456A-89AF-DEBC87A6CA89” because the volume “Time Machine Backups” is out of space."
Yes, it's so full it can't get started -- not even far enough to start deleting old backups.
If you have other data there (not usually a good idea), move some of it elsewhere temporarily, and try again.
If not, manually delete a couple of old backups, and "compact" the sparse bundle, per Time Machine - Frequently Asked Question #12.

OBIEE install fails while creating a domain

Hi,
I am trying to install OBIEE 11.1.1.3 on linux 64. I selected the Enterprise install option. The installer gives error while creating a domain during the configuration process.
BI Configuration Log
Config Action BI Configuration started
Creating Domain
Error
null
Step Creating Domain failed
Configuration Action 'Creating Domain' has failed. Please check logs for details.
The log file is as follows..
[2010-09-29T14:45:33.319-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Assigning Port: 7002 to: DOMAIN_PORT
[2010-09-29T14:45:33.422-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Assigning Port: 9556 to: NODE_MANAGER_PORT
[2010-09-29T14:45:33.422-05:00] [as] [NOTIFICATION] [] [oracle.as.install.engine] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Setting valueOf(DOMAIN_PORT) to:7002. Value obtained from:USER
[2010-09-29T14:45:33.422-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Domain port set to: 7002
[2010-09-29T14:45:33.422-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Nodemanager port set to: 9556
[2010-09-29T14:45:33.446-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Starting initial node manager configuration...
[2010-09-29T14:45:33.446-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Found listening port from node manager properties: null
[2010-09-29T14:45:33.446-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Unable to reuse node manager - port is null
[2010-09-29T14:45:33.446-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] No reusable node manager found.
[2010-09-29T14:45:33.446-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Completed initial node manager configuration.
[2010-09-29T14:45:33.448-05:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 38] [ecid: 0000IhV1njD27Ud5Tf0Fyc1CcstI00000S,0] Assigning Port: 9556 to: NODE_MANAGER_PORT
Can anybody tell what may be wrong. I verified that the port 9556 was free.

Hello George,
Did you figured out how to solve this problem?. I have been trying to install OBIEE 11g all morning and that's the exact error that I'm getting from the log file:
Assigning Port: 7001 to: DOMAIN_PORT
[2010-09-29T11:16:14.842-06:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] Assigning Port: 9556 to: NODE_MANAGER_PORT
[2010-09-29T11:16:14.842-06:00] [as] [NOTIFICATION] [] [oracle.as.install.engine] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] Setting valueOf(DOMAIN_PORT) to:7001. Value obtained from:USER
[2010-09-29T11:16:14.842-06:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] Domain port set to: 7001
[2010-09-29T11:16:14.842-06:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] Nodemanager port set to: 9556
[2010-09-29T11:16:14.914-06:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] Starting initial node manager configuration...
[2010-09-29T11:16:14.915-06:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] Found listening port from node manager properties: null
[2010-09-29T11:16:14.915-06:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] Unable to reuse node manager - port is null
[2010-09-29T11:16:14.915-06:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] No reusable node manager found.
[2010-09-29T11:16:14.915-06:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] Completed initial node manager configuration.
[2010-09-29T11:16:14.915-06:00] [as] [NOTIFICATION] [] [oracle.as.install.bi] [tid: 26] [ecid: 0000IhUVavHFW7WFLzmJOA1Ccq_j00000H,0] Assigning Port: 9556 to: NODE_MANAGER_PORT
Please help on this issue.
Thanks.
Pablo.

"An unexpected error occurred while creating a custom installer."

All;
I—and I've seen several others in older posts—have been reported received the error "An unexpected error occurred while creating a custom installer" while attampting to build a customer ARD client installer. My guess is that this is do to a issue related to 10.8.X (10.8.4, in my case) based console Mac but I cannot confirm this. I have verified that there are no outstanding OS, client or application updates or hot fixes, as well.
Has anyone built an successful installer from Mountain Lion-installed Mac? Is there any know workarounds?
Thanks in advance, for any help.

Have the exact same problem.
iMac running 10.8.4
Got through the steps of creating a custom client installer.
if I choose not to customize and just save an installer I don't get the error but it creates a file of Zero bytes in size.
If I chose to configure, when I try to save I get:
An unexpected error occurred while creating a custom installer. Please try again....
Console log reports:
9/1/13 12:32:29.603 AM Remote Desktop[1306]: open on /private/tmp/RemoteDesktopClientInstaller_HEATyAJ5CR/extracted/RemoteDesktopCli ent.pkg/Scripts/RemoteDesktopClient.pkg: No such file or directory
I have tried to save this in several location, with no effect on the error or the information logged, with the exception of the name of the temp directory that DOES contains the file (zero bytes):
RemoteDesktopClient.pkg
Need help with this someone...!
APPLE...I JUST purchase this Applciation for $80.....it just flat out does not work....

An exception occured while creating a query in EntityManager

I was directed to create a new topic rather than resurrect a long dead thread. I appreciate the correction in this.
Persistence, Entity Manager, NetBeans 6.7.1, GlassFish v2.1, Database
I am getting the following Stack Trace:
[#|2009-12-08T16:22:06.171-0500|SEVERE|sun-appserver2.1|javax.faces|_ThreadID=18;_ThreadName=httpSSLWorkerThread-8080-1;_RequestID=390db479-49c0-47e5-bcdc-e5e07f871644;|javax.faces.event.AbortProcessingException: java.lang.IllegalArgumentException: An exception occured while creating a query in EntityManager
javax.faces.event.AbortProcessingException: java.lang.IllegalArgumentException: An exception occured while creating a query in EntityManager
     at javax.faces.event.MethodExpressionValueChangeListener.processValueChange(MethodExpressionValueChangeListener.java:82)
     at javax.faces.event.ValueChangeEvent.processListener(ValueChangeEvent.java:123)
     at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:746)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:416)
     at sun.reflect.GeneratedMethodAccessor290.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.faces.extensions.avatar.components.PartialTraversalViewRootHelper.broadcastEvents(PartialTraversalViewRootHelper.java:500)
     at com.sun.faces.extensions.avatar.components.PartialTraversalViewRootHelper.processValidators(PartialTraversalViewRootHelper.java:267)
     at com.sun.faces.extensions.avatar.components.PartialTraversalViewRootImpl.processValidators(PartialTraversalViewRootImpl.java:152)
     at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:100)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
     at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
     at com.sun.faces.extensions.avatar.lifecycle.PartialTraversalLifecycle.execute(PartialTraversalLifecycle.java:94)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
     at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:427)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:315)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:287)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:218)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
     at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
     at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:222)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1096)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:166)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:648)
     at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:593)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:587)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1096)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:288)
     at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:647)
     at com.sun.enterprise.web.connector.grizzly.comet.CometEngine.executeServlet(CometEngine.java:609)
     at com.sun.enterprise.web.connector.grizzly.comet.CometEngine.handle(CometEngine.java:356)
     at com.sun.enterprise.web.connector.grizzly.comet.CometAsyncFilter.doFilter(CometAsyncFilter.java:84)
     at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
     at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
     at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
     at com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
Caused by: java.lang.IllegalArgumentException: An exception occured while creating a query in EntityManager
     at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerImpl.createQuery(EntityManagerImpl.java:209)
     at com.davisco.web.jpa.controllers.EmpdataJpaController.findEmpdataEntities(EmpdataJpaController.java:165)
     at com.davisco.web.jpa.controllers.EmpdataJpaJpaController.findEmpdataJpaEntities(EmpdataJpaJpaController.java:155)
     at com.davisco.web.jpa.controllers.EmpdataJpaJpaController.findEmpdataJpaEmpnoEntities(EmpdataJpaJpaController.java:214)
     at com.davisco.web.jsf.EmpdataController.getEmployeesByEmpno(EmpdataController.java:471)
     at com.davisco.web.jsf.EmpdataController.addEmployeeEmpnos(EmpdataController.java:439)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     ... 48 more
Caused by: Exception [TOPLINK-8034] (Oracle TopLink Essentials - 2.1 (Build b60e-fcs (12/23/2008))): oracle.toplink.essentials.exceptions.EJBQLException
Exception Description: Error compiling the query [select object(o) from Empdata as o]. Unknown abstract schema type [Empdata].
     at oracle.toplink.essentials.exceptions.EJBQLException.unknownAbstractSchemaType(EJBQLException.java:494)
     at oracle.toplink.essentials.internal.parsing.ParseTreeContext.classForSchemaName(ParseTreeContext.java:163)
     at oracle.toplink.essentials.internal.parsing.SelectNode.getClassOfFirstVariable(SelectNode.java:366)
     at oracle.toplink.essentials.internal.parsing.SelectNode.getReferenceClass(SelectNode.java:354)
     ... 65 more
It appears that problem
|javax.faces.event.AbortProcessingException: java.lang.IllegalArgumentException: An exception occured while creating a query in EntityManager
is actually caused by
Exception Description: Error compiling the query [select object(o) from Empdata as o]. Unknown abstract schema type [Empdata].
The Query is a very basic query.
     private EntityManagerFactory emf = javax.persistence.Persistence.createEntityManagerFactory("PersistPU");
     public EntityManager getEntityManager() {
          return emf.createEntityManager();
     private List<Empdata> findEmpdataEntities(boolean all, int maxResults, int firstResult) {
          EntityManager em = getEntityManager();
          try {
               Query q = em.createQuery("select object(o) from Empdata as o"); // Problem line
               if (!all) {
                    q.setMaxResults(maxResults);
                    q.setFirstResult(firstResult);
               return q.getResultList();
          } finally {
               em.close();
I have reviewed my Configuration Files and Source Packages without solution.
Where do I need to look or what do I need to do to determine the error?

After reading similar discussion in the OTN Discussion page ( [Thread: Unknown abstract schema type |http://forums.oracle.com/forums/thread.jspa?threadID=602826] ) I reviewed how I was creating my EntityManagerFactory. I realize also more information is required for a more complete understanding of the circumstances.
I originally created a project in Netbeans using the wizard to create a JSF Project from Entity Classes. Through trial and error I produced from the resulting JSF Web pages a maintenance project for a given table in the database. I was then given the task to split the table and build a new project utilizing the existing entity classes in a production project.
After the table was split and the new entity classes created I then entered the task of starting a new project using the entity classes in the production project. To do this I used the Netbeans wizard to create the JpaControllers in the production project. I copied as much code as I could from the working table maintenance project I had just completed. I have now started to connect the two projects. I have included the production project with the entities as a library project. I created the persistence.xml file in the new project with the same persistence unit name as the production project. I have included the Toplink Extensions as a library in the new project (even though the production project has the entity classes). From what I have been able to glean I am thinking my EntityManagerFactory declaration may be misdirecting the finding of the Empdata schema in my new project. Here is how I declared my EntityManager in the example given:
private EntityManagerFactory emf = javax.persistence.Persistence.createEntityManagerFactory("DvPersistPU");
     public EntityManager getEntityManager() {
          return emf.createEntityManager();
Here is the wizard generated method which fails with a NullPointerException in the return statement:
     @PersistenceUnit(unitName = "PersistPU")
     private EntityManagerFactory emf = null;
     public EntityManager getEntityManager() {
          return emf.createEntityManager();
Hopefully this will better help someone to direct me to determining the cause of my error or the error of my ways.
NullPointerException stacktrace just mentioned:
EmpdataController: getEmployeesByEmpno [0]
AbortProcessingException thrown when processing event of type 'javax.faces.event.ValueChangeEvent' during phase 'PROCESS_VALIDATIONS 3' for component with ID or Client ID of 'srchEmp'
javax.faces.event.AbortProcessingException: java.lang.NullPointerException
javax.faces.event.AbortProcessingException: java.lang.NullPointerException
at javax.faces.event.MethodExpressionValueChangeListener.processValueChange(MethodExpressionValueChangeListener.java:82)
at javax.faces.event.ValueChangeEvent.processListener(ValueChangeEvent.java:123)
at javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:746)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:416)
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 com.sun.faces.extensions.avatar.components.PartialTraversalViewRootHelper.broadcastEvents(PartialTraversalViewRootHelper.java:500)
at com.sun.faces.extensions.avatar.components.PartialTraversalViewRootHelper.processValidators(PartialTraversalViewRootHelper.java:267)
at com.sun.faces.extensions.avatar.components.PartialTraversalViewRootImpl.processValidators(PartialTraversalViewRootImpl.java:152)
at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
at com.sun.faces.extensions.avatar.lifecycle.PartialTraversalLifecycle.execute(PartialTraversalLifecycle.java:94)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
Caused by: java.lang.NullPointerException
at com.company.web.jpa.controllers.EmpdataJpaController.getEntityManager(EmpdataJpaController.java:71)
at com.company.web.jpa.controllers.EmpdataJpaController.findEmpdataEntities(EmpdataJpaController.java:163)
at com.company.web.jpa.controllers.EmpdataJpaController.findEmpdataEntities(EmpdataJpaController.java:155)
at com.company.web.jpa.controllers.EmpdataJpaController.findEmpdataEmpnoEntities(EmpdataJpaController.java:214)
at com.company.web.jsf.EmpdataController.getEmployeesByEmpno(EmpdataController.java:471)
at com.company.web.jsf.EmpdataController.addEmployeeEmpnos(EmpdataController.java:439)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
... 49 more
Would someone please help me know where to look next or point me in the direction to find the cause of the error(s)?
Thank you.

Time Machine warning: An error occured while creating a backup folder. What to do???

Time Machine warning: An error occured while creating a backup folder. What to do???

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

An error occured while creating the original attribute for message no26 296

Hi All,
I am new to DMS , we are trying to store PM documents on content server , created a storage category and while assigning files to storage category then on saving the document i get the below error :
An error occured while creating the original attribute for
Message no. 26 296
Diagnosis
An error occured while creating an original in the Knowledge Provider.
System Response
The original could not be created.
Procedure
Contact the systems administrator and check the log file (transaction Evaluate application log, object SDOK).
Please let me know what configs i am missing ...
Thanks in advance
regrds
pushpa

Hi Pushpa,
Which enhancement package are you on currently? This is observed in cases where originals in DIR's are invisible and sometimes error message 26296 occurs in transaction CV01n. Hence,please check your entries in the table SDOKPROP to avoid such a problem in your system.
Further,suggest you explore if the below resolutions can be adopted in your case.
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=10321987
http://wiki.sdn.sap.com/wiki/display/PLM/OriginalsinvisibleafterEHP3or+EHP4
Regards,
Pradeepkumar haragoldavar

Time machine says unable to complete back up an eror occurred while creating back up folder

Time machine shows error message "unable to complete back up an error occurred while creating back up folder" No error code is diplayed but if I turn the whole system off and restart it time machine backs up just the once

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to a failed backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showning, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

A fatal error occurred while creating an SSL client credential. The internal error state is 10013.

Hi All
I am seeing the below event appearing in the system log on all our Exchange 2013 servers regularly. I am not seeing any connectivity issues between any clients and the servers and no other issues have been reported at this stage.
Log Name:      System
Source:        Schannel
Date:          10/04/2015 9:21:17 AM
Event ID:      36871
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:
Description:
A fatal error occurred while creating an SSL client credential. The internal error state is 10013.
I am not sure if its related to the public certificate we are using or if its related to the one provided from the local CA.I have searched and found other links that suggest it could be related to SSL versions being disabled etc.
All servers are running Windows 2012 R2 Datacenter. The Exchange CAS servers do also sit behind a pair of F5 BIG IP Load Balancers
Any suggestions on where to look?
Thanks

Hi,
According to the event log, the issue is related to Schannel instead of Exchange.
Please try the following steps:
1.In Control Panel, click Administrative Tools, and then double-click Local Security Policy.
2.In Local Security Settings, expand Local Policies, and then click Security Options.
3.Under Policy in the right pane, double-click System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing, and then click Enabled.
4. Ran gpupdate /force
If it doesn’t work, please go to C:\ProgramData\Microsoft\Crypto\RSA and grant "Network Services" Read permission to "MachineKeys" folder. Then restart server to have a try.
Here is a similar thread for your reference:
https://social.technet.microsoft.com/Forums/lync/en-US/e70a8dbc-6f48-4fde-a93b-783554344822/a-fatal-error-occurred-when-attempting-to-access-the-ssl-client-credential-private-key?forum=ocscertificates
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Error occurred while creating dimension attributes.

Hi All,
         I have restored the back up file in the NW 10.0 environment (In BW 7.3 system using UJBR tcode the backup file was colleted from NW 7.5 system). In this process I have got an error "Error occurred while creating the dimension attributes via Admin API" and I have tried to resolve this with the program execution "UJA_ASSIGN_INFOOBJECTS_CATALOG". I am not able to open the Environment after this restore process completion. Could you guide me in this to resolve the issue. Please Let me know if you need more information to understand the issue.
Thanks and Regards,
Krishan.

Hi Nilanjan,
                  I have logged into the BPC system and able to open the APSHELLENVIRONMENTSHELL. When I tried to open a new environment which I have restored in the BW system error like "500-server ". Is this related to Service Pack ? or need to apply any new one to this system. And one more log I have observed in the process of DATA. When I have executed the UJA_DATA_CHECKER there is a message what I have got in this process " InfoObject catalog /CPMB/ENVIRONMENTSHELL_CHAR is not available in version A".
BW System Details:
                               SAPK-80102INCPMBPC
Thanks and Regards,
Krishna.

Time Machine Error: An error occurred while creating the backup directory

Time Machine Error: Unable to complete backup. An error occured while creating the backup directory.
I back up to wirelessly to a Time Capsule. I get these errors often. I'll go for a few days with everything working and then encounter these errors. I've even completely erased the Time Capsule drive and started over. It'll work fine for a few days and then start the errors over again. Interestingly, when the errors occur, the Time Capsule drive can not be unmounted even if clicking the eject button. I am on 10.5.8 but it happened in 10.5.7 as well. I have another Mac that doesn't seem to have any issues with the same Time Capsule.
Here's a log - they all seem to fail with similar errors:
Starting standard backup
Backup destination alias resolved to path: /Volumes/AirPort Disk
Disk image /Volumes/AirPort Disk/Brittney’s Computer_0019e33d4fde.sparsebundle mounted at: /Volumes/Backup of Brittney’s Computer
Backing up to: /Volumes/Backup of Brittney’s Computer/Backups.backupdb
2009-08-27 13:52:48.465 FindSystemFiles[2955:713] Querying receipt database for system packages
2009-08-27 13:52:48.693 FindSystemFiles[2955:713] Using system path cache.
Failed to create progress log file at path:/Volumes/Backup of Brittney’s Computer/Backups.backupdb/Brittney’s Computer/2009-08-26-212437.inProgress/.Backup.273091970.250248.log.
Error: (-50) Creating directory 7CCE60DD-ADCC-4004-A0D9-3EC83D892372
Failed to make snapshot.
Backup failed with error: 2
Failed to eject volume /Volumes/Backup of Brittney’s Computer (FSVolumeRefNum: -114; status: -47; dissenting pid: 0)

Nancy H wrote:
I used it as it came, supposedly formatted for a mac.
It may or may not be right.
I'd be inclined to start over, per #5 in the Frequently Asked Questions *User Tip* at the top of this forum.
If that doesn't help, go on to #C10, etc., in the Troubleshooting Tip, as in the previous post.

Hello I bought a G-Raid GR4 4000 4 TB and used it for a backup with my new Imac27. Now this is all I get. "Time Machine couldn't complete the backup to "G-RAID". to complete backup. An error occurred while creating the backup folder.

Hello I bought a G-Raid GR4 4000 4 TB and used it for a backup with my new Imac27. Now this is all I get. "Time Machine couldn’t complete the backup to “G-RAID”. to complete backup. An error occurred while creating the backup folder."
Any idea what I should do?

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the search box.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

An error occured while creating the original attribute for

Hi All,
We encounter this error in "An error occured while creating the original attribute for " DMS very often when a user edits a file & tries to check in.
I searched the forums & realized that this is caused by the inconsistencies in the KPRO & DMS server and removing these
inconsistencies will repair this issue.
I have been deleting the inconsistencies using DMS reports DMS_KPRO_READ & DMS_KPRO_CHECK1 and it resolves the error
so the file is unlocked. But I haven't been able to figure out the ROOT cause of this issue.I couldn't find any information on the root cause of this issue. What can be done to fix this error permanently.
Regards
-Neha

Hi Neha,
Please go to transaction SE16 and enter 'SDOKPROP' as table. Then enter 'DMS*' in the field PROP_NAME and press F8. Now all DMS related entries should be displayed to you. Please compare them with the following entries displayed in the attached screenshot and maintain the missing entries.
DMS_ACTIVE_VERSION 00 Active Version
DMS_APPLICATION 00 Logical application
DMS_CHECKOUT_USER 00 Checkout User
DMS_CREATE_AUDIT 00 Generate new version of the original
DMS_DEFAULT_LANGUAGE 00 Default Language
DMS_DELETEABLE 00 PHIO deletable
DMS_DOC_KEY 02 IWB_DMS01 DMS_DOCKEY Document info record
DMS_DOC_VERSION 00 Version of relevant document
DMS_DRAW_APPNR 00 Application number from DRAW
DMS_DRAW_DTTRG 00 Data carrier from DRAW
DMS_DRAW_FILEP 00 File name from DRAW
DMS_FILE1 00 File name(firstpart)
DMS_FILE2 00 File name(secondpart)
DMS_FILE3 00 File name(thirdpart)
DMS_FILE_ID 00 GUID that points to table DMS_PHIO2FILE
DMS_FRMTXT 00 Format description, ID of additional file
DMS_MUP_CAT 00 Markup category
DMS_MUP_FLAG 00 Markup flag
DMS_ORDER 00 Sequence of additional files
DMS_STATUS 00 Document status
DMS_STATUSNR 00 Number in status protocol
DMS_STATUSNR_X 00 References to Status Log
Please pay attention that all entries are typed well and that there are no spelling errors. If all these values are maintained correctly in table SDOKPROP the dump and the error message should no longer appear.
For further information you can also see the corresponding SDN WIKI page under
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/plm/error26296in+CV01N
Regards,
Ravindra

Error: Time Machine couldn't complete the backup to Time Capsule - Unable to complete backup. An error occurred while creating the backup folder.

error: Time Machine couldn't complete the backup to Time Capsule - Unable to complete backup. An error occurred while creating the backup folder.

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

"An occurred while creating a domain log handler"

Similar Messages

Maybe you are looking for