System Management Bus - error

I have MSI845PE MAX and WXP Home edition. In Device Manager ->Other  devices is exclamation mark  in System Management Bus. What I have do corect this problem. Thanx

Did you try to Disable, and then Renable the device by double clicking on it in Device Manager?..........Sean REILLY875

Similar Messages

  • OnCommand System Manager recieves error 500

    Good day, i am running OnCommand System Manager ver 3.1.1 on Windows. Today, for the very first time, i have seen this issue: i can connect to my 3210 running DataONTAP 8.0.3P2 7-mode, but when i try to reach my new 2240 running DataONTAP 8.1.3P3 7-mode i recieve an error 500 "connection refused". I have found this workaround: on the 2240s i have issued the command >options httpd.admin.enable on ;after this the OnCommand System Manager probably still tries a secure connection, on the console i see errors like [hostname: HTTPPool03:warning]: HTTP XML Authentication failed from MyClientIP .  But now i guess OnCommand System Manager falls back to a non secure connection, i see the question "do you want to set up a secure connection or continue without...", i answer "continue without" and i'm able to manage my filers again. What's happened? Maybe something java updates related? Thanks in advance.
    Alessandro  

    While removing newer version of Java and installing older versions probably fixes this in most cases, do you really want to run version of software that have known vulnerabilities in them? I think that companies like NETAPP, EMC, DELL, HP, etc, etc., need to be accountable for staying current.  They need to upgrade the applications regularly to stay compatible with the platforms they develop in.  The days of write it once and forget it are long gone.  The threat vectors have changed and continue to change on a daily basis. If I had machine that was dedicated to doing nothing other managing storage, network and servers, that never saw any portion of the production network and was isolated 100% from the internet, perhaps leaving archaic versions of depreciated software out there would be an option.  The days of doing business this way are also long gone. Cannot speak for everyone of course, but I don’t have the real-estate on my desk and have no desire to run up down the hall to my MDF every time I want to manage something in the environment.   

  • Nvidia Pci system Managment controllers error!!!

    In The " system Administrator " of Win XP, appears this dispositive " Nvidia Pci bus system managment " when acces at propertis of them appears " This dispositive nos hace controllers installed ". Anywhere in the list of dispositives appear as valid. What is the problem? Thanks.

    There is NO problem .
    Many devices don't have spesific drivers . Still they need allocated mem/io range and to register in the pci enumeration
    and bus system with vendor id class id and div. other registry settings .
    Look through device manager , expand all + for all groups , if you have no devices with yellow "question mark" all is okay .

  • PCI System Management Bus

    I am running Windows 98SE.  I have everything up and working, except for one little thing.  The PCI Management Bus does not have a drive.  My Windows disk has no drivers for it, and have no found anything online.  Any and all help is welcome and appreciative.

    Sorry, I was typing fast and that just slipped my mind.  I'm running RS482M4-ILD board.  I actually decided to read forum rules and put my specs in my signature, just like it suggests.  Sorry for wasting your time like that.  I'll make sure to proofread my posts from now on and make sure I put in all the information

  • ERROR MESSAGE sap system manager:work process restarted, session terminated

    Hi,
    i am a beginer in SAP administration, users are getting this error message and i have done all my research and not able to resolve this issue. Here are the details
    SAP Version :ideas 4.7
    Database :Oracle
    OS : windows 2003
    Module user is working on MM
    user working on it is a Super user with all the permissions
    SAP is configure to run under the  European date and decimal format.
    I have never done any database administration on it, it is a new install and has been rarely used.
    User creates a RFQ and when he tries saving it , seems like for the first time after either restarting the macine or restarting the service it might work and at time it might not, this is a very sporadic error and most of the times it crashes out with the message "sap system manager:work process restarted, session terminated" and kicks the user out of the session.
    Below are the details of the error message from ST22 :
    name of the runtime error : system_core_dumped
    below are the details of the error message and its resoltion as suggested by sap help :
    ========
    Runtime Errors         SYSTEM_CORE_DUMPED           
           Occurred on     01.02.2008 at 07:52:19
    Process terminated by signal " ".                                             
    What happened?
    The current ABAP program had to be terminated because the                     
    ABAP processor detected an internal system error.                             
    The current ABAP program "SAPLCLSC" had to be terminated because the ABAP     
    processor discovered an invalid system state.                                 
    What can you do?
                                                                                    Make a note of the actions and input which caused the error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                                                               
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer      
    termination messages, especially those beyond their normal deletion           
    date.                                                                               
    Error analysis
    An SAP System process was terminated by an operating system signal.           
                                                                                    Possible reasons for this are:                                                
    1. Internal SAP System error.                                                 
    2. Process was terminated externally (by the system administrator).           
               Last error logged in SAP kernel                                    
                                                                                    Component............ "Taskhandler"                                           
    Place................ "SAP-Server server1_DEV_00 on host server1 (wp 1)"      
    Version.............. 1                                                       
    Error code........... 11                                                      
    Error text........... "ThSigHandler: signal"                                  
    Description.......... " "                                                     
    System call.......... " "                                                     
    Module............... "thxxhead.c"                                            
    Line................. 9555                                                                               
    How to correct the error
    The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often             
    contains a file called 'core'.                                                                               
    Save this file under another name.                                                                               
    If you cannot solve the problem yourself, please send the                     
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                  
       To obtain this, select the "Print" function on the current screen.         
                                                                                    2. A suitable hardcopy prinout of the system log.                             
       To obtain this, call the system log with Transaction SM21                  
       and select the "Print" function to print out the relevant                  
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,            
       supply the source code.                                                    
       To do this, you can either use the "PRINT" command in the editor or        
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred            
       or which actions and input led to the error.                                                                               
    System environment
    SAP Release.............. " "                                                                               
    Application server....... " "                                                 
    Network address.......... " "                                                 
    Operating system......... " "                                                 
    Release.................. " "                                                 
    Hardware type............ " "                                                 
    Character length......... " " Bits                                            
    Pointer length........... " " Bits                                            
    Work process number...... " "                                                 
    Short dump setting....... " "                                                                               
    Database server.......... " "                                                 
    Database type............ " "                                                 
    Database name............ " "                                                 
    Database owner........... " "                                                                               
    Character set............ " "                                                                               
    SAP kernel............... " "                                                 
    Created on............... " "                                                 
    Created in............... " "                                                 
    Database version......... " "                                                                               
    Patch level.............. " "                                                 
    Patch text............... " "                                                                               
    Supported environment....                                                     
    Database................. " "                                                 
    SAP database version..... " "                                                 
    Operating system......... " "                                                 
    User, transaction...
    Client.............. " "                                                      
    User................ " "                                                      
    Language key........ " "                                                      
    Transaction......... "ME41 "                                                  
    Program............. "SAPLCLSC"                                               
    Screen.............. "SAPMM06E 0320"                                          
    Screen line......... 71                                                       
    Information on where termination occurred
    The termination occurred in the ABAP program "SAPLCLSC" in "EXECUTE_SELECT".  
    The main program was "SAPMM06E ".                                                                               
    The termination occurred in line 131 of the source code of the (Include)      
    program "LCLSCF2G"                                                           
    of the source code of program "LCLSCF2G" (when calling the editor 1310).      
    =============
    i even tried increasing the dialog processes but with no use.The same error occurs.
    I appreciate every one of help i can get, i am working on a deadline which is tomorrow evening to resovle this issue, any kind of help is highly appreciated.
    thanks
    mudessir.

    Hi
       follow correction method suggested in this dump,
    " The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
    contains a file called 'core'.  Save this file under another name."
    have you done this?
    with regards,
    raj.
    <i>pls, award points</i>

  • TimesTen Error :5126: A system managed cache group cannot contain non-stand

    I have created few cache groups in TimesTen.
    And when i fired script to create fillowing cache group its gives me error.
    please see the details mentioned below.
    CREATE USERMANAGED CACHE GROUP C_TBLSSTPACCOUNTINGSUMMARY
    AUTOREFRESH MODE INCREMENTAL INTERVAL 5 SECONDS STATE ON
    FROM
    schema.tablename
    ACCOUNTINGSUMMARYID DOUBLE,
    INPUTFILENAME VARCHAR(255) NOT NULL,
    ACCOUNTINGSTATUS VARCHAR(255) NOT NULL,
    RECORDCOUNT DOUBLE,
    LASTUPDATEDDATE DATE NOT NULL,
    CREATEDATE TIMESTAMP DEFAULT SYSDATE,
    PRIMARY KEY (ACCOUNTINGSUMMARYID),
    PROPAGATE);
    then error occurs like==>
    5121: Non-standard type mapping for column JISPRATCORBILLINGDEV501.TBLSSTPACCOUNTINGSUMMARY.ACCOUNTINGSUMMARYID, cache operations are restricted
    5126: A system managed cache group cannot contain non-standard column type mapping
    The command failed.

    If you have access to Oracle Metalink, Please take a look at the Note:367431.1
    Regards,
    Sabdar Syed.

  • Bus Error, System Pref won't launch

    This isn't a case of the System Preference not being found, being moved out of the Applications Folder, or anything trivial like that. System Preferences will not launch. This is a clean install of Leopard, and updated to 10.5.8. The error message in console is:
    9/1/10 3:11:45 PM com.apple.launchd74 (0x0-0x18018.com.apple.systempreferences212) Exited abnormally: Bus error
    "The application System Preferences quit unexpectedly." Relaunch doesn't wo

    baltwo swrote : "Move the com.apple.systempreferences.plist file out of your /Library/Preferences/"
    Was my first idea and would love to but, as this is just after having installed the system, Sys Prefs has not yet created any Pref, good, bad or indifferent ; ).
    Catch22ish, huh ?

  • System Preferences Won't Launch, console "bus error"

    This isn't a case of the System Preference not being found, being moved out of the Applications Folder, or anything trivial like that. System Preferences will not launch. This is a clean install of Leopard, and updated to 10.5.8. The error message in console is:
    9/1/10 3:11:45 PM com.apple.launchd74 (0x0-0x18018.com.apple.systempreferences212) Exited abnormally: Bus error
    "The application System Preferences quit unexpectedly." Relaunch doesn't work.

    I have exactly the same problem after having installed 10.5.8.
    I had to do this after not being able to start the machine at all because of (what I believe to be) a bug with Security Update 2010-005. The Archive and Install process did not work.
    This thread should be in "Using Mac OS X Leopard". I found it Googling "Exited abnormally: Bus error".

  • System received a Bus Error exception

    Hello everbody,
    when i power off and power on again my  router, i did not start. it says the message like this:
    -Traceback= 0x4027754C 0x400886BC 0x4008CDE4 0x400BAA5C
    $0 : 00000000, AT : 42F60000, v0 : 00000303, v1 : BFA00000
    a0 : 00000303, a1 : 00000000, a2 : 00000000, a3 : 00000005
    t0 : 000F4240, t1 : 0000000B, t2 : 0000000B, t3 : FFFFFFFE
    t4 : 4AB8C413, t5 : 00000000, t6 : 43130000, t7 : 4AB8C029
    s0 : 43137F24, s1 : 00000006, s2 : 00000000, s3 : 00000000
    s4 : 438FACE0, s5 : 42F40000, s6 : BEEFBACC, s7 : 00000000
    t8 : BFA00000, t9 : 00000003, k0 : 00000020, k1 : 00000000
    gp : 42F600E0, sp : 438FAC68, s8 : 43974F28, ra : 40277540
    EPC  : 4027754C, ErrorEPC : BFCC0E8C, SREG     : 34008003
    MDLO : 000003E8, MDHI     : 00000000, BadVaddr : 00000110
    DATA_START : 0x419E4B00
    Cause 0000000C (Code 0x3): TLB (store) exception
    -Traceback= 0x4027754C 0x400886BC 0x4008CDE4 0x400BAA5C
    No warm reboot Storage
    *** System received a Bus Error exception ***
    signal= 0xa, code= 0xc, context= 0x4313c01c
    PC = 0x4008d45c, Cause = 0x20, Status Reg = 0x34008002
    i need help urgently, what should i do. thanks in advance

    Thanks Leo for help,
    my router model is 2811. Do you have any information/document to fix the hardware failure.
    what should i do.

  • What does "The System bootstrapper has crashed: Bus error" mean ?

    What does "The System bootstrapper has crashed: Bus error" mean ?

    Was this an upgrade?
    You could repair disk and permissions,  but I suspect a corrupt OS X.  I would reinstall the operating system.
    COmmand R on reboot if your Mac is newer.

  • Error: System.Management.Automation.RemoteException: Federation information could not be received from the external organization.

    Greetings.
    I'm getting 2 errors and 1 warning in the Hybrid Configuration object:
    INFO : Session=Tenant Cmdlet=Get-FederationInformation -DomainName 'SanJuanCiudadPatria.com' -BypassAdditionalDomainValidation: $true START
    ERROR : System.Management.Automation.RemoteException: Federation information could not be received from the external organization.
    INFO : Session=Tenant Cmdlet=Get-FederationInformation FINISH Time=2620.7003ms
    INFO : Session=Tenant Cmdlet=Get-FederationInformation -DomainName 'SanJuanCiudadPatria.com' -BypassAdditionalDomainValidation: $true START
    ERROR : System.Management.Automation.RemoteException: Federation information could not be received from the external organization.
    INFO : Session=OnPrem Cmdlet=Get-OrganizationConfig START
    INFO : Session=OnPrem Cmdlet=Get-OrganizationConfig FINISH Time=203.229ms
    WARNING : Office 365 was unable to communicate with your on-premises Autodiscover endpoint.  This is typically due to incorrect DNS or firewall configuration.  The Office 365 tenant is currently configured to use the following URL for Autodiscover
    queries from the Office 365 tenant to the on-premises organization - https://autodiscover.SanJuanCiudadPatria.com/autodiscover/autodiscover.svc/WSSecurity. See the following article for further information: http://go.microsoft.com/fwlink/p/?LinkId=275838
    Any help would be greatly appreciated.
    Hello World.

    Hello,
    If the IIS configuration is missing the svc-Integrated handler mapping, the issue may occur. Please try to refer to the following KB to check if the issue can be solved.
    http://support.microsoft.com/kb/2626696
    Please check if there is A record for autodiscover on public DNS server or DNS SRV record.
    Additional blog for your reference.
    http://blogs.technet.com/b/mikehall/archive/2013/08/21/office-365-insight-into-the-hybrid-configuration-wizard-part-2.aspx
    Cara Chen
    TechNet Community Support

  • EEM smtp maxrun - System received a Bus Error exception

                       Hello, I need help with problem on my cisco 2901 router. If internet connection is down, and in this momen router try send mail over SMTP (tcl script) script was finish over maxrun.(it is normal for router). Auto my router rebooted
    In log I see:
    No warm reboot Storage
    *** System received a Bus Error exception ***
    signal= 0xa, code= 0x8, context= 0x29c1cdc4
      PC = 0x26310d54, SP = 0x317c09f8, RA = 0x22895e30
      Cause Reg = 0x00000008, Status Reg = 0x50009fe3
    sh ver:
    Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.1(4)M4, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Tue 20-Mar-12 18:57 by prod_rel_team
    If i disable scrip all work fine.

    You will need to open a TAC case for this.  The image you are running supports a feature called ASLR which requires additional information be collected to try and decode things.  Also it would be best to get the entire stack trace from the crashinfo file rather than just the RA and PC from the console dump.  It is best to have this worked by TAC to understand the root cause.
    Mike

  • How do I fix: DirectoryServices: Job appears to have crashed: Bus error

    Can anyone help with this problem? The only solution I have found is to erase and reinstall the OS. A reinstall alone will not fix it.
    I have experienced this problem on 3 Macs now, and Apple Care has virtually rebuilt my mini attempting to fix it. However to date, I haven't been able to find anyone at Apple who will look at the data. Here is what appears endlessly in /var/log/system.log:
    Apr 1 08:55:43 Peters-MacBook-Air com.apple.launchd[1] (com.apple.DirectoryServices[161]): Job appears to have crashed: Bus error
    Apr 1 08:55:43 Peters-MacBook-Air com.apple.launchd[1] (com.apple.DirectoryServices): Throttling respawn: Will start in 8 seconds
    Apr 1 08:55:43 Peters-MacBook-Air com.apple.ReportCrash.Root[156]: 2011-04-01 08:55:43.390 ReportCrash[156:140b] Saved crash report for DirectoryService[161] version ??? (???) to /Library/Logs/DiagnosticReports/DirectoryService2011-04-01-085543localhost.crash
    Apr 1 08:55:51 Peters-MacBook-Air DirectoryService[162]: Improper shutdown detected
    Apr 1 08:55:53 Peters-MacBook-Air com.apple.launchd[1] (com.apple.DirectoryServices[162]): Job appears to have crashed: Bus error
    Apr 1 08:55:53 Peters-MacBook-Air com.apple.launchd[1] (com.apple.DirectoryServices): Throttling respawn: Will start in 8 seconds
    Apr 1 08:55:53 Peters-MacBook-Air com.apple.ReportCrash.Root[156]: 2011-04-01 08:55:53.788 ReportCrash[156:380b] Saved crash report for DirectoryService[162] version ??? (???) to /Library/Logs/DiagnosticReports/DirectoryService2011-04-01-085553localhost.crash
    Apr 1 08:56:01 Peters-MacBook-Air DirectoryService[163]: Improper shutdown detected
    Apr 1 08:56:04 Peters-MacBook-Air com.apple.launchd[1] (com.apple.DirectoryServices[163]): Job appears to have crashed: Bus error
    Apr 1 08:56:04 Peters-MacBook-Air com.apple.launchd[1] (com.apple.DirectoryServices): Throttling respawn: Will start in 8 seconds
    Apr 1 08:56:04 Peters-MacBook-Air com.apple.ReportCrash.Root[156]: 2011-04-01 08:56:04.237 ReportCrash[156:472f] Saved crash report for DirectoryService[163] version ??? (???) to /Library/Logs/DiagnosticReports/DirectoryService2011-04-01-085604localhost.crash
    Apr 1 08:56:12 Peters-MacBook-Air DirectoryService[165]: Improper shutdown detected
    Here is one of the crash logs.
    Process: DirectoryService [226]
    Path: /usr/sbin/DirectoryService
    Identifier: DirectoryService
    Version: ??? (???)
    Code Type: X86-64 (Native)
    Parent Process: launchd [1]
    Date/Time: 2011-04-04 10:30:15.232 -0600
    OS Version: Mac OS X 10.6.6 (10J567)
    Report Version: 6
    Exception Type: EXCBADACCESS (SIGBUS)
    Exception Codes: 0x000000000000000a, 0x0000000100385000
    Crashed Thread: 1 Dispatch queue: com.apple.root.default-priority
    Thread 0: Dispatch queue: com.apple.main-thread
    0 libSystem.B.dylib 0x00007fff8503f2da machmsgtrap + 10
    1 libSystem.B.dylib 0x00007fff8503f94d mach_msg + 59
    2 com.apple.CoreFoundation 0x00007fff83955932 __CFRunLoopRun + 1698
    3 com.apple.CoreFoundation 0x00007fff83954dbf CFRunLoopRunSpecific + 575
    4 com.apple.CoreFoundation 0x00007fff83954b46 CFRunLoopRun + 70
    5 DirectoryService 0x000000010000dbe9 main + 3061
    6 DirectoryService 0x000000010000cfec start + 52
    Thread 1 Crashed: Dispatch queue: com.apple.root.default-priority
    0 libSystem.B.dylib 0x00007fff8509a33d strtok_r + 19
    1 DirectoryService 0x00000001000a9d04 FlatFileNode::FetchMatchingRecords(sBDPISearchRecordsContext*, void*, unsigned int*) + 1976
    2 DirectoryService 0x00000001000acad7 FlatFileNode::InternalSearchRecords(sBDPISearchRecordsContext*, void*, unsigned int*) + 681
    3 DirectoryService 0x00000001000acd5b FlatFileNode::SearchRecords(sBDPISearchRecordsContext*, void*, unsigned int*) + 237
    4 DirectoryService 0x00000001000a5a5b BaseDirectoryPlugin::GetRecordList(sGetRecordList*) + 309
    5 DirectoryService 0x00000001000a68a0 BaseDirectoryPlugin::ProcessRequest(void*) + 584
    6 DirectoryService 0x00000001000017fb CRequestHandler::HandlePluginCall(sComData**) + 715
    7 DirectoryService 0x00000001000024bc CRequestHandler::HandleRequest(sComData**) + 222
    8 DirectoryService 0x000000010002e42a CMessaging::SendInlineMessage(unsigned int) + 148
    9 DirectoryService 0x000000010000562b dsGetRecordList + 1113
    10 DirectoryService 0x0000000100082929 CCachePlugin::GetRecordListLibInfo(unsigned int, char const*, char const*, unsigned int, tDataList*, sCacheValidation* (*)(unsigned int, unsigned int, kvbuf_t*, tDataBuffer*, tRecordEntry*, unsigned int, void*, CCache*, char const**), kvbuf_t*, void*, CCache*, char const**, sCacheValidation**) + 221
    11 DirectoryService 0x000000010008933e CCachePlugin::DSgethostbyname_int(char*, char const*, char const*, int, bool, void**, int*) + 960
    12 DirectoryService 0x0000000100089ae2 CCachePlugin::DSgethostbynameservice(kvbuft*, int) + 336
    13 DirectoryService 0x000000010008f7e7 CCachePlugin::ProcessLookupRequest(int, char*, int, int) + 811
    14 DirectoryService 0x000000010002a0fd libinfoDSmigdoQuery + 559
    15 DirectoryService 0x000000010009325a _XQuery + 262
    16 DirectoryService 0x0000000100092fea DSlibinfoMIG_server + 106
    17 DirectoryService 0x00000001000282a1 dsmigdemux_internaldispatch(mach_msg_headert*, machmsg_headert*) + 65
    18 libSystem.B.dylib 0x00007fff850bbe24 machmsgserver + 357
    19 libSystem.B.dylib 0x00007fff8507b2c4 dispatch_call_block_andrelease + 15
    20 libSystem.B.dylib 0x00007fff85059810 dispatch_workerthread2 + 206
    21 libSystem.B.dylib 0x00007fff85059168 pthreadwqthread + 353
    22 libSystem.B.dylib 0x00007fff85059005 start_wqthread + 13
    Thread 2:
    0 libSystem.B.dylib 0x00007fff8503f2da machmsgtrap + 10
    1 libSystem.B.dylib 0x00007fff8503f94d mach_msg + 59
    2 com.apple.CoreFoundation 0x00007fff83955932 __CFRunLoopRun + 1698
    3 com.apple.CoreFoundation 0x00007fff83954dbf CFRunLoopRunSpecific + 575
    4 com.apple.CoreFoundation 0x00007fff83954b46 CFRunLoopRun + 70
    5 DirectoryService 0x000000010001c784 CPluginRunLoopThread::ThreadMain() + 150
    6 ...ectoryServiceCore.Framework 0x00000001001790ac DSCThread::Run() + 36
    7 ...ectoryServiceCore.Framework 0x000000010017934b DSLThread::_RunWrapper(void*) + 67
    8 libSystem.B.dylib 0x00007fff85078536 pthreadstart + 331
    9 libSystem.B.dylib 0x00007fff850783e9 thread_start + 13
    Thread 3: Dispatch queue: com.apple.root.high-priority
    0 libSystem.B.dylib 0x00007fff8503f316 semaphorewaittrap + 10
    1 libSystem.B.dylib 0x00007fff8507b669 dispatch_semaphore_waitslow + 211
    2 DirectoryService 0x00000001000286bd ___StartKernelListener_block_invoke8 + 33
    3 libSystem.B.dylib 0x00007fff8507b2c4 dispatch_call_block_andrelease + 15
    4 libSystem.B.dylib 0x00007fff85059831 dispatch_workerthread2 + 239
    5 libSystem.B.dylib 0x00007fff85059168 pthreadwqthread + 353
    6 libSystem.B.dylib 0x00007fff85059005 start_wqthread + 13
    Thread 4: Dispatch queue: com.apple.libdispatch-manager
    0 libSystem.B.dylib 0x00007fff8505816a kevent + 10
    1 libSystem.B.dylib 0x00007fff8505a03d dispatch_mgrinvoke + 154
    2 libSystem.B.dylib 0x00007fff85059d14 dispatch_queueinvoke + 185
    3 libSystem.B.dylib 0x00007fff8505983e dispatch_workerthread2 + 252
    4 libSystem.B.dylib 0x00007fff85059168 pthreadwqthread + 353
    5 libSystem.B.dylib 0x00007fff85059005 start_wqthread + 13
    Thread 5:
    0 libSystem.B.dylib 0x00007fff8503f2da machmsgtrap + 10
    1 libSystem.B.dylib 0x00007fff8503f94d mach_msg + 59
    2 libSystem.B.dylib 0x00007fff8504ac4e vprocmig_lookup2 + 182
    3 libSystem.B.dylib 0x00007fff8504aaa5 bootstraplookup2 + 268
    4 libSystem.B.dylib 0x00007fff85053ec4 dsrunning + 52
    5 libSystem.B.dylib 0x00007fff85053ce1 searchgetmodule + 86
    6 libSystem.B.dylib 0x00007fff85053c68 searchitembynumber + 196
    7 libSystem.B.dylib 0x00007fff85073a56 getpwuid + 26
    8 com.apple.CoreFoundation 0x00007fff8393cf49 _CFUpdateUserInfo + 105
    9 com.apple.CoreFoundation 0x00007fff8393ce96 _CFUserName + 22
    10 com.apple.CoreFoundation 0x00007fff8393b119 __CFXPreferencesGetManagedSourceForBundleIDAndUser + 537
    11 com.apple.CoreFoundation 0x00007fff8393aae7 __CFXPreferencesGetSearchListForBundleID + 119
    12 com.apple.CoreFoundation 0x00007fff8393a9fb CFPreferencesCopyAppValue + 43
    13 com.apple.CoreFoundation 0x00007fff8393a999 _CFBundleCopyUserLanguages + 665
    14 com.apple.CoreFoundation 0x00007fff8393a1b4 _CFBundleAddPreferredLprojNamesInDirectory + 404
    15 com.apple.CoreFoundation 0x00007fff83939c8a _CFBundleGetLanguageSearchList + 170
    16 com.apple.CoreFoundation 0x00007fff8393a4ba _CFBundleAddPreferredLprojNamesInDirectory + 1178
    17 com.apple.CoreFoundation 0x00007fff83993e97 _CFBundleCopyLanguageSearchListInDirectory + 167
    18 com.apple.CoreFoundation 0x00007fff839990d9 CFBundleCopyResourceURLsOfTypeInDirectory + 249
    19 DirectoryService 0x000000010001eb92 CPluginHandler::LoadPlugins(unsigned int) + 388
    20 DirectoryService 0x000000010000e9c9 CPluginHandler::ThreadMain() + 491
    21 ...ectoryServiceCore.Framework 0x00000001001790ac DSCThread::Run() + 36
    22 ...ectoryServiceCore.Framework 0x000000010017934b DSLThread::_RunWrapper(void*) + 67
    23 libSystem.B.dylib 0x00007fff85078536 pthreadstart + 331
    24 libSystem.B.dylib 0x00007fff850783e9 thread_start + 13
    Thread 6: Dispatch queue: com.apple.root.default-priority
    0 libSystem.B.dylib 0x00007fff8503f2da machmsgtrap + 10
    1 libSystem.B.dylib 0x00007fff8503f94d mach_msg + 59
    2 libSystem.B.dylib 0x00007fff850bbe93 machmsgserver + 468
    3 libSystem.B.dylib 0x00007fff8507b2c4 dispatch_call_block_andrelease + 15
    4 libSystem.B.dylib 0x00007fff85059810 dispatch_workerthread2 + 206
    5 libSystem.B.dylib 0x00007fff85059168 pthreadwqthread + 353
    6 libSystem.B.dylib 0x00007fff85059005 start_wqthread + 13
    Thread 7: Dispatch queue: com.apple.root.high-priority
    0 libSystem.B.dylib 0x00007fff8507b8c2 syscall + 10
    1 DirectoryService 0x00000001000284ca ___StartKernelListener_block_invoke9 + 72
    2 libSystem.B.dylib 0x00007fff8507b2c4 dispatch_call_block_andrelease + 15
    3 libSystem.B.dylib 0x00007fff85059831 dispatch_workerthread2 + 239
    4 libSystem.B.dylib 0x00007fff85059168 pthreadwqthread + 353
    5 libSystem.B.dylib 0x00007fff85059005 start_wqthread + 13
    Thread 1 crashed with X86 Thread State (64-bit):
    rax: 0x0000000000000000 rbx: 0x000000010040c300 rcx: 0x00007fff70996630 rdx: 0x000000010040bab0
    rdi: 0x0000000100385000 rsi: 0x00000001000eebea rbp: 0x000000010037fd70 rsp: 0x000000010037fd70
    r8: 0x0000000000000000 r9: 0x000000010040c1e0 r10: 0x0000000000000001 r11: 0x0000000000000011
    r12: 0x0000000000000000 r13: 0x0000000000000001 r14: 0x000000010040c380 r15: 0x000000010037fea0
    rip: 0x00007fff8509a33d rfl: 0x0000000000010206 cr2: 0x0000000100385000
    Binary Images:
    0x100000000 - 0x100120ff7 +DirectoryService ??? (???) <910DBBCD-D741-1530-210F-9A3944045A5B> /usr/sbin/DirectoryService
    0x100171000 - 0x100182fff com.apple.DirectoryServiceCore.Framework 3.6 (621.9) <16FCF0D0-89B6-6BD2-F8CA-443E1A89307C> /System/Library/PrivateFrameworks/DirectoryServiceCore.framework/Versions/A/Dir ectoryServiceCore
    0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <DB8B8AB0-0C97-B51C-BE8B-B79895735A33> /usr/lib/dyld
    0x7fff80a41000 - 0x7fff80b58fef libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <AFE91118-DBF3-6313-37B8-8A2002C6A46B> /usr/lib/libxml2.2.dylib
    0x7fff80bc6000 - 0x7fff80c7cfff libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <1960E662-D35C-5D98-EB16-D43166AE6A22> /usr/lib/libobjc.A.dylib
    0x7fff813f6000 - 0x7fff81445ff7 com.apple.DirectoryService.PasswordServerFramework 6.0 (6.0) <F5B744D7-AEAF-6B66-43CF-6E31CDA18EAB> /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordS erver
    0x7fff81446000 - 0x7fff8144aff7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib
    0x7fff8144b000 - 0x7fff814ebfff com.apple.LaunchServices 362.2 (362.2) <A8EDC37C-1D40-5ED0-49BE-90EF110A6B3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
    0x7fff814ec000 - 0x7fff81569fef libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <35ECA411-2C08-FD7D-11B1-1B7A04921A5C> /usr/lib/libstdc++.6.dylib
    0x7fff817a6000 - 0x7fff817d1ff7 libxslt.1.dylib 3.24.0 (compatibility 3.0.0) <6589F0FC-41DB-8494-CA8B-487F4E328EB9> /usr/lib/libxslt.1.dylib
    0x7fff821e1000 - 0x7fff82467fff com.apple.security 6.1.1 (37594) <1B4E1ABD-1BB3-DA49-F574-0EEB23E73C6A> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff824fd000 - 0x7fff82525fff com.apple.DictionaryServices 1.1.2 (1.1.2) <E9269069-93FA-2B71-F9BA-FDDD23C4A65E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
    0x7fff828c2000 - 0x7fff82922fe7 com.apple.framework.IOKit 2.0 (???) <D107CB8A-5182-3AC4-35D0-07068A695C05> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff82968000 - 0x7fff8297afe7 libsasl2.2.dylib 3.15.0 (compatibility 3.0.0) <30FE378B-99FE-8C7C-06D0-A3AA0A0A70D4> /usr/lib/libsasl2.2.dylib
    0x7fff829ff000 - 0x7fff82a20fff libresolv.9.dylib 41.0.0 (compatibility 1.0.0) <9B7AEE96-D18E-5ECF-9837-BD5CFD397831> /usr/lib/libresolv.9.dylib
    0x7fff83909000 - 0x7fff83a80fe7 com.apple.CoreFoundation 6.6.4 (550.42) <770C572A-CF70-168F-F43C-242B9114FCB5> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff84e33000 - 0x7fff84e44ff7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <5BAFAE5C-2307-C27B-464D-582A10A6990B> /usr/lib/libz.1.dylib
    0x7fff84ee3000 - 0x7fff84f2ffff libauto.dylib ??? (???) <F7221B46-DC4F-3153-CE61-7F52C8C293CF> /usr/lib/libauto.dylib
    0x7fff84f7b000 - 0x7fff84fb8fff com.apple.LDAPFramework 2.0 (120.1) <A890D6E1-2721-1C1B-3B3C-13ACE5EF6B3D> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x7fff84ff3000 - 0x7fff8503dff7 com.apple.Metadata 10.6.3 (507.15) <5170FCE0-ED6C-2E3E-AB28-1DDE3F628FC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
    0x7fff8503e000 - 0x7fff851fffff libSystem.B.dylib 125.2.1 (compatibility 1.0.0) <71E6D4C9-F945-6EC2-998C-D61AD590DAB6> /usr/lib/libSystem.B.dylib
    0x7fff857a0000 - 0x7fff857a1ff7 com.apple.TrustEvaluationAgent 1.1 (1) <A91CE5B9-3C63-5F8C-5052-95CCAB866F72> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
    0x7fff857c5000 - 0x7fff85882ff7 com.apple.CoreServices.OSServices 357 (357) <ABB9A264-05D8-DFF1-35DB-C4B19C4E0B71> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x7fff85883000 - 0x7fff85a41fff libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <781E7B63-2AD0-E9BA-927C-4521DB616D02> /usr/lib/libicucore.A.dylib
    0x7fff85b42000 - 0x7fff85b83fff com.apple.SystemConfiguration 1.10.5 (1.10.2) <FB39F09C-57BB-D8CC-348D-93E00C602F7D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x7fff85fab000 - 0x7fff8605afff edu.mit.Kerberos 6.5.10 (6.5.10) <05AEA348-2288-E1C0-8F10-0D8880AE7530> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x7fff861c2000 - 0x7fff8627bfff libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <2C5ED312-E646-9ADE-73A9-6199A2A43150> /usr/lib/libsqlite3.dylib
    0x7fff8627c000 - 0x7fff86292fef libbsm.0.dylib ??? (???) <0321D32C-9FE1-3919-E03E-2530A0C1191B> /usr/lib/libbsm.0.dylib
    0x7fff86958000 - 0x7fff86a79fe7 libcrypto.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <48AEAFE1-21F4-B3C8-4199-35AD5E8D0613> /usr/lib/libcrypto.0.9.8.dylib
    0x7fff86c7c000 - 0x7fff86cb6fff libssl.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <C7153747-50E3-32DA-426F-CC4C505D1D6C> /usr/lib/libssl.0.9.8.dylib
    0x7fff8740e000 - 0x7fff8741cff7 libkxld.dylib ??? (???) <4016E9E6-0645-5384-A697-2775B5228113> /usr/lib/system/libkxld.dylib
    0x7fff87454000 - 0x7fff87788fff com.apple.CoreServices.CarbonCore 861.23 (861.23) <08F360FA-1771-4F0B-F356-BEF68BB9D421> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x7fff878b9000 - 0x7fff878b9ff7 com.apple.CoreServices 44 (44) <DC7400FB-851E-7B8A-5BF6-6F50094302FB> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff8864d000 - 0x7fff88688fff com.apple.AE 496.4 (496.4) <CB905496-4D6B-F26A-399D-840D26DBEE5B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
    0x7fff88878000 - 0x7fff8894afe7 com.apple.CFNetwork 454.11.5 (454.11.5) <B3E2BE12-D7AA-5940-632A-1E5E7BF8E6E3> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x7fff8894b000 - 0x7fff88bceff7 com.apple.Foundation 6.6.4 (751.42) <9A99D378-E97A-8C0F-3857-D0FAA30FCDD5> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff88e7f000 - 0x7fff88f0ffff com.apple.SearchKit 1.3.0 (1.3.0) <45BA1053-9196-3C2F-2421-AFF5E09627CC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x7fff89120000 - 0x7fff8912ffff com.apple.NetFS 3.2.1 (3.2.1) <4396CAD7-FDAF-8C63-97FA-74E7124DFF2A> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff8913e000 - 0x7fff89144fff com.apple.DiskArbitration 2.3.1 (2.3.1) <D5D3AE5F-83AC-0CEB-2DC3-755F0CC20A4E> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x7fffffe00000 - 0x7fffffe01fff libSystem.B.dylib ??? (???) <71E6D4C9-F945-6EC2-998C-D61AD590DAB6> /usr/lib/libSystem.B.dylib

    Any fix for this yet?
    com.apple.DirectoryServices crashes and attempts to restart every 10 seconds on my system:
    10/10/11 4:05:29 PM    com.apple.launchd[1]    (com.apple.DirectoryServices[1791]) Job appears to have crashed: Bus error
    10/10/11 4:05:29 PM    com.apple.launchd[1]    (com.apple.DirectoryServices) Throttling respawn: Will start in 7 seconds
    10/10/11 4:05:29 PM    com.apple.ReportCrash.Root[1789]    2011-10-10 16:05:29.978 ReportCrash[1789:4543] Saved crash report for DirectoryService[1791] version ??? (???) to /Library/Logs/DiagnosticReports/DirectoryService_2011-10-10-160529_localhost.cr ash

  • Bus error in the Forte executable

    Hi,
    We have an environment with forte' (ver. 3.0.G.2) running
    on AIX 4.1 (The name of central server is cld_app1 and the nodemgr start
    with the name cld_TDR). In our environment we are using two differnet
    repository. In rep1 we have a very simple project (called 'aaa') that
    use one small class with two methods. One method print the date & time.
    The second method communicate with a serviceobject that use MQSeries to
    put/get some messages in the queues.
    The project work correctly in test run and in distribuite mode.
    If we export the same project (aaa) and we import in other repository
    (rep2 in the same environment) the project doesn't work. Infact,
    during test run forte' return the following:
    Begin Stack Backtrace
    =========================================================
    =
    Trace caused by a bus error in the Forte executable:
    ftexec Version 3.0.G.2
    IBM RS6000/Aix 4.1
    Forte Application Environment (tm), Forte Runtime Environment (tm),
    Forte Conductor (tm):
    Copyright (c) 1994-1998, Forte Software, Inc. and its licensors.
    US Patent No. 5,457,797
    Forte Express (tm), Forte WebEnterprise (tm):
    Copyright (c) 1995-1998, Forte Software, Inc.
    All Rights Reserved.
    Unpublished rights reserved under the copyright laws of the United
    States.
    Fri Mar 13 16:07:45 1998
    Fault at 25-Mar-1999 10:42:53, pid '2292', node 'cld_app1':
    0xd0b8886c = d0b8886c()
    0xd0b88ae4 = d0b88ae4()
    qqos_StkTrc: Cannot print stack trace.
    Recursive stack trace detected. Exiting.
    If we try to run in partitioning mode, the same error appears when
    forte' "loading partition into server" with the following adding
    message:
    Unable to start the partition aaa_cl0_Part1 on any of nodes to wich
    been assigned. See the remainder of the error stack for more
    information.
    In the "more" informations we have the following:
    SYSTEM ERROR: Unable to start the partition aaa_cl0_Part1 on any of the
    nodes to which it has been assigned. See the remainder of the error
    stack for more
    information.
    Class: qqsp_ResourceException
    Error #: [1602, 593]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
    Last TOOL statement: method overview.StartApplication
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    SYSTEM ERROR: Unable to start partition aaa_cl0_Part1 on node cld_TDR.
    Class: qqsp_ErrorDescriptor
    Error #: [1602, 592]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    SYSTEM ERROR: Lost contact with remote server while trying to load
    partition
    aaa_cl0_Part1. Check server log file for more information about the
    specific
    problem.
    Class: qqsp_ResourceException
    Error #: [1301, 102]
    Detected at: qqem_IPartitionAgent::Startup at 5
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Thu Mar 25 09:22:20
    Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
    (object name Unnamed) from partition "Forte_Executor",
    (partitionId =
    546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158.19]) in application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: Network partner closed connection. This usually means the
    process at the other end of the wire failed. Please go look there and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Thu Mar 25 09:22:20
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: Error parameters for Set:0 Msg:0:
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Thu Mar 25 09:22:20
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    Thanks in advance
    Luz Marina e Massimiliano
    Get Your Private, Free Email at http://www.hotmail.com
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi,
    We have an environment with forte' (ver. 3.0.G.2) running
    on AIX 4.1 (The name of central server is cld_app1 and the nodemgr start
    with the name cld_TDR). In our environment we are using two differnet
    repository. In rep1 we have a very simple project (called 'aaa') that
    use one small class with two methods. One method print the date & time.
    The second method communicate with a serviceobject that use MQSeries to
    put/get some messages in the queues.
    The project work correctly in test run and in distribuite mode.
    If we export the same project (aaa) and we import in other repository
    (rep2 in the same environment) the project doesn't work. Infact,
    during test run forte' return the following:
    Begin Stack Backtrace
    =========================================================
    =
    Trace caused by a bus error in the Forte executable:
    ftexec Version 3.0.G.2
    IBM RS6000/Aix 4.1
    Forte Application Environment (tm), Forte Runtime Environment (tm),
    Forte Conductor (tm):
    Copyright (c) 1994-1998, Forte Software, Inc. and its licensors.
    US Patent No. 5,457,797
    Forte Express (tm), Forte WebEnterprise (tm):
    Copyright (c) 1995-1998, Forte Software, Inc.
    All Rights Reserved.
    Unpublished rights reserved under the copyright laws of the United
    States.
    Fri Mar 13 16:07:45 1998
    Fault at 25-Mar-1999 10:42:53, pid '2292', node 'cld_app1':
    0xd0b8886c = d0b8886c()
    0xd0b88ae4 = d0b88ae4()
    qqos_StkTrc: Cannot print stack trace.
    Recursive stack trace detected. Exiting.
    If we try to run in partitioning mode, the same error appears when
    forte' "loading partition into server" with the following adding
    message:
    Unable to start the partition aaa_cl0_Part1 on any of nodes to wich
    been assigned. See the remainder of the error stack for more
    information.
    In the "more" informations we have the following:
    SYSTEM ERROR: Unable to start the partition aaa_cl0_Part1 on any of the
    nodes to which it has been assigned. See the remainder of the error
    stack for more
    information.
    Class: qqsp_ResourceException
    Error #: [1602, 593]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
    Last TOOL statement: method overview.StartApplication
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    SYSTEM ERROR: Unable to start partition aaa_cl0_Part1 on node cld_TDR.
    Class: qqsp_ErrorDescriptor
    Error #: [1602, 592]
    Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    SYSTEM ERROR: Lost contact with remote server while trying to load
    partition
    aaa_cl0_Part1. Check server log file for more information about the
    specific
    problem.
    Class: qqsp_ResourceException
    Error #: [1301, 102]
    Detected at: qqem_IPartitionAgent::Startup at 5
    Error Time: Thu Mar 25 09:22:21
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: The connection to the partner was terminated by the
    Communication
    Manager for the reasons below.
    Class: qqsp_DistAccessException
    Detected at: qqdo_PartitionMgr::StopLocation at 1
    Error Time: Thu Mar 25 09:22:20
    Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
    (object name Unnamed) from partition "Forte_Executor",
    (partitionId =
    546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158.19]) in application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: Network partner closed connection. This usually means the
    process at the other end of the wire failed. Please go look there and
    find
    out why.
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 2
    Error Time: Thu Mar 25 09:22:20
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    INFORMATION: Error parameters for Set:0 Msg:0:
    Class: qqsp_DistAccessException
    Detected at: qqcm_HoseFSM::ReceivedClose at 1
    Error Time: Thu Mar 25 09:22:20
    Exception occurred (locally) on partition "Forte_cl0_Client",
    (partitionId
    = 546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1, taskId =
    [546BCA70-E125-11D2-BFFF-B37364EDAA77:0x158:0x1.17]) in
    application
    "Forte_cl0", pid 20236 on node cld_app1 in environment
    Collaudo_TDR.
    Thanks in advance
    Luz Marina e Massimiliano
    Get Your Private, Free Email at http://www.hotmail.com
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • InDesign Server :line 13: 2753 Bus error "$installed_name" "$@"

    [InDesign Server CS4, CS5, CS5.5    line 13: 2753 Bus error "$installed_name" "$@"]
    We support a few clients on various version of InDesign Server and all have exactly the same issue upon having the application produce PDF files...   line 13: 2753 Bus error "$installed_name" "$@"   which causes InDesign Server to unexpectedly quit.
    Searching these forums we have found CS3 instances of this error message pointing to fonts not loaded on the machine running InDesign Server, but no "this is what we did to fix it" solution has been found.
    Our customers are running beefed up MacPros or Mac Minis with Mac OS 10.6 (non server) and OS 10.7 (server), 8GB - 16GB RAM, 1TB HD
    For font management we have the following being utilized:
    - Universal type server
      - if no plugin exists for InD Server, not sure how much this app will help manage fonts
    - Suitcase Server
    - if no plugin exists for InD Server, not sure how much this app will help manage fonts
    - Loading all fonts into:   /Users/*/Library/Fonts
      - seems to be the best option for font management on a system running InDesign Server
    Our company develops a plugin for InDesign Server and allows regular InDesign to produce the pdfs in a similar manner.  Running our plugin under regular InDesign we DO NOT have these issues of BUS errors, yet as soon as any of our customers utilize InDesign Server, they all immediately see BUS errors.
    We have written a shell script that quits (normally) indesign server, and relaunches it (if quit abnormally) so that we have some semblance of an "always on" InDesign Server application, but this is merely a band-aid fix for a bigger problem.
    We are pointing the finger at Adobe InDesign Server being the problem here, yet our customers do not care where the blame is placed, we are seeing a solution for them in any fashion that presents a permanent solution.
    Julio Vasquez
    Product Specialist @ Comosoft, Inc.

    Hi Julio,
    I am having the same exact problem. We are evaluating the InDesign server and will consider buying it only if it performs reasonably stable. This "installed_name" "$@" is baffling us.
    Team Adobe InDesign Server: Kindly address this concern soon!
    Varun

Maybe you are looking for