RPC failure

Hi,
Im hoping you guys might be able to help me out. I have an E3500 server, and Im installing Solaris 2.5.1. I know its old, but my company isn't slated to update to Solaris 8 until next year. Anyhow. I can load the OS and all my programs fine. The problem is when I load a Specific Solaris updates package which contains numerous updates. The server loads in Single user mode, and after reboot I start recieving the following errors:
rcpbind: unable to set RPC max record size.
ls.so.l: /usr/sbin/rpcbind: fatal: relocation error: file /usr/sbin/rpcbind: symbol_svc_vc_set_tcp_keepalive: referenced symbol not found.
Killed
rpcbind
The system will then take for ever to get to a login prompt and hang when ever any account tries to log in.
What is strange is that before my hard drive failed, and I had to reload. This package was installed with no problems. I have tried reloading Solaris twice now, and both times everything is running great until the update. Unfortunetly the package is mandatory per my home office or I just would not load it.

You might try doing a ldd on the /usr/sbin/rpcbind binary to make sure all it libraries are showing. But technically if a library isn't rpcbind will fail before you get the error below.
This may sound painful but you might try a find command looking for all *.so files and then running nm on the library and grep'ing for symbol_svc_vc_set_tcp_keepalive. If you find it, see if the LD_LIBRARY_PATH includes the path for that library.

Similar Messages

  • Adding Metaset, rpc failure -7

    Hi,
    I try o add a new resource group and diskset to a cluster, and my metaset cmd fails with an rpc failure -7
    Solaris 10 11/06, Sun Cluster 3.1 on a Sun Fire V890
    root@node2:~ # metaset -s XXXX -a -h node2 node1
    ERROR: node1: rpc failure -7
    root@node2:~ # metaset -s XXXX
    Set name = XXXX, Set number = 9
    Host                Owner
      node2
      node1
    root@node2:~ # RPC should be OK:
    root@node2:~ #  rpcinfo node1 | grep md
        100145    1    ticots    \000\000\000C       scadmd     superuser
        100145    1    ticotsord \000\000\000F       scadmd     superuser
        100145    1    tcp       0.0.0.0.128.11      scadmd     superuser
        100533    1    ticots    \000\000\000K       scrcmd     superuser
        100533    1    ticotsord \000\000\000N       scrcmd     superuser
        100533    1    tcp       0.0.0.0.128.12      scrcmd     superuser
        100141    1    tcp       0.0.0.0.128.25      rgmd_receptionist superuser
        100141    1    ticotsord \000\000\000h       rgmd_receptionist superuser
        100141    1    ticots    \000\000\000j       rgmd_receptionist superuserThe hostname is not in /etc/hosts and /etc/inet/ipnodes as it is only an alias, but i have the ip addresses in /etc/hosts.allow. It worked with this setup two days ago.
    We had a problem with a failed fibre channel interface which has been fixed. I ran an scgdevs on node2.
    Any idea what the rpc failure -7 means.
    Fritz

    Tom,
    I faced a similar issue recently and the problem at the time was due to the unstable network. However, I'll let the experts confirm if -7 error is indeed for network related failures when creating a metaset.
    Though the -7 error was returned, all metaset commands succeeded after creating the set.

  • RPC FAILURE: For stress test

    I am working with Sun Rpc for providing the client server interface in my project. I have observed that during stress testing after approx 3 hour client start taking a lot of time to process and give back the result. Although server side time stamp is still in microseconds, whereas client side gone in secs.Do any body face such problem previously if yes please let me know the solution.

    Hi Tim.
    Did you figure this problem out?
    I'm having some kind of the same problem.
    And is curious about how you solved it.

  • RPC FAILURE: Due to Client Side processing

    I am working with Sun Rpc for providing the client server interface in my project. I have observed that during stress testing after approx 3 hour client start taking a lot of time to process and give back the result. Although server side time stamp is still in microseconds, whereas client side gone in secs.Do any body face such problem previously if yes please let me know the solution.

    This forum is for discussion of programming in C++, particularly using Sun C++ compilers.
    You are more likely to find help for your question in a Solaris forum -- I suggest the "kernel" forum.

  • Server 2003 VPN clients can't verify username and password

    Hi,
    Hoping someone can help or point me in the right direction. I have a Windows Server 2003 R2 standard SP2 running RRAS. It has Dual NIC's and is configured for PPTP VPN. I am using a BT Business Hub 5 for internet access and using the BT Static IP service.
    The BT Hub assigns the static IP address chosen to the Server using DHCP. The firewall is configured to port forward PPTP traffic to the 2003 server. This all works correctly.
    The 2003 server is on a domain where the DC is a 2008 R2 server. The DC also acts as the DNS and DHCP for the network.
    The default gateway for the domain is pointed towards our WinGate proxy server which also acts as a DNS server.
    The 2003 server LAN NIC is configured manually, usually I would not configure a deafult gateway on the LAN NIC as the WAN NIC needs the default gateway for the BT Hub.
    The problem I am having is if a default gateway is configured on the LAN NIC, I can connect to the VPN and it will logon to the network. Once connected everything works ok. If the connection drops, when trying to reconnect the client can no longer verify
    the user name and password against the domain and the connection is refused.
    If I do not have a default gateway configured in the LAN NIC the VPN clients can not verify the username and password for the domain at all and I get RPC failure errors in the event viewer with the source dnsapi.
    Once this error occurs the only way I can get the clients to reconnect is to disable the WAN NIC, restart the RRAS service and enable the WAN NIC again.
    Any insight will be much appreciated.

    Hello,
    for Networking configuration questions better ask in
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/home#forum=winserverNIS&filter=alltypes&sort=lastpostdesc&content=Search
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://blogs.msmvps.com/MWeber
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    Twitter:  

  • Authentication role on Windows Satellite not working

    Hi,
    I've configured my satellite servers with the content, imaging and
    authentication role. After
    analyzing traffic between the several sites, all workstations were
    communicating directly with the primary server.
    The client logs on the remote site all show :
    [DEBUG] [04/23/2011 09:17:55.125] [1032] [ZenworksWindowsService] [129] []
    [CommonCasa] [] [ Host: wsuszwl:2645] [] []
    [DEBUG] [04/23/2011 09:17:55.125] [1032] [ZenworksWindowsService] [129] []
    [CommonCasa] [] [ ServiceName: com.novell.zenworks.TMS_TREE] [] []
    [DEBUG] [04/23/2011 09:17:56.000] [1032] [ZenworksWindowsService] [127] []
    [SessionManager] [] [SessionLogonThread signaling TESS event: UserLogin] []
    [DEBUG] [04/23/2011 09:17:56.000] [1032] [ZenworksWindowsService] [127]
    [adminzwl] [SessionManager] [] [OnChange performing change event for session
    396680129, with event: UserLogin] [] []
    [DEBUG] [04/23/2011 09:17:56.000] [1032] [ZenworksWindowsService] [127] []
    [Novell.Zenworks.Tess] [] [EventManager -- EventTrigger for UserLogin has
    been called.] [] []
    [DEBUG] [04/23/2011 09:17:56.000] [1032] [ZenworksWindowsService] [127] []
    [Novell.Zenworks.Tess] [] [EventManager -- EventTrigger for UserLogin has
    been called.] [] []
    [DEBUG] [04/23/2011 09:17:56.000] [1032] [ZenworksWindowsService] [127]
    [adminzwl] [SessionManager] [] [OnChange finished performing change event
    for session 396680129, with event: UserLogin] [] []
    [DEBUG] [04/23/2011 09:17:56.000] [1032] [ZenworksWindowsService] [127] []
    [SessionManager] [] [SessionLogonThread finished signaling TESS event:
    UserLogin] [] []
    [DEBUG] [04/23/2011 09:17:56.140] [1032] [ZenworksWindowsService] [129] []
    [CommonCasa] [] [ObtainAuthToken took exception: -939589602
    System.Exception: -939589602
    at Novell.Casa.Client.Auth.Authtoken.ObtainAuthToken( String sService,
    String sHost, WinLuid luid)
    wsuszwl is the satellite, running Windows 2003 server, ZEN 10.3.3 and WSUS.
    WSUS default port has been changed to 8530. After this exception -939589602
    , the client authenticates to the primary server, correctly following the
    nearest server rules.
    I checked if something was listening on port 2645 on the satellite and it
    was not. On the primary server port 2645 is listening, checked via
    https://server:2645/CasaAuthTokenSvc/
    I've enabled Casa logging on the satellite, below a few lines from that log.
    Am I missing something here? I'm confused, because while configuring the
    authentication role of the satellite, ZCM tells you it's using port 443 for
    authentication. But it seems it's using port 2645?
    And I can't find any ZEN service not running on the satellite. The ZEN
    agent on the satellite shows under Satellite Role Status : Authentication
    Enabling. As if it's trying to enbele the roles, but it's not succeeding.
    I found some stuff while googlng that told me it would not be possible to
    use the authentication role on Windows bases satellites, only on linux
    based. But that was a pretty old article.
    Thanks for any help
    Ron
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenEx- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenInt- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenInt- ServiceName =
    com.novell.zenworks.TMS_TREE
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenInt- HostName =
    wsuszwl:443
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenInt- BufferLength = 0
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenEntryInCache- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenCacheEntry- Key =
    com.novell.zenworks.TMS_TREE@wsuszwl
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenCacheEntry- Keysize = 37
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenCacheEntry-
    CredStoreScope = 16266C0
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenEntryInCache- End,
    pEntry = 0x0
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenFromServer- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenFromServer- Hostname =
    wsuszwl
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenFromServer- port = 443
    [1668-1BB4] [09:15:58] CASA_AuthToken -OpenRpcSession- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -OpenRpcSession- Host = wsuszwl
    [1668-1BB4] [09:15:58] CASA_AuthToken -OpenRpcSession- HostPort = 443
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyMultiToWideAlloc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyMultiToWideAlloc- End, retStatus
    = 00000000
    [1668-1BB4] [09:15:58] CASA_AuthToken -OpenRpcSession- End, pSession =
    05F94F98
    [1668-1BB4] [09:15:58] CASA_AuthToken -BuildGetAuthPolicyMsg- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -BuildGetAuthPolicyMsg- End, pMsg =
    0x5F94FB0
    [1668-1BB4] [09:15:58] CASA_AuthToken -Rpc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -InternalRpc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyMultiToWideAlloc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyMultiToWideAlloc- End, retStatus
    = 00000000
    [1668-1BB4] [09:15:58] CASA_AuthToken -InternalRpc- before
    WinHttpOpenRequest
    [1668-1BB4] [09:15:58] CASA_AuthToken -InvalidCertsFromHostAllowed- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -InvalidCertsFromHostAllowed- End,
    retStatus = 0
    [1668-1BB4] [09:15:58] CASA_AuthToken -SecureFailureStatusCallback- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -SecureFailureStatusCallback- End
    [1668-1BB4] [09:15:58] CASA_AuthToken -InternalRpc- Secure connection
    failure, flags = 10
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyWideToMultiAlloc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyWideToMultiAlloc- End, retStatus
    = 00000000
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyWideToMultiAlloc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyWideToMultiAlloc- End, retStatus
    = 00000000
    [1668-1BB4] [09:15:58] CASA_AuthToken -UserApprovedCert- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -UserApprovedCert- Invalid Cert from
    Host = wsuszwl
    [1668-1BB4] [09:15:58] CASA_AuthToken -InternalRpc- User approved invalid
    certificate from wsuszwl
    [1668-1BB4] [09:15:58] CASA_AuthToken -AllowInvalidCertsFromHost- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -AllowInvalidCertsFromHost-
    X509_ASN_ENCODING
    [1668-1BB4] [09:15:58] CASA_AuthToken -AllowInvalidCertsFromHost- Entered to
    iterate the cert list
    [1668-1BB4] [09:15:58] CASA_AuthToken -AllowInvalidCertsFromHost- End,
    retStatus = 0
    [1668-1BB4] [09:15:58] CASA_AuthToken -InternalRpc- End, retStatus = 0
    [1668-1BB4] [09:15:58] CASA_AuthToken -Rpc- End, retStatus = 0
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenFromServer- Did not
    receive GetAuthPolicy Response data
    [1668-1BB4] [09:15:58] CASA_AuthToken -CloseRpcSession- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -CloseRpcSession- End
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenFromServer- End,
    retStatus = C7FF0020
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenInt- End, retStatus =
    C7FF0020
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenEx- End, retStatus =
    C7FF0020
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenEx- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenInt- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenInt- ServiceName =
    com.novell.zenworks.TMS_TREE
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenInt- HostName =
    wsuszwl:2645
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenInt- BufferLength = 0
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenEntryInCache- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenCacheEntry- Key =
    com.novell.zenworks.TMS_TREE@wsuszwl
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenCacheEntry- Keysize = 37
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenCacheEntry-
    CredStoreScope = 162DAF4
    [1668-1BB4] [09:15:58] CASA_AuthToken -FindAuthTokenEntryInCache- End,
    pEntry = 0x0
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenFromServer- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenFromServer- Hostname =
    wsuszwl
    [1668-1BB4] [09:15:58] CASA_AuthToken -ObtainAuthTokenFromServer- port =
    2645
    [1668-1BB4] [09:15:58] CASA_AuthToken -OpenRpcSession- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -OpenRpcSession- Host = wsuszwl
    [1668-1BB4] [09:15:58] CASA_AuthToken -OpenRpcSession- HostPort = 2645
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyMultiToWideAlloc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyMultiToWideAlloc- End, retStatus
    = 00000000
    [1668-1BB4] [09:15:58] CASA_AuthToken -OpenRpcSession- End, pSession =
    05F94F98
    [1668-1BB4] [09:15:58] CASA_AuthToken -BuildGetAuthPolicyMsg- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -BuildGetAuthPolicyMsg- End, pMsg =
    0x5F94FB0
    [1668-1BB4] [09:15:58] CASA_AuthToken -Rpc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -InternalRpc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyMultiToWideAlloc- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -CopyMultiToWideAlloc- End, retStatus
    = 00000000
    [1668-1BB4] [09:15:58] CASA_AuthToken -InternalRpc- before
    WinHttpOpenRequest
    [1668-1BB4] [09:15:58] CASA_AuthToken -InvalidCertsFromHostAllowed- Start
    [1668-1BB4] [09:15:58] CASA_AuthToken -InvalidCertsFromHostAllowed- End,
    retStatus = 0
    [1668-1BB4] [09:15:59] CASA_AuthToken -InternalRpc- Unable to connect to
    server
    [1668-1BB4] [09:15:59] CASA_AuthToken -InternalRpc- End, retStatus =
    C7FF001E
    [1668-1BB4] [09:15:59] CASA_AuthToken -Rpc- End, retStatus = C7FF001E
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenFromServer-
    GetAuthPolicy Rpc failure, error = C7FF001E
    [1668-1BB4] [09:15:59] CASA_AuthToken -CloseRpcSession- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -CloseRpcSession- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenFromServer- End,
    retStatus = C7FF001E
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenInt- End, retStatus =
    C7FF001E
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenEx- End, retStatus =
    C7FF001E
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenEx- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenInt- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenInt- ServiceName =
    com.novell.zenworks.TMS_TREE
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenInt- HostName =
    zentms1.tmsnet.org:443
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenInt- BufferLength = 0
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindAuthTokenEntryInCache- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindAuthTokenCacheEntry- Key =
    [email protected]
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindAuthTokenCacheEntry- Keysize = 48
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindAuthTokenCacheEntry-
    CredStoreScope = 1638FD4
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindAuthTokenEntryInCache- End,
    pEntry = 0x0
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenFromServer- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenFromServer- Hostname =
    zentms1.tmsnet.org
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainAuthTokenFromServer- port = 443
    [1668-1BB4] [09:15:59] CASA_AuthToken -OpenRpcSession- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -OpenRpcSession- Host =
    zentms1.tmsnet.org
    [1668-1BB4] [09:15:59] CASA_AuthToken -OpenRpcSession- HostPort = 443
    [1668-1BB4] [09:15:59] CASA_AuthToken -CopyMultiToWideAlloc- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -CopyMultiToWideAlloc- End, retStatus
    = 00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -OpenRpcSession- End, pSession =
    05F94ED8
    [1668-1BB4] [09:15:59] CASA_AuthToken -BuildGetAuthPolicyMsg- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -BuildGetAuthPolicyMsg- End, pMsg =
    0x5F94FB0
    [1668-1BB4] [09:15:59] CASA_AuthToken -Rpc- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -InternalRpc- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -CopyMultiToWideAlloc- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -CopyMultiToWideAlloc- End, retStatus
    = 00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -InternalRpc- before
    WinHttpOpenRequest
    [1668-1BB4] [09:15:59] CASA_AuthToken -InvalidCertsFromHostAllowed- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -InvalidCertsFromHostAllowed- End,
    retStatus = 0
    [1668-1BB4] [09:15:59] CASA_AuthToken -InternalRpc- End, retStatus = 0
    [1668-1BB4] [09:15:59] CASA_AuthToken -Rpc- End, retStatus = 0
    [1668-1BB4] [09:15:59] CASA_AuthToken -CreateGetAuthPolicyResp- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespStartElementHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespStartElementHandler-
    End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespStartElementHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespStartElementHandler-
    End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespStartElementHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespStartElementHandler-
    End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespEndElementHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespEndElementHandler-
    End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- End, retStatus =
    00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespEndElementHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespEndElementHandler-
    End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespStartElementHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespStartElementHandler-
    End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- End, retStatus =
    00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespEndElementHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespEndElementHandler-
    End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespEndElementHandler-
    Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthPolicyRespEndElementHandler-
    End
    [1668-1BB4] [09:15:59] CASA_AuthToken -CreateGetAuthPolicyResp- End,
    retStatus = 00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -CreateAuthPolicy- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -DecodeData- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -DecodeData- End, retStatus = 0
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- End, retStatus =
    00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- End, retStatus =
    00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyStartElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConsumeElementData- End, retStatus =
    00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyCharDataHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -AuthPolicyEndElementHandler- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -CreateAuthPolicy- End, retStatus =
    00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -ObtainSessionToken- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenEntryInCache- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenCacheEntry- Key =
    TMS_TREE
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenCacheEntry- Keysize =
    9
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenCacheEntry-
    CredStoreScope = 1638FD4
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenEntryInCache- End,
    pEntry = 0x0
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenEntryInCache- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenCacheEntry- Key =
    TMS_TREE
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenCacheEntry- Keysize =
    9
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenCacheEntry-
    CredStoreScope = 1638FD4
    [1668-1BB4] [09:15:59] CASA_AuthToken -FindSessionTokenEntryInCache- End,
    pEntry = 0x0
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthMechToken- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthTokenIf- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetConfigInterface- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetConfigInterface- End, retStatus =
    00000000
    [1668-1BB4] [09:15:59] CASA_PwdMech -AuthTokenIf_AddReference- Start
    [1668-1BB4] [09:15:59] CASA_PwdMech -AuthTokenIf_AddReference- End, refCount
    = 2
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConfigIf_ReleaseReference- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -ConfigIf_ReleaseReference- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthTokenIf- End, retStatus =
    00000000
    [1668-1BB4] [09:15:59] CASA_PwdMech -AuthTokenIf_GetAuthToken- Start
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- Start
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- Realm = TMS_TREE
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- CredStoreScope =
    1638FD4
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- RealmCredsOnly = 1
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- Username =
    Administrator
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- End, retStatus = 0
    [1668-1BB4] [09:15:59] CASA_PwdMech -EncodeData- Start
    [1668-1BB4] [09:15:59] CASA_PwdMech -EncodeData- End, retStatus = 0
    [1668-1BB4] [09:15:59] CASA_PwdMech -AuthTokenIf_GetAuthToken- End,
    retStatus = C7FD0006
    [1668-1BB4] [09:15:59] CASA_PwdMech -AuthTokenIf_GetAuthToken- Start
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- Start
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- Realm = TMS_TREE
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- CredStoreScope =
    1638FD4
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- RealmCredsOnly = 1
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- Username =
    Administrator
    [1668-1BB4] [09:15:59] CASA_PwdMech -GetUserCredentials- End, retStatus = 0
    [1668-1BB4] [09:15:59] CASA_PwdMech -EncodeData- Start
    [1668-1BB4] [09:15:59] CASA_PwdMech -EncodeData- End, retStatus = 0
    [1668-1BB4] [09:15:59] CASA_PwdMech -AuthTokenIf_GetAuthToken- End,
    retStatus = 00000000
    [1668-1BB4] [09:15:59] CASA_PwdMech -AuthTokenIf_ReleaseReference- Start
    [1668-1BB4] [09:15:59] CASA_PwdMech -AuthTokenIf_ReleaseReference- End
    [1668-1BB4] [09:15:59] CASA_AuthToken -GetAuthMechToken- End, retStatus =
    00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -BuildAuthenticateMsg- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -BuildAuthenticateMsg- End, pMsg =
    0x5F95DE8
    [1668-1BB4] [09:15:59] CASA_AuthToken -Rpc- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -InternalRpc- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -CopyMultiToWideAlloc- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -CopyMultiToWideAlloc- End, retStatus
    = 00000000
    [1668-1BB4] [09:15:59] CASA_AuthToken -InternalRpc- before
    WinHttpOpenRequest
    [1668-1BB4] [09:15:59] CASA_AuthToken -InvalidCertsFromHostAllowed- Start
    [1668-1BB4] [09:15:59] CASA_AuthToken -InvalidCertsFromHostAllowed- End,
    retStatus = 0
    [1668-1BB4] [09:15:59] CASA_AuthToken -InternalRpc- End, retStatus = 0

    Rvd,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://forums.novell.com/

  • Outlook Anywhere is not working

    Hello all,
    I have Exchange 2007 SP3 running.  I have enabled Outllook anywhere.  I have yet to be able to get it to work.  I have been told the only port I need open is 443.  when I go to setup my clients, I do a manual configuration.  for
    the server I enter my internal server name ( I have been told this is how its to be setup), then I go specify the outside URL for the proxy.  I have RPC over HTTP Proxy installed on the server, but when I run Microsoft's test I get the following
    RPC over HTTP Connectivity failed.   This is running on a Server 2008 64-bit machine. 
    Any pointers on what to check would be very helpful.  I have quite a few people that would like to use this, but it fails connecting at the last step in the Outlook setup due to the RPC failure.
    edit-  I also opened my firewall wide open to make sure that wasn't blocking it, and with all ports open it still failed. 
    Thanks
    David

    Hi David,
    Thank you for your question.
     We could disable IPv6 on Exchange server which install on Window server 2008 to check if the issue persist.
    If the issue persist, we could refer to the following steps to reinstall RPC-over-http:
    Disable outlook anywhere using the Exchange Management Console
    Remove RPC proxy component using PowerShell servermanagercmd -r rpc-over-http-proxy
    Reboot the server
    Install RPC proxy component using PowerShell servermanagercmd -i rpc-over-http-proxy
    Enable outlook anywhere using the Exchange Management Console
    Restart the Microsoft Active Directory Topology Service
    Try the test again
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    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]
    Jim Xu
    TechNet Community Support

  • Spotlight on Xsan gone beserk

    Anyone ever seen spotlight indexing errors on Xsan 2? Xsan Admin was hanging badly when trying to index the Xsan volume. It's just a theory at this points, but spotlight seems to hate files from Unix or Windows, especially files which are unique on those filesystems but not on Mac OS X.
    Some of the errors which makes me think it's spotlight related:
    MDSChannelPeerRequest: (ipc/mig) server raised exception com.apple.metadata.mds[62]
    XSANFSFSCTLSpotlightRPC fsctl failed (errno = 45)ERROR: _MDSChannelInitForXsan: _XsanCreateMDSChannel failed: 45
    com.apple.metadata.mds[62]
    ERROR: _MDSChannelXsanFetchAccessTokenForUID: dead channel
    mds[62]
    (Error) Message: MDSChannel RPC failure (fetchPropertiesForContext:) [no channelAccessToken]

    Same here. Turned of Spotlight indexing on the three filesystems, but errors still comming identical to yours
    Probably not related, but who knows, also have loads of Console Log Entries (in the All Messages bit of console) that state...
    xsand Automount: volume options are not a dictionary
    This I think comes from the automount.plist file that has a field marked...
    <key>MountOptions</key>
    and I suspect the MountOptions bit needs to be swapped for something else, but I have no idea what.

  • OD with errors, not displaying my users

    Yesterday the OD Slave was having issues and now today the Master OD is having the same issues.
    When launching Workgroup Manager I get this error message (which isn't well documented here on the interwebs):
    "Error of type eDSOperationFailed (-14483) on line 3395 of /SourceCache/WorkgroupManager/WorkgroupManager-361.3.1/PMMUGMainView.mm"
    I try to follow the path in the error message and there is no /SourceCache directory that I can find.
    Console Messages is giving me this group of error messages over and over every couple of seconds.
    9/1/11 12:18:55 PM          com.apple.metadata.mds[68]          XSANFS_FSCTL_SpotlightRPC fsctl failed (errno = 45)ERROR: _MDSChannelInitForXsan: _XsanCreateMDSChannel failed: 45
    9/1/11 12:18:55 PM          com.apple.metadata.mds[68]          ERROR: _MDSChannelXsanFetchAccessTokenForUID: dead channel
    9/1/11 12:18:55 PM          mds[68]          (Error) Message: MDSChannel RPC failure (fetchPropertiesForContext:) [no channelAccessToken]
    9/1/11 12:18:55 PM          mds[68]          (Error) Store: <MDSDistantStore 0x102905760 shutdown:NO got shutdown notification:NO>{channel:0x102904bf0 localPath:'/Volumes/Media'} bring up failed -- will retry
    2 days ago we had a network switch failure that I am wondering could be the root cause, but I don't have any clue.
    If anyone knows what is going on with my system your insight would be greatly appreciated.

    I have just come across this error as well
    "Error of type eDSOperationFailed (-14483) on line 3395 of /SourceCache/WorkgroupManager/WorkgroupManager-361.3.1/PMMUGMainView.mm"
    Funnily enough though WGM works fine if I lauch it imediately after boot. Seems that if server admin is launched before WGM the issue occurs...
    This has literally just begun so sorry for no technical input yet as I have jsut begun troubleshooting myself, have you managed to discover anything since first coming across the problem?

  • Can anyone verify this console error?

    When I mount my airdisk in 10.5.2, I get this error everytime in the console:
    Mar 14 17:38:23 Ryan mds[21]: (Error) Message: MDSChannel RPC failure (fetchPropertiesForContext:)
    Mar 14 17:38:23 Ryan mds[21]: (Error) Store: <MDSDistantStore: 0x364810>{channel:0x35fd40 localPath:'/Volumes/Storage'} bring up failed -- will retry
    The airdisk works fine and at great speed. I just want to know if it is normal or not. Thanks.

    Check out this thread: http://discussions.apple.com/thread.jspa?messageID=6853786
    The error relates to the failure of spotlight to index/search Airdisk volumes. It means that performing searches on Airdisk volumes will always fail to return any results.
    A workaround is to mount your Airdisks using SMB but this renders the normally useful Airdisk Utility redundant. Also, I find that SMB doesn't handle unicode characters as well as AFP does.
    I think there are 2 problems here. There is a problem with the AFP implementation used on the AEBSn, if there weren't then Time Machine would be supported. Then there is a problem with the mds daemon, rather than fail, it should degrade and allow non-indexed search to problem.
    Message was edited by: ctomer

  • VM deployment fails - blocked job using WAP deployment

    I am new so sorry if I am missing something very obvious.
    I am testing WAP and SCVMM 2012 R2. I created a public plan and deployed VMs. The last VM did not deploy successfully. I am assuming it was because for a time frame the VMM Library was not accessible (RPC failure). The VM deployment stayed at 75% (customizing
    VM) and after 2 hours at the same Level i canceled the Job. (For Information: by then the VMM Library was available again).
    I started a new Job but all new Jobs using the same WAP plan and VM template receive error 2606 "unable to perform the Job because one or more of the selected objects are locked by another Job". Now I am assuming the error is the previously cancled
    Job but I am not sure.
    As shown in KB 2795040 I tried to see the blocking Job. Problem is TaskID. I don't have it. I checked on the Jobs view in SCVMM but it doesn't Show a Task ID for the Job I canceled. I looked in the VirtualMachine Manager DB table for Task trails to find
    which Jobs failed in order to find the Task ID. But at the time I canceled the Job I didn't find any corresponding Jobs. I looked at the time stamp when the VM deployment started but the Task ID I found there was not present in the tbl_VMM_Lock.
    How do I find the corresponding TaskID to the Job that is blocking the deployment Jobs?

    I was just able to get it working on mine on a VMMR2 Cluster (hyper-v on 2012 and 2012 R2 hosts with the same success) and the Service Template using a VM template with Server 2008R2 Enterprise.  I don't know if you did the same steps but:
    created a fresh VM in VMM - install Virtual Guest Services.
    convert that VM to a VM Template - VMM then copies the VM files to a location on your VMM Library.
    create Service template using the new VM template - with no services.
    I've had problems in the past with trying to convert a VM to a template, and the VM would fail at the 'Fix up differencing disks' ..  It wasn't until I did a fresh install instead of trying to convert a VM copy of a copy of a copy of a V2V migration.. 
    Mine completes successfully but with an error couldn't install Virtual Guest Services when they are already installed.  hmmm..  The VM/Service is running fine however.
    ---------------------------- Error I got -------------------------------
    Error (13233)
    Unable to install Virtual Guest Services on virtual machine TEST_SERVICE. The Hyper-V Integration Services setup exited with error code 60001.
    Recommended Action
    For more information, refer to the Hyper-V documentation for virtual machine integration services at
    http://go.microsoft.com/fwlink/?LinkId=118036 and then try the operation again.

  • KDE Konqueror NFS Problem

    Hello,
    i have NFS up and running,
    if i mount it per hand all is functionally,
    i can copy files between all shares only
    in konqueror 3.2 or 3.3 i can only read files from
    the nfs shares if i going to write a file i get
    an rpc failure ??
    i only found these in the kernel log:
    kernel: RPC: bad TCP reclen 0x00000f9c (non-terminal)
    in konquereo it works also if i mount the nfs share by hand or fstab.
    can anyone help me
    regards
    albert

    Hello,
    i have NFS up and running,
    if i mount it per hand all is functionally,
    i can copy files between all shares only
    in konqueror 3.2 or 3.3 i can only read files from
    the nfs shares if i going to write a file i get
    an rpc failure ??
    i only found these in the kernel log:
    kernel: RPC: bad TCP reclen 0x00000f9c (non-terminal)
    in konquereo it works also if i mount the nfs share by hand or fstab.
    can anyone help me
    regards
    albert

  • Can ANYBODY use spotlight search on an Airport Disk?

    Seriously does this work for anybody?

    felix2006 wrote:
    Seriously does this work for anybody?
    I've tried several things:
    mdutil -sv /Volumes/paul
    /Volumes/paul:
    No index.
    sudo mdutil -i on /Volumes/paul
    /Volumes/paul:
    Error: unable to perform operation. (-103)
    No index.
    So that doesn't work. If you check Console.app, you will see that the mds process repeated attempts to setup indexing:
    11/03/2008 18:09:55 mds[36] (Error) Message: MDSChannel RPC failure (fetchPropertiesForContext:)
    11/03/2008 18:09:55 mds[36] (Error) Store: <MDSDistantStore: 0x3da2b0>{channel:0x397670 localPath:'/Volumes/paul'} bring up failed -- will retry
    I've no idea why it's failing.
    Message was edited by: ctomer
    Message was edited by: ctomer

  • Catching SOAPException at Java Client

    We have a 3 tier application where in Front End is in Java , Middle layer is in SOAP deployed using Systinet Server for c++ and backend is in DCE( Distributed Computing Environment ) .
    We are calling DCE specific RPC through a SOAP Services, now when a specific DCERPC fails, SOAP Server binary crashes and on Front end Java , only Temporary delays error message gets displayed.
    SOAP Java Client code files are generated using WSDL , now at SOAPServer CPP exception is written using inbuilt Systinet Exception handling mechanism
    and the same has to be caught at the Java side.
    In CPP side , the code for Trims
         if (ret_status != rpc_s_ok) {
              dce_ret = 0;
         WASP_GenericFaultException * gen_exc = new WASP_GenericFaultException("DCE ERROR - calling WF_ListWuClnt() RPC");
              WASP_VString reason = "RPC Failure, return status = " + ret_status;
    gen_exc->setReason(reason, "en");
    throw gen_exc;
    Now for Java Client , we have written a custom exception class as below
    public class TrimsCustomException extends javax.xml.soap.SOAPException
         public String msgId;
         public     String msgText;
         public TrimsCustomException()
                   //Default Constructor
         public TrimsCustomException(String Id,String Txt)
                   this.msgId=Id;
                   this.msgText=Txt;
         public String getMsgId()
                   return msgId;
         public String getMessage()
                   return msgText;
    Still is there any better way to catch the exception ?

    here is the following code :
         public byte[] marshall()
              StringBuffer payload = new StringBuffer("<?xml version=\'1.0\' encoding=\'UTF-8\'?>");
              payload.append("<soap:Envelope xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:soap=\"http://schemas.xmlsoap.org/soap/envelope/\">");
              payload.append("<soap:Body>");
              payload.append("<Bonjour xmlns=\"http://tempuri.org/\">");
              payload.append("<strName>elise</strName>");
              payload.append("</Bonjour>");
              payload.append("</soap:Body>");
              payload.append("</soap:Envelope>\r\n");
              System.out.println(payload.toString());
              return payload.toString().getBytes();
    AND FOR THE CONNECTION :
    URL endpoint = new URL("http://biztalk:8080/PCS_Integration/SynchronizeProfiles.asmx");
              URLConnection con = endpoint.openConnection ();
              con.setDoInput (true);
              con.setDoOutput (true);
              con.setUseCaches (false);
              con.setAllowUserInteraction(false);
              con.setRequestProperty ("Content-Length", Integer.toString (request.length));
              con.setRequestProperty ("Content-Type", "text/xml; charset=utf-8");
              con.setRequestProperty ("SOAPAction", "\"http://tempuri.org/WS_UpdateProfileAgency\"");
              OutputStream out = con.getOutputStream ();
              out.write (request);
              out.flush ();
              out.close();
                   InputStream in = con.getInputStream();
    //then parse the xml result
    hope it can help you

  • Spotlight gone mad

    Help !
    MDS XSan 2.2 10.6.1
    Client XSan 2.2 10.6.1
    I have 1 CLient that continuously reports the following errors
    "com.apple.metadata.mds: XSANFSFSCTLSpotlightRPC
    com.apple.metadata.mds[67]: XSANFSFSCTLSpotlightRPC fsctl failed (errno = 45)ERROR: _MDSChannelInitForXsan: _XsanCreateMDSChannel
    mds[67]: (Error) Message: MDSChannel RPC failure (fetchPropertiesForContext:) [no channelAccessToken] "
    I sow an archived message on a post that it was related to foreign files, but there was not explanation to why this was happening ...
    Any thought ???
    Message was edited by: Anthony G Palermo
    Message was edited by: Anthony G Palermo

    Hi Jerry.
    This does seem to be a widespread problem, and putting your root in the Privacy Pane as you have done is the only fix I've found so far:
    http://discussions.apple.com/message.jspa?messageID=10074229#10074229

Maybe you are looking for

  • Receiver JDBC Adapter for Count of records in Table

    Hi All, I am talking about Client Proxy to Receiver JDBC scenario.I've a requirement where i need to count the no of records created or updated in SQL server for particular transaction date.Question is- Is it possible to execute normal sql query to g

  • Using HLEVEL with multiple hierarchies

    Hi all, Is there a way to pass a parameter to the HLEVEL keyword to specifiy which hierarchy (Parent H1,H2, H3, etc.) to use when pulling the HLEVEL? We would like to use HLEVEL for report formatting however we need the ability to choose the hiearchy

  • Hyperion Performace Scorecard

    Is there a sub-forum for HPS? I have one simple question for Performance Scorecard. How to change the trend indicator? I know the performance indicator can be add or edit in the object view, performance indicator list. But for the trend indicator, an

  • Windows Vista 32-bit recovery

    Okay, so the computer was reset to factory specs 3 days ago because I believe the DVD player crapped out on me, I went into "safe mode" and disabled it and was able to use computer fine, started up fine.  After Windows ran all automatic updates (3 ho

  • PS creating Operative Network from standard and need to copy user fields

    Hello All, has anyone tried to create Opertive Network(cn21) with reference to a Standard network. what we need to do is from the first line line item copy 3 user defined fields from the User Fields tab on the Standard Network to the header of the Op