Could not send permission request...

I just set up my daughter with her own .mac account. When I attempt to send a message from her account, I'm prompted to 'request parental permission'.
I click on 'Ask Permission' and am presented with the message...
'Could not send your permission request to your parent...'
Her email settings are the same as mine with the exception of ID and password.
Setting up in System Preferences and Mail worked just fine.
Any ideas?
Thanks...Kevin

I'm wondering why there are no replies to this at all.
Probably because you're talking about a new feature (Parental Controls) that few people use or have experience with.
Are there any Apple employees that look over
these discussions?
http://discussions.apple.com/help.jspa
I'm still unable to get this working.
Open Mail Help, type "parental controls" in the search box and press <Return>. Post back here if there is something there you don't understand or need more info.
Is it worth posting a problem here?
Usually, yes.
Or is this just for problems that are easy to solve?
I assure you that, each and every day, problems much, much harder than yours are being solved in this forum.

Similar Messages

  • TT14000: TimesTen daemon internal error: Could not send 'manage' request

    Hi
    I have got error like TimesTen daemon internal error: Could not send 'manage' request .Can any one help, why this error is came and what is solution for this.
    I have restarted the Timesten Daemon now its working fine.But why i got that error?
    Below is the tterror log :
    12:50:27.53 Err : : 31518: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc 400 err1 703 err2 836
    12:50:28.52 Warn: : 31518: 31522 ------------------: subdaemon process exited
    14:04:21.95 Warn: : 31518: 31619/0xcce7500: Recovery started
    14:04:23.01 Warn: : 31619: subd: Warning identified in [sub.c: line 2152]
    14:04:23.01 Warn: : 31619: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    14:04:23.01 Warn: : 31619: -- file "db.c", lineno 12011, procedure "sbDbConnect"
    14:04:23.01 Warn: : 31619: subd: connect trouble, rc 2, reason 20100
    14:04:23.01 Warn: : 31619: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    20:23:57.74 Warn: : 31518: 9216 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
    21:15:17.79 Warn: : 31518: 22608 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
    09:22:11.63 Warn: : 31518: 32431 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=21
    09:28:03.52 Warn: : 31518: 32417 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
    20:26:56.30 Warn: : 31518: 1165 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=1
    20:40:31.73 Warn: : 31518: 21549 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=3
    23:17:52.64 Warn: : 31518: 29899 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=20 '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=215
    09:42:29.96 Warn: : 31518: 22044 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=10
    13:12:19.91 Warn: : 31518: 16923 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=10
    19:42:46.21 Warn: : 31518: 10794 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1174700038 count=10
    00:00:06.83 Warn: : 6786: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 34 users
    00:00:06.83 Warn: : 6786: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
    00:00:06.83 Warn: : 6786: WARNING: data store no longer considered in use
    00:00:06.84 Warn: : 6786: WARNING: PL/SQL shared segment existed at time of daemon termination
    00:00:06.84 Err : : 6786: TT14000: TimesTen daemon internal error: Could not destroy PL/SQL shared memory, error
    00:00:06.84 Warn: : 6786: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    00:00:15.32 Warn: : 6786: 6792/0x1edfc500: Recovery started
    00:00:16.39 Warn: : 6792: subd: Warning identified in [sub.c: line 2152]
    00:00:16.39 Warn: : 6792: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    00:00:16.39 Warn: : 6792: -- file "db.c", lineno 12011, procedure "sbDbConnect"
    00:00:16.39 Warn: : 6792: subd: connect trouble, rc 2, reason 20100
    00:00:16.39 Warn: : 6792: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    17:51:04.03 Warn: : 6786: 17730 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1225031686 count=10
    10:03:44.61 Warn: REP: 7064: TT_TT70_32:receiver.c(7921): TT16191: Replacing old table definition (OASTT.USER_AUTH) with the one received from peer (TT_TT70_32_MASTER)
    10:03:52.28 Warn: REP: 7064: TT_TT70_32:receiver.c(7921): TT16191: Replacing old table definition (OASTT.USER_AUTH) with the one received from peer (TT_TT70_32_MASTER)
    10:04:02.73 Warn: REP: 7064: TT_TT70_32:receiver.c(7921): TT16191: Replacing old table definition (OASTT.USER_AUTH) with the one received from peer (TT_TT70_32_MASTER)
    17:58:15.58 Warn: : 6786: 15156 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1225031686 count=7
    18:02:14.24 Warn: REP: 7064: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
    18:02:25.07 Warn: REP: 7064: got termination signal, stopping
    18:02:25.81 Warn: : 6790: got termination signal, stopping
    18:02:25.86 Warn: : 6792: got termination signal, stopping
    18:02:25.87 Err : : 6786: TT14006: TimesTen daemon disconnect failed: 6792/0x2aaab80008c0: disconnect complete: Disconnect not started. Info: 0 7064 0x1f758520 (/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32)
    18:02:25.87 Err : : 6792: TT14000: TimesTen daemon internal error: subd: Monitor thread failed to disconnect, tt error 798 (TT0798: Daemon reports error 0 -- file "db.c", lineno 16124, procedure "sbDbDisconnect").
    18:02:25.87 Warn: : 6786: got termination signal, stopping
    18:02:25.91 Warn: : 6789: got termination signal, stopping
    18:02:25.95 Warn: : 6791: got termination signal, stopping
    18:02:26.05 Err : : 6786: TT14000: TimesTen daemon internal error: Could not connect to subdaemon port 43791
    18:02:26.05 Err : : 6786: TT14006: TimesTen daemon disconnect failed: error -1 in stopManaging
    18:02:26.05 Err : REP: 7064: TT_TT70_32:repagent.c(3338): TT16005: Failed to disconnect from datastore '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' for 'REPHOLD' thread
    18:02:26.05 Err : REP: 7064: TT_TT70_32:repagent.c(3338): TT791: TT0791: Cannot communicate with subdaemon -- file "db.c", lineno 16124, procedure "sbDbDisconnect"
    18:02:26.05 Warn: : 6786: 6792 ------------------: subdaemon process exited
    18:02:26.05 Warn: : 6786: 6792 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1225031686 count=10
    18:02:26.05 Warn: : 6786: daRecovery: subdaemon 6792, managing data store, failed: invalidate (failcode=202)
    18:02:26.05 Warn: : 6786: Invalidating the data store (failcode 202, recovery for 6792)
    18:02:26.11 Err : : 6786: Could not connect to subdaemon 6794, port 56784
    18:02:26.28 Warn: : 6786: 6789 ------------------: subdaemon process exited
    18:02:26.53 Warn: : 6786: 6791 ------------------: subdaemon process exited
    18:02:26.59 Warn: : 6786: 6790 ------------------: subdaemon process exited
    18:02:26.71 Err : : 6786: Could not connect to subdaemon 7064, port 45797
    13:42:14.95 Warn: : 10502: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    13:42:32.63 Err : : 10502: TT14000: TimesTen daemon internal error: Error 22 creating shared segment, KEY 0x4e048006
    13:42:32.63 Err : : 10502: -- OS reports invalid shared segment size
    13:42:32.63 Err : : 10502: -- Confirm that SHMMAX kernel parameter is set > datastore size
    13:42:32.63 Err : : 10508: subd: Error identified in [sub.c: line 2152]
    13:42:32.63 Err : : 10508: subd: (Error 836): TT0836: Cannot create data store shared-memory segment, error 22 -- file "db.c", lineno 9572, procedure "sbDbConnect"
    13:42:32.63 Err : : 10508: -- file "db.c", lineno 9572, procedure "sbDbConnect"
    13:42:32.63 Warn: : 10508: subd: connect trouble, rc 1, reason 836
    13:42:32.63 Err : : 10508: Err 836: TT0836: Cannot create data store shared-memory segment, error 22 -- file "db.c", lineno 9572, procedure "sbDbConnect"
    13:42:32.63 Err : : 10502: TT14000: TimesTen daemon internal error: Could not send 'manage' request to subdaemon rc 400 err1 703 err2 836
    13:42:33.63 Warn: : 10502: 10508 ------------------: subdaemon process exited
    13:46:59.96 Warn: : 10502: 10605/0x819500: Recovery started
    13:47:01.02 Warn: : 10605: subd: Warning identified in [sub.c: line 2152]
    13:47:01.02 Warn: : 10605: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    13:47:01.02 Warn: : 10605: -- file "db.c", lineno 12011, procedure "sbDbConnect"
    13:47:01.02 Warn: : 10605: subd: connect trouble, rc 2, reason 20100
    13:47:01.02 Warn: : 10605: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 12011, procedure "sbDbConnect"
    15:37:47.14 Warn: : 10502: 28930 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1392803846 count=1
    19:41:05.92 Warn: : 10502: 28950 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=1
    12:18:40.18 Warn: : 10502: 19264 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=16
    19:09:15.13 Warn: : 10502: 29472 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=24
    20:29:21.07 Warn: : 10502: 6896 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=27
    11:11:30.98 Warn: REP: 18767: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
    14:26:06.81 Warn: : 10502: 25502 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=3
    10:52:42.36 Warn: : 10502: 6487 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=12
    11:06:20.50 Warn: : 10502: 15322 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=1
    13:19:36.58 Warn: REP: 18767: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
    16:48:45.24 Warn: : 10506: got termination signal, stopping
    16:48:45.48 Warn: : 10505: got termination signal, stopping
    16:48:45.95 Warn: : 10502: 10505 ------------------: subdaemon process exited
    16:48:45.95 Warn: : 10502: 10506 ------------------: subdaemon process exited
    16:48:45.99 Warn: REP: 18767: got termination signal, stopping
    16:48:46.20 Warn: : 10507: got termination signal, stopping
    16:48:46.26 Warn: : 10502: got termination signal, stopping
    16:48:46.86 Warn: : 10605: got termination signal, stopping
    16:48:46.95 Warn: : 10502: 10507 ------------------: subdaemon process exited
    16:48:46.99 Err : : 10502: TT14000: TimesTen daemon internal error: Could not connect to subdaemon port 36872
    16:48:46.99 Err : : 10502: TT14006: TimesTen daemon disconnect failed: error -1 in stopManaging
    16:48:46.99 Err : REP: 18767: TT_TT70_32:repagent.c(3338): TT16005: Failed to disconnect from datastore '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' for 'REPLISTENER' thread
    16:48:46.99 Err : REP: 18767: TT_TT70_32:repagent.c(3338): TT791: TT0791: Cannot communicate with subdaemon -- file "db.c", lineno 16124, procedure "sbDbDisconnect"
    16:48:46.99 Warn: : 10502: 10605 ------------------: subdaemon process exited
    16:48:46.99 Warn: : 10502: 10605 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1594130438 count=10
    16:48:46.99 Warn: : 10502: daRecovery: subdaemon 10605, managing data store, failed: invalidate (failcode=202)
    16:48:46.99 Warn: : 10502: Invalidating the data store (failcode 202, recovery for 10605)
    16:48:47.09 Err : : 10502: Could not connect to subdaemon 10510, port 58206
    16:48:47.16 Err : : 10502: Could not connect to subdaemon 18767, port 49611
    13:17:45.67 Warn: : 8602: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    13:17:52.84 Warn: : 8602: 8605/0x12207500: Recovery started
    13:18:41.73 Err : : 8602: 8789/(nil): /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/snmp.ini: bad -trap_dest value SMARTS4: Host not found (authoritative answer)
    13:31:31.49 Warn: : 8602: 5706 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=1
    01:25:41.22 Warn: : 8602: 18419 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=158
    10:29:11.03 Warn: : 8602: 30002 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=43
    12:47:07.86 Warn: : 8602: Invalidating in-RAM shared data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because in use at exit
    12:47:07.87 Warn: : 8602: 8605/0x123481a0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    12:47:07.88 Warn: : 8605: Stopping subdaemon Log Marker thread for /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because db is invalid.
    12:47:07.88 Warn: : 8602: 8605/0x123a47b0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    12:47:07.96 Warn: : 8602: 8605/0x1243c900: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    12:47:08.88 Warn: : 8602: 8605 ------------------: subdaemon process exited
    12:47:08.88 Warn: : 8602: 8605 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 1745125382 count=10
    12:47:34.78 Warn: : 20263: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 11 users
    12:47:34.78 Warn: : 20263: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
    12:47:34.78 Warn: : 20263: WARNING: data store no longer considered in use
    12:47:34.78 Warn: : 20263: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    12:51:06.94 Warn: : 20263: 20266/0x14690500: Recovery started
    16:29:00.34 Warn: : 20263: 22849 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 134512646 count=1
    10:12:26.98 Warn: REP: 20784: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. TimesTen replication agent is stopping
    10:12:30.91 Warn: : 20263: Invalidating in-RAM shared data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because in use at exit
    10:12:30.91 Warn: : 20263: 20266/0x1479ff40: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:30.91 Warn: : 20266: Stopping subdaemon Log Marker thread for /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because db is invalid.
    10:12:30.91 Warn: : 20263: 20266/0x1488b830: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:30.96 Warn: : 20263: 20266/0x1486fa40: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.03 Warn: : 20263: 20266/0x2aaac40008c0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.34 Warn: : 20263: 20266/0x2aaac401c6b0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.40 Warn: : 20263: 20266/0x2aaac00008c0: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.66 Warn: : 20263: 20266/0x2aaac4078700: Forced Disconnect /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32
    10:12:31.91 Warn: : 20263: 20266 ------------------: subdaemon process exited
    10:12:31.91 Warn: : 20263: 20266 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 134512646 count=10
    10:12:36.28 Warn: : 14678: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 11 users
    10:12:36.28 Warn: : 14678: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
    10:12:36.28 Warn: : 14678: WARNING: data store no longer considered in use
    10:12:36.28 Warn: : 14678: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    10:13:25.52 Warn: : 14678: 14683/0x5121500: Recovery started
    10:10:12.39 Warn: : 14678: 15486 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=1
    10:06:55.19 Warn: : 14678: 30796 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=2
    09:58:48.69 Warn: : 14678: 12930 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=2
    15:27:42.39 Warn: : 14678: 7811 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=2
    10:16:36.60 Warn: REP: 14964: TT_TT70_32:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out
    10:53:27.24 Warn: : 14678: 11658 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=1
    15:11:33.81 Warn: : 14678: got termination signal, stopping
    15:11:34.63 Err : : 14678: Could not connect to subdaemon 14686, port 41664
    15:11:34.72 Warn: : 14682: got termination signal, stopping
    15:11:35.10 Warn: : 14681: got termination signal, stopping
    15:11:35.11 Warn: : 14684: got termination signal, stopping
    15:11:35.23 Warn: : 14683: got termination signal, stopping
    15:11:35.35 Warn: : 14678: 14684 ------------------: subdaemon process exited
    15:11:35.43 Warn: REP: 14964: got termination signal, stopping
    15:11:35.53 Warn: : 14678: 14681 ------------------: subdaemon process exited
    15:11:35.55 Warn: : 14678: 14682 ------------------: subdaemon process exited
    15:11:36.29 Err : : 14678: TT14000: TimesTen daemon internal error: 14683: Error processing 'unmanage' in subdaemon rc -2
    15:11:36.29 Err : : 14678: TT14000: TimesTen daemon internal error: Unparsable reply to unmanage
    15:11:36.29 Err : : 14678: TT14006: TimesTen daemon disconnect failed: error -1 in stopManaging
    15:11:36.29 Err : REP: 14964: TT_TT70_32:repagent.c(3338): TT16005: Failed to disconnect from datastore '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' for 'REPLISTENER' thread
    15:11:36.29 Warn: : 14678: 14683 ------------------: subdaemon process exited
    15:11:36.29 Err : REP: 14964: TT_TT70_32:repagent.c(3338): TT798: TT0798: Daemon reports error 0 -- file "db.c", lineno 16124, procedure "sbDbDisconnect"
    15:11:36.30 Warn: : 14678: 14683 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 201621511 count=1
    15:11:37.63 Warn: : 14678: Invalidating in-RAM shared data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because in use at exit
    15:54:42.72 Warn: : 8962: Invalidating the data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 because it had 1 users
    15:54:42.73 Warn: : 8962: WARNING: data store /opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32 was in use at daemon termination.
    15:54:42.73 Warn: : 8962: WARNING: data store no longer considered in use
    15:54:42.73 Warn: : 8962: WARNING: PL/SQL shared segment existed at time of daemon termination
    15:54:42.73 Err : : 8962: TT14000: TimesTen daemon internal error: Could not destroy PL/SQL shared memory, error 22
    15:54:42.73 Warn: : 8962: TimesTen Daemon Release 11.2.1.3.0.TT_tt70_32 started.
    15:54:48.61 Warn: : 8962: 8973/0x17292500: Recovery started
    16:15:24.25 Warn: : 8962: 5703 exited while connected to data store '/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_tt70_32' shm 251953159 count=1
    15:32:17.57 Warn: : 8962: 8974/0xff51500: Recovery started
    15:32:55.78 Warn: REP: 28114: SIPT_TT_SUB4:receiver.c(2682): TT16060: Failed to read data from the network. select() timed out

    1)
    TimesTen Release 11.2.1.3.0 (64 bit Linux/x86_64) (TT_tt70_32:53388) 2009-08-21T05:34:23Z
    Instance admin: timesten
    Instance home directory: /opt/timesten/tt7032/TimesTen/TT_tt70_32
    Group owner: timesten
    Daemon home directory: /opt/timesten/tt7032/TimesTen/TT_tt70_32/info
    PL/SQL enabled.
    2)
    [TT_1121]
    Driver=/opt/timesten/tt7032/TimesTen/TT_tt70_32/lib/libtten.so
    DataStore=/opt/timesten/tt7032/TimesTen/TT_tt70_32/info/TT_1121
    DatabaseCharacterSet=US7ASCII
    3)
    kernel.shmmax = 2147483648
    kernel.shmall = 2097152
    4)
    MemTotal: 8171576 kB
    MemFree: 3754532 kB
    Buffers: 312052 kB
    Cached: 1656640 kB
    SwapCached: 0 kB
    Active: 3924072 kB
    Inactive: 309660 kB
    HighTotal: 0 kB
    HighFree: 0 kB
    LowTotal: 8171576 kB
    LowFree: 3754532 kB
    SwapTotal: 8388600 kB
    SwapFree: 8388600 kB
    Dirty: 652 kB
    Writeback: 4 kB
    AnonPages: 2265060 kB
    Mapped: 153924 kB
    Slab: 126580 kB
    PageTables: 12320 kB
    NFS_Unstable: 0 kB
    Bounce: 0 kB
    CommitLimit: 12474388 kB
    Committed_AS: 4718116 kB
    VmallocTotal: 34359738367 kB
    VmallocUsed: 284328 kB
    VmallocChunk: 34359452663 kB
    HugePages_Total: 0
    HugePages_Free: 0
    HugePages_Rsvd: 0
    Hugepagesize: 2048 kB

  • CS6 Error: "Could not complete your request because of a program error."

    I get the error "Could not complete your request because of a program error." anytime I try to open a .psd file someone has sent me.
    This error is occuring in CS6.
    Anything I can do?

    Hi Basedcade,
    Do you know what version of Photoshop was used to create the .psd they are sending? II'd want to make sure the person sending the .psd is selecting the option to maximize compatibility when saving the .psd file. How is the person sending you the .psd file, email, etc.? Does the person sending it have an Adobe ID? If so, maybe have them upload the .psd and share it via Creative Cloud to see if it does the same thing when transferred that way?
    -Dave

  • ERROR MESSAGE: Could Not Complete your request ...

    I've been looking into all the sites about the problems I have. included here. like a has-been, I get an error on the "Could Not Complete your request Because the file is not compatible with this version of photoshop". because power outages at my house unexpectedly. and finally I get the error message. read advice from a site that I'm looking for, they said, using the old version of photoshop. I'm using Photoshop CS3. and tried to open my files with Photoshop CS2. after I try, I managed to open my file. but all the images disappear. there are only empty layers that should contain pictures. why did it happen? Can you help me? maybe I'll send my file to you. I really need your help all. I hope you will help me. Thank you.

    You had a power outage did you run chkdsk to see if the disk has any errors ? After a power failure its a good idea to run chkdsk /F

  • "Could not complete your request because it is not a valid Photoshop document"?

    Hi
    i am getting this error  "Could not complete your request because it is not a valid Photo shop document"
    i am using CS 5 . PSD files are from different sources. some are saved by me and some are from INTERNET . all files was working fine 3 weeks ago .
    i moved them to external hard drive.I installed window 7 and moved all files from hard disk to My PC ( there was no error while moving files from HD to PC)
    Now when i try to open  it shows "Could not complete your request because it is not a valid Photoshop document"?
    here is file link  Download 36-web-buttons-collection.psd from Sendspace.com - send big files the easy way
    i did try many PSD repair  software but nothing works
    please help me . i need those file very badly
    regards
    sahil !
    (please ignore my bad English)

    It is only showing as a psd file in Windows, because it merely happens to have the extension ".psd". That does not mean that the file is an actual Photoshop file.
    You could rename it to a file with a zip extension, and Windows would think it is an archive.
    The extension means nothing unless the actual file data is written as a psd. And in this case it is not. You have file that is NOT a psd, with a file extension ".psd".
    Show or hide file name extensions - Windows Help

  • Could not complete your request

    Receiving message could not complete your request because photoshop does not recognize this type of file.
    My wife just installed mavericks and updated to flash 11. When we try to bring a photo into pse 12 . We receive the above message.
    We are trying to bring the photo in from iphoto.
    thanks,
    gary

    You can't just jump into the iphoto library from outside iphoto. That is just begging for your iphoto library to get corrupted and lose all the photos in it. You have two options:
    1. Set PSE as your external editor and send the photos from iphoto. If you want to do that, choose this file:
    Then Save, not Save As, and iphoto will remember your last edits plus the original, although you must lose the edited version to revert to the original. You may need to set the PSE editor prefs>Saving Files>on first save to save over existing to make this work.
    2. Export the photo from iphoto to the desktop, do whatever you want including changing name or format, save your work and import the edited file back to iphoto as a new image. It won't be a version, but you can save as many versions as you like using this method.

  • Workflow : Could not send e-mail [10014 : email ...

    hi,
    i am trying to send email notification via workflow, but i am not able to do so. anyone can help to troubleshoot this?
    below are the steps i have carried out for email configuration:
    1. i have added the mail server on mds.ini, MDS is restarted after every changes.
    2. requester and approval has correct email setup at console.
    3. a notification is added in workflow.
    4. telnet ping to mail server with port 25 is fine.
    when i check the log, i have the error :
    "Could not send e-mail [10013 : email : Notify] [Mail server:xxxxxxxxx] [From address:xxxxxxxx] [To address:xxxxxxx
    i know the guidelines and steps for configurations, but apparently it does not workout, so any troubleshoot guideline will be more appreciated.
    Thanks!
    Shanti

    Hi Shanti,
    I am sure you must have checked all this but then again would you please check following things and let us know ?
    1) Please check the SMTP Server Name in your Outlook Express if you are using Outlook
    2) Please log into MDS file and go under that particular Repositoy and check what details you have given for Mail Server
    3) Please give SMTP address in mail server line
    4) Log into Console and check if you have alligned Users and Roles to each other correctly or not.
    5) log into Data Manager and open the workflow and check the properties of Mail notification stencil and check if correct proertise are set ot not.
    Once you have made the changes at server level please restart the server again and then please let us know if this problem exist or not, may be we can more troubleshoot it further.
    Thanks and Regards
    Praful.

  • Could not send notification 65569 (status 'FAILED')

    Customize Workflow runs with 2006 error - only happen in the morning
    We have created a customize workflow which works a bit funny here:
    When we first run the workflow in the morning, it ends up with this error:
    Activity Buyer Notifications
    Result Mail
    Error Name WFMLRSND_FAILED
    Error Message 2006: Could not send notification 65569 (status 'FAILED') to 'CONTRACT SERVICES'.
    Error Stack WF_MAIL.GetDocContent(PO_DETAILS_BUYER)
    Then, thinking of some problem might happend to the workflow mailer, we run the standard workflow, e.g. PO Approval. It runs successfully and send out the notification email. So, we then run the customise workflow again, and this time it works, no error has been generated as above.
    The funny thing is, this had happened more than a week, where every morning I have to somehow run a standard workflow (normally I just create a new PO and send for approval), and got my customize workflow run successfully.
    Can someone highlight what's going wrong here?
    Is that some setup or soemthing that contribute to this problem?
    Thanks,
    Patricia

    The notifications are defined in the workflow but they do use a document type attribute (we send a table of data "Job", "Job Name", "Amounts").
    We have changed the database packages a lot and that created many problems afterwards so we minimized when we make those changes and we restart everything (database, IAS Server) afterwards.
    Here is the email to SYSADMIN:
    =========================================================
    Subject: Error in Workflow DUNAPIN2/20060323123955x30741282 2006: Could not send notification 41119 (status 'ERROR') to 'KKEMPER'.
    From
    To SYSADMIN
    Sent 03-APR-06
    Due
    Notification ID 41121
    An Error occurred in the following Workflow.
    Item Type = DUNAPIN2
    Item Key = 20060323123955x30741282
    User Key =20060323123955x30741282
    Error Name = WFMLRSND_FAILED
    Error Message = 2006: Could not send notification 41119 (status 'ERROR') to 'KKEMPER'.
    Error Stack = &ERROR_STACK
    Activity Id = 52557
    Activity Label = GET_GENERAL_LEDGER_APPROVAL:NTF_V2_AR_DEPT_OFF_MGR
    Result Code = #MAIL
    Notification Id = 41119
    Assigned User = KKEMPER
    Workflow monitor
    Please click on one of the following choices to automatically generate an E-mail response. Before sending the E-mail response to close this notification, ensure all response prompts include a desired response value within quotes.
    How do you want to Continue?
    How do you want to continue?: Abort Resolved Retry Request information
    =========================================================
    Any help would be greatly appreciated.
    Jim

  • I can't import any photos. 'Could not copy to requested location' is the given but i have tried importing to both hard drive and external drive.

    i can't import any photos. 'Could not copy to requested location' is the given but i have tried importing to both hard drive and external drive. Help please ?

    Most likely, the "requested location" where you are trying to copy files to does not have WRITE permission, and so you need to change the permissions.

  • Could not complete your request because an adjustment or fill layer cannot be converted to the desti

    Getteing the following message when dragging layers between files - Could not complete your request because an adjustment or fill layer cannot be converted to the destination document mode. Original file was client created and supplied. I have issolated the issue- two hue/saturation adjustment layers. I can and will just recreate them in the new file, but am looking for a root casue or long termsolution as it is a new client I believe will be sending me a good amount of production work.

    Actually, 16-bit mode (some filters work in 8-bit only, though) is recommended to reduce the introduction of posterization which can easily arise with the relatively low precision of 8-bit mode. It doesn't benefit all work, but, especially if you use adjustments or low-opacity brushes, it's something to consider.

  • "could not complete the requested operation" Illustrator CS4 OS X

    I've searched online and in the forums for a solution to this issue. I'm running OS X 10.5.8 and have CS4 installed. Every other application in the suite works except Illustrator. I get the error "could not complete the requested operation" on startup and then Illustrator tries to send a crash report.
    I'm out of town and don't have my original copies of the software with me so I cannot reinstall. >_<
    Does anybody know how this might be fixed? I really need to get some work done and I'm stuck!

    you probably did not read that document I gave you a link to becuse i think they mention the problem you are encountering and why.
    I am not being sarcastic but you do have to read more carefully. I'm guilty sometimes of this myself.
    but not often
    form the Adobe systems requirements you should read it but I can tell you it won't launch on your system so you will have to updte it.
    Seee it clearly say Mac OS X 10.6.8 or 10.7
    Mac OS
    Multicore Intel processor with 64-bit support
    Mac OS X v10.6.8 or v10.7
    2GB of RAM (8GB recommended)
    2GB of available hard-disk space for installation; additional free space required during installation (cannot install on a volume that uses a case-sensitive file system or on removable flash storage devices)
    1024x768 display (1280x800 recommended) with 16-bit video card
    DVD-ROM drive compatible with dual-layer DVDs
    This software will not operate without activation. Broadband Internet connection and registration are required for software activation, validation of subscriptions, and access to online services.† Phone activation is not available.

  • LIBTUX_CAT:1286: ERROR: tpreturn could not send reply TPEOS

    Hi,
    Our application uses tuxedo for loadbalancing. we are using this from last 4 years, but today i'm getting one error with one scenario. As per my understading tpreturn call is failing. ULOG file shows below given message
    032615.ocpdev1!BBL.14797.1.0: LIBTUX_CAT:216: WARN: Process 18711 died; removing from BB
    032813.ocpdev1!issueHolders.18634.1.0: ERROR: msgsnd err:(LIBTUX_CAT:669: ERROR: Message operation failed because of the invalid message queue identifier) er
    rno=22,qid=188425,buf=-9223372026643562600,bytes=293,flag=2048
    032813.ocpdev1!issueHolders.18634.1.0: LIBTUX_CAT:1286: ERROR: tpreturn could not send reply TPEOS - operating system error
    I have searched google pages and couldn't get any clue. I have tried modifying UBB Config file with SYSTEM_ACCESS parameter to PROTECTED and other parameters but no use.
    Please let me know what can be done.

    Hi,
    I think you are referring to the documentation for error LIBTUX_CAT:1286, which suggests tuning the kernel parameters as a more general solution. The explanation for LIBTUX_CAT:669 is more specific (earlier messages in the ULOG usually give a more specific reason for the problem):
    +669 ERROR: Message operation failed because of the invalid message queue identifier+
    Description
    msgsnd to a queue failed because of invalid message queue identifier. This can also occur if a request is made by a client who exits before the request is satisfied. The cleanup after the client exits removes the message queue.
    Action
    Check the message queue identifier in msgsnd(). The message may be corrupted. Contact your ORACLE TUXEDO system Technical Support.
    Increasing the kernel parameters will not help in this case, as the problem is due to the queue having been removed, which happens when the client program terminates, and it is quite likely that there will be no messages in the ULOG indicating what happened. You will need to follow the suggestions made earlier in this forum thread and find out what happened to the client.
    Regards,
    Malcolm.

  • I am getting the error message "could not copy to requested location" to a drive i have been using for over a year... when I do the same thing to another drive - it works just fine. why?

    i am getting the error message "could not copy to requested location" to a drive i have been using for over a year... when I do the same thing to another drive - it works just fine. why?

    Possibly the drive is full
    Possibly the permissions are not set to WRITE permission
    Possibly there has been a "user mistake" and you think you are copying to a drive you have been using for over a year but something has accidentally changed and you're copying to a different location

  • Error:  "Could not complete your request because of a program error" (photoshop CS2 9.0.2 on MAC OSX

    Today I started my program (photoshop CS2 9.0.2) and opened a JPG file. When I went to print the file the program crashed and closed. When I restarted the program and went to open the file I got this error message, "Could not complete your request because of a program error".
    I have tried several different file types/sizes and all result in the same error message since the program crashed. It will not open any file I try to open. As I indicated above I am using Photoshop CS2 9.0.2 it is on a MAC with OSX 10.4.11.
    I called Adobe and the Rep directed me to Tech Note 331307 and told me to Re-create the Photoshop preferences files. Which I did and restarted the program, but when I tried to open a file (any file) I still get the same error message so it doesn't appear to be the preferences.
    Does anyone have any info as to what the problem may be and how to correct it.
    Thanks

    Thanks for the response. OK... This is the first day I have been able to get back to the problem.
    My system I am running Photoshop on is a Power Mac G4, AGP Graphics ATY Rage 128Pro chip set 16MB VRAM LCD 1280x1024 32-bit color, 500MHz, 1.75GB of memory, 1 MB L2 Cache, 100 MHz Bus Speed. I had installed the latest security update and repaired the permissions the day the problem started.
    Now to day I started the system and went in and created a Guest Account. I logged into the guest account and started Photoshop. Low and behold it worked just fine. So I logged out of guest and logged into my main user account And started Photoshop. Wouldn't you know it.... It works just fine. I can open any file I want with now problems.
    I got to thinking after I had done all of this that I wished I had tried to open a file in Photoshop today prior to creating the guest account to see if it still had the problem in my main user account.
    I did not change anything else on the system and all seems to work fine now. So at his point I am really not sure what the problem was.
    Again thanks for taking the time to respond to this issue.

  • I want to edit my raw images on cs5 photoshop.  But when I go to open the .CR2 file it says  '' Could not complete your request because the file appears to be from a camera model which is not supported by the installed version of Camera Raw. Please visit

    I want to edit my raw images on cs5 photoshop.  But when I go to open the .CR2 file it says 
    '' Could not complete your request because the file appears to be from a camera model which is not supported by the installed version of Camera Raw. Please visit the Camera Raw help documentation for additional information.  '' 
    When I go to updates in photoshop help i try to update photoshop and photoshop camera raw but it then says 
    '' Updates could not be applied the error log file may help you in identifying the problem. Then, try updating again. If the problems persist, contact customer support for further assistance. 
    Photoshop Camera Raw 8.7.1(CS6) There was an error installing this update. Please quit and try again later. Error Code: U44M1I216 ''  
    I dont know how to get around this please help

    CR2 files from which Canon camera?
    Supported cameras are listed here
    Camera Raw plug-in | Supported cameras

Maybe you are looking for