IDOC Runtime error TIME_OUT has occurred

Dears,
          We are having a Machine to Machine Order interface, where huge volume of order files are being sent to SAP from legacy system through XML files which PI interface converts as Inbound IDOCs.
The issue we are facing here is : when huge number of order files are sent the IDOCs are stuck in 51 status due to TIME_OUT error. This is mainly because of :
1. Huge volume of files
2. Size of files
which eventually leads to optimum consumption of system resources and thus leading to TIME OUT errors, where order files gets stuck under 51 status with TIME OUT errors.
Alternative solutions : During peak season we do re run the IDOCs when the system resources are up or not busy.
Let me know, are there any other approach which we can consdier other than below mentioned ones :
1. Batch jobs
2. Bang on for bigger app servers
Your inputs and suggestions are highly appreciated.
Regards
Chirag Gowda

Hi,
break this into two select queries......
use the below code to do the same....
data : begin of fs_afko
              aufnr type afko-aufnr,
              aufpl type afko-aufpl,
              reuck type afko-reuck,
        end of fs_afko.
data : Begin of fs_afpo,
            aufnr type afpo-aufnr,
           matnr type afpo-matnr,
        End of fs_afpo.
data : t_afko type table of fs_afko,
         t_afpo type table of fs_afpo.
SELECT aufnr aufpl rueck
  INTO   TABLE t_afko
  FROM   afko
  WHERE  afko~aufnr  IN  s_aufnr
  AND    afko~dispo  IN  s_dispo.
SELECT afpo~matnr
  INTO   TABLE t_afpo
  FROM   afpo
  FOR ALL ENTRIES IN t_afko
  WHERE  aufnr  =  t_afko-aufnr
  AND    afpo~matnr  IN  s_matnr
  AND    afpo~dwerk  IN  s_werks
  AND    afpo~dauat  IN  s_auart.
loop at t_afko into fs_afko.
  loop at t_afpo into fs_afpo where aufnr = fs_afko-aufnr.
    move-corresponding fs_afko to fs_temp_orders.
    move-corresponding fs_afpo to fs_temp_orders.
    append fs_temp_orders to it_temp_orders
  endloop.
endloop.
Regards,
Siddarth

Similar Messages

  • Runtime error RFC_NO_AUTHORITY has occurred in SM58

    Hi Guys,
    We are posting some IDocs from SAP R/3 ECC to XI and they get stuck in SM58 with error:
    "Runtime error RFC_NO_AUTHORITY has occurred"
    Do you have any ideas what this might be ?
    Does this have to do with the user that executes the program to send the IDocs or the user used in RFC, because the RFC in SM59 works fine when tested and the user used there is PIAPPLUSER. It is also possible to logon remote.

    Hi,
    Thank you for your reply. Problem solved. I assigned role SAP_ALL to PIAPPLUSER used in the RFC Connection in SM59.
    Best Regards,
    Evaggelos Gkatzios
    Edited by: Evaggelos Gkatzios on May 30, 2010 12:45 PM

  • Runtime error objects_objref_not_assigned has occured

    hi,
    i created bdc call transaction using (TRIP) tcode. and calling in rfc. in the back end its working properly, and in report also i called this function module and tested, there also getting result
    properly, but the problem is, when this RFC used in java application means it showing error like (RUNTIME ERROR OBJECT_OBJECTREF_NOT_ASSIGNED ) has occured.
    plz give some solution.......................

    Dear Klaus sir,
    Basicalliy the data is coming from dot net to sap by rfc(zobd_upload) and into table zobd..
    after that we are using one program where we can fetch the data from zobd table and using one bdc to update the likp table.but in production likp table is not updating and zobd table updated..
    how to resolve that issue?
    is any bdc problem?

  • Runtime error OBJECTS_OBJREF_NOT_ASSIGNED has occurred

    Hi All,
    I am trying to run a MM42 BDC in the background and I am getting the error - Runtime error OBJECTS_OBJREF_NOT_ASSIGNED has occurred. Kindly help

    Dear Klaus sir,
    Basicalliy the data is coming from dot net to sap by rfc(zobd_upload) and into table zobd..
    after that we are using one program where we can fetch the data from zobd table and using one bdc to update the likp table.but in production likp table is not updating and zobd table updated..
    how to resolve that issue?
    is any bdc problem?

  • While executing 'Z' BAPI Runtime error CALL_FUNCTION_NOT_FOUND has occurred

    Dear Friends,
    We Customized 'Z' BAPI but not transported to QA yet,
    Is it possible to test with QA by fetch QA data by giving RFC target sys: (QA RFC Destination Name)
    If I give RFC target sys: (QA RFC Destination), I am getting Runtime error CALL_FUNCTION_NOT_FOUND has occurred. 
    How to resole this....
    What is method to check this customized BAPI with different server...../
    It is working fine for Standard BAPI.
    Regards

    But you should be able to call it in the DEV system from QA. This will prove that the RFC part works.
    Rob

  • Runtime error CONVT_NO_NUMBER has occurred

    Dear experts,
    I am using BAPI -- 'HR_MAINTAIN_MASTERDATA' to maintain infotype 8(Basic pay).
    I debugged the code. The data is coming in IT (that is of type PPROP) from my text file. But it gives runtime error in the FM saying --
    "Runtime error CONVT_NO_NUMBER has occurred"
    Please guide,
    Sumit.

    hi,
    I checked in ST22. It says unable to interpret 4B as a number. Now I went to transaction PA30 and checked it's possible values. There were only 2- 8A and 8B. so I changed it to 8B. But still gives same error, as unable to interpret 8B as  a number.
    This is my int table while debugging--
    line infty(c4)  fname(c132)   fval(c255)   seqnr(n2)
    1     0008     P0008-PERNR     40083005     00
    2     0008     P0008-BEGDA     01012010     00
    3     0008     P0008-ENDDA     31129999     00
    4     0008     P0008-TRFAR     A1     00
    5     0008     P0008-TRFGR     ASST.GM     00
    6     0008     P0008-TRFST     MA     00
    7     0008     P0008-BSGRD     8B     00       " here is my 8B
    8     0008     P0008-TRFGB     10     00
    9     0008     P0008-DIVGV     01     00
    10     0008     P0008-ANSAL     192     00
    11     0008     P0008-ANCUR     18437     00
    12     0008     P0008-WAERS     INR     00
    13     0008     P0008-LGA01     INR     00
    14     0008     P0008-BET01     4000     00
    15     0008     P0008-LGA02     4657     00
    if fval is of c255, why doen it interpret it's fields as a number?

  • Runtime error RAISE_EXCEPTION has occurred

    I am running BDC in background for PP03 and getting this error message "Error message: (00/341) Runtime error RAISE_EXCEPTION has occurred" but while running in foreground it is working fine.In mode E there is no error ie successfully executed but in background this exception "Exception condition "CNTL_SYSTEM_ERROR" is raised......Please give details analysis of problem as i am new to ABAP-HR.. Pasting the dump also. ABAP Gurus please dont adivice me to try with other alternates like BAPI etc. As i am doN'T know about BAPI and i am bound to fix the problem by BDC only
    Thanks in advance

    You cannot use PP03 in batch. It is not batch compatible.It uses some control framework which work only if the SAP GUI is active or when it is run in foreground. Use PP02 instead.A workaround of the problem would be to switch off the object manager: Set the ADMINISTRATION OBJMG switch in table T77S0 to X or (to deactivate the object manager for specific users only) proceed according to Note 496718.
    In the medium or long term, SAP recommends that you use Transaction PP02 only. Transaction PP02 is and will be the only transaction that is fully batch-input-compatible (also in future releases).

  • Iw31 -Recording - Runtime error RAISE_EXCEPTION has occured

    Recently We updated Support Pack.
    We already operating a transaction, IW31 through a recording method.
    After Support Pack, We can able to create Order for only one technical object. We cannot able to create Order for other selected Technical Object.
    We tried Recording through Abaper. We got a Run time Error.
    Runtime error RAISE_EXCEPTION has occured
    Any SAP Note to be applied.
    Please suggest.
    Raja

    hi
    check in service market place for the support patch level impact notes in the maintenance and services tab,

  • Runtime Errors TIME_OUT

    guyz,
    i am facing the below issue while running DTP to load the master data attr to info object.
    previoulsy it was working perfect but from last few days its getting hanged and throwing this error.
    also records are very few around 2500.
    dont know why its getting hanged.
    Runtime Errors         TIME_OUT
    Date and Time          10/04/2011 16:35:09
    Short text
         Time limit exceeded.
    What happened?
         The program "SAPLSENA" has exceeded the maximum permitted runtime without
         interruption and has therefore been terminated.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    Error analysis
         After a specific time, the program is terminated to make the work area
         available to other users who may be waiting.
         This is to prevent a work area being blocked unnecessarily long by, for
         example:
         - Endless loops (DO, WHILE, ...),
         - Database accesses with a large result set
         - Database accesses without a suitable index (full table scan)
         The maximum runtime of a program is limited by the system profile
         parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this
          time limit is
         exceeded, the system attempts to cancel any running SQL statement or
         signals the ABAP processor to stop the running program. Then the system
         waits another 60 seconds maximum. If the program is then still active,
         the work process is restarted.
    How to correct the error
        Programs with long runtime should generally be started as background
        jobs. If this is not possible, you can increase the system profile
        parameter "rdisp/max_wprun_time".
        Depending on the cause of the error, you may have to take one of the
        following measures:
        - Endless loop: Correct program;
        - Dataset resulting from database access is too large:
          Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
          (for example);
        - Database has unsuitable index: Check index generation.
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "TIME_OUT" " "
        "SAPLSENA" or "LSENAF01"
        "FLUSH_PACKAGE"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
           Display the system log by calling transaction SM21.
           Restrict the time interval to 10 minutes before and five minutes
        after the short dump. Then choose "System->List->Save->Local File
        (Unconverted)".
        3. If the problem occurs in a problem of your own or a modified SAP
        program: The source code of the program
           In the editor, choose "Utilities->More
        Utilities->Upload/Download->Download".
        4. Details about the conditions under which the error occurred or which
        actions and input led to the error.
    also sometimes when i try to refresh the requests in the manage option of the info object, it doesnt show the previous requests and throws the message
    Refresh of the display terminated because InfoCube/DSO cannot be locked
    Message no. RSM854
    Diagnosis
    InfoProvider 0PROD_CATEG cannot be locked with lock argument RSICCONT.
    System Response
    The display is not refreshed and contains old or incorrect data, that can come from other InfoProviders.
    Procedure
    Check why the sm12 lock is not yet released on the table RSICCONT; Where necessary delete the lock.
    With reproduction of an unauthorized lock, write a message to SAP.
    please guide.
    cheerz,
    raps.

    Dear Raps,
    The program SAPLSENA is the lock handler tool. It is doing
    enqueue/dequeue operations.
    The error should come from the program created running in this dialog
    process and calls the SAPLSENA program to create the lock.
    The problem actually occurs because an application program commits many
    separate calls of DEQUEUE function modules, and thus causes the
    dispatcher queue in the enqueue dispatcher to overflow. Such an
    application program always causes a performance problem. DEQUEUE calls
    are started asynchronously, that is, they normally do not give a
    response, and the calling program continues without waiting time.
    If an overflow of the ENQ dispatcher queue occurs in this case, locks
    are kept forever, and processes that are waiting for an enqueue
    response, will keep hanging.
    Please kindly refer to some notes for more information.
    653996     Analyzing lock situations
    142054     Processes in status stopped ENQ
    97760      Enqueue: Performance and resource consuption
    74141      Resource Management for tRFC and aRFC
    39412      How many work processes to configure
    Please check as well attached note 74141 for RFC load distribution.
    Regards,
    arvind

  • Display Infocube Content produces Runtime Errors = TIME_OUT

    Hi,
    Upon trying to display content of an InfoCube (200 records only), I received the following error:
    Runtime Errors         TIME_OUT                                                     
    Date and Time          13.12.2007 11:16:24                                                                               
    Short text                                                                               
    Time limit exceeded.                                                                               
    What happened?                                                                     
         The program "CL_SQL_RESULT_SET=============CP" has exceeded the maximum        
          permitted runtime without                                                     
         interruption and has therefore been terminated.                                                                               
    Error analysis                                                                     
         After a specific time, the program is terminated to make the work area         
         available to other users who may be waiting.                                   
         This is to prevent a work area being blocked unnecessarily long by, for        
         example:                                                                       
         - Endless loops (DO, WHILE, ...),                                              
         - Database accesses with a large result set                                    
         - Database accesses without a suitable index (full table scan)                                                                               
    The maximum runtime of a program is limited by the system profile              
         parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this  
          time limit is                                                                 
         exceeded, the system attempts to cancel any running SQL statement or           
         signals the ABAP processor to stop the running program. Then the system        
         waits another 60 seconds maximum. If the program is then still active,         
         the work process is restarted.                                                                               
    Trigger Location of Runtime Error                                             
        Program                                 CL_SQL_RESULT_SET=============CP  
        Include                                 CL_SQL_RESULT_SET=============CM006
        Row                                     32                                
        Module type                             (METHOD)                          
        Module Name                             NEXT_PACKAGE                                                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    2 *                                                                       
        3 * Fetches the next bulk of rows into an internal table.                 
        4 *                                                                       
        5                                                                         
        6   DATA:                                                                 
        7     sql_code       TYPE i,                                              
        8     sql_msg        TYPE dbsqlmsg.                                       
        9                                                                         
       10   FIELD-SYMBOLS:                                                        
       11     <line> TYPE ANY,                                                    
       12     <outtab> TYPE STANDARD TABLE.                                       
       13                                                                         
       14                                                                         
       15   IF me->cursor = c_invalid_cursor.                                     
       16 *   result set has already been closed                                  
       17     RAISE EXCEPTION TYPE cx_sql_exception                               
       18       EXPORTING invalid_cursor = 'X'.                                   
       19   ENDIF.                                                                
       20                                                                         
       21 * check that a reference to the output table has been set by            
          22 * a preceeding call of SET_PARAM_TABLE; in this case the attribute  
       23 * LINE_REF contains a reference to a data structure of the          
       24 * table's line type                                                 
       25   IF me->itab_ref IS INITIAL.                                       
       26     RAISE EXCEPTION TYPE cx_parameter_invalid                       
       27           EXPORTING parameter = 'ITAB_REF'.                         
       28   ENDIF.                                                            
       29   ASSIGN me->itab_line_ref->* TO <line>.                            
       30   ASSIGN me->itab_ref->* TO <outtab>.                               
       31                                                                     
    >>>>>   CALL 'C_DB_FUNCTION' ID 'FUNCTION' FIELD 'DB_SQL'                 
       33                        ID 'FCODE'    FIELD c_fcode_next_package     
       34                        ID 'CONNAME'  FIELD me->con_ref->con_name    
       35                        ID 'CONDA'    FIELD me->con_ref->con_da      
       36                        ID 'CURSOR'   FIELD me->cursor               
       37                        ID 'BOUND'    FIELD me->outvals_bound        
       38                        ID 'OUTVALS'  FIELD me->parameters->param_tab
       39                        ID 'OUTTAB'   FIELD <outtab>                 
       40                        ID 'LINE'     FIELD <line>                   
       41                        ID 'UPTO'     FIELD upto                     
       42                        ID 'ROWCNT'   FIELD rows_ret                 
       43                        ID 'SQLCODE'  FIELD sql_code                 
       44                        ID 'SQLMSG'   FIELD sql_msg.                 
       45                                                                     
       46   IF sy-subrc = 0.                                                  
       47 *   some rows fetched                                               
       48     ADD rows_ret TO rows_fetched.                                   
       49                                                                     
       50 *   set the OUTVALS_BOUND flag; this avoids "reassignement" of the  
       51 *   output variables the next time this method is called, i.e. the                                             
    Can someone help me to solve this problem. Thanks!

    Hi,
    Chk the below line from the dump in line 3 - 'Fetches the next bulk of rows into an internal table'
    what that error means is the volume which u r trying to view is beyond the size of the internal table buffer and because of that it is leading to a dump.
    As the previous reply suggests try to increase the size of table buffer which will help you display much larger volumes.
    Selection of fewer columns would be much quicker and easier to analyse data quickly.
    Regards

  • Transaction IA12:ABAP runtime errors:TIME_OUT

    Hi,
    We are executing transaction IA12.We are getting ABAP runtime errors:Time_Out.
    We have searched for a SAP note to sort the issue:SAP Note 607086 - Functional location: Problems when displaying structure list.
    Please suggest what will be the option to solve the issue.
    Thanks.

    Hi,
    searching for the FORM routine where the timeout occurs ("mara_predecessor_f50") and excluding SAP notes that are modification notes or based on the implementation of modification notes, there is only one remaining note
    Note 658930 - Structure list: Configuration not considered with BOM
    for 46C up to Support Package SAPKH46C46.
    If this is still not in your system, the note may be a solution.
    If not, I'm running out of good ideas. Then also the SAP modification notes can be your last option.
    Regards,
    Klaus

  • Portal Runtime Error : An exception occurred while processing a request

    Hello friends,
    After upgradation of my portal to the following patch level, SAP J2EE 6.20:
    <b>Portal Version :</b> EP 6 SP 2 patch 29 hotfix 0
    <b>Content Mgmt and Collaboration  version</b> : 6 SP2 patch 5
    i faced many performance related issues. Portal seems to be <b>very slow</b>. After logging in, most of the time I get 2 errors:
    <b>Either</b>
    <b>1></b> Iview remains blank.
    <b>Or
    2></b> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
    But when I refresh that particular iview, it works fine.
    I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found <b>the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."</b>Aug 18, 2005 6:07:42 PM # PRT-Async 2          Fatal           Exception ID:06:07_18/08/05_0669
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
    Component class : com.sapportals.portal.prt.pom.RootComponentNode
    User : tempuser
            at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
            at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
            at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
            at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
            at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
            at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
            at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
            at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
            at java.lang.Thread.run(Thread.java:479)
    <b>Help needed.(</b>as i am helpless now.)
    Regards,
    Nilz

    Anthony,
      I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
    I created like this
             project-> rightclick->   export-> par ->selecting project-> givint protal password-> and finish.
    The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
    but the par file is  created in the NW studio Navigation bar.
      Let me know any help regarding this
    thanks
    venkat

  • How to resolve this issue in windows 7 ?? "An Internal Virtual Machine error (3) has occurred. The virtual machine will reset now."

    Dear Friends,
    Do kindly help me out on this issues. I have installed Microsoft Virtual PC 2007 in my PC and i am trying to create an new virtual machine for several testing. I have a clean ISO image of windows 7 . I import through Captured ISO option. The system tries
    to configure the OS . But during the configuration i am getting this error. 
    *Your PC needs to Restart.
    Please hold the power button.
    Error Code: 0X0000005D
    Parameters:
    0x03063A09
    0x756E6547
    0x49656E69
    0x6C65746E
    An Internal Virtual Machine error (3) has occured.
    The virtual machine will reset now.
    I have Enabled the virtualization settings in BIOS. 
    Kindly help me out to resolve this issue. 
    Base Machine Platform : Windows 7 - 32 Bit and Windows 7 - 64 Bit.
    ISO Image : windows 7 - 32 bit.

    Error Code:  0x0000005D: Your
    CPU is not compatible.
    Ref : http://www.winvistatips.com/internal-virtual-machine-error-3-has-occurred-t520964.html
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • System error 86 has occurred. The specified network password is not correct. - despite the NTLMv2 fix

    After the Windows 2008 R2 64 bit server got below 2 updates a network share is no longer available. And trying to remap it with correct credentials (that work on a Windows 8.1 64 bit) gives this error: "System error 86 has occurred. The specified network
    password is not correct."
    Local Policies -> Security Options -> Network Security: LAN Manager Authentication Level
    is already set to "LM and NTLM - use NTLMV2 session security if negotiated"
    In fact this is how it was working earlier. And it hasn't been changed.
    Below 2 updates were installed in past few days:
    Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.185.3528.0)
    Update for Windows (KB974405)

    Hi,
    Does the network share a DFS share? If so, please install the hotfix below to check the results.
    You cannot access a DFS share by using a valid user account in Windows Server 2008 R2, in Windows 7, in Windows Vista or in Windows Server 2008
    http://support.microsoft.com/kb/2549311
    Best Regards,
    Mandy 
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • TS3694 I have recently done the update to my iphone and then tried to backup my iphone to itunes and an error meesage has occured and now my phone isn't responding to anything and is stating that it needs to be restored back to manufacturers settings, hel

    I have recently done the update to my iphone and then tried to backup my iphone to itunes and an error meesage has occured and now my phone isn't responding to anything and is stating that it needs to be restored back to manufacturers settings, Can anyone help?

    Hi d_diotte,
    Thanks for using Apple Support Communities.  If you're unable to update your iPhone and keep seeing the "Connect to iTunes" image, this article has some steps you can try:
    iOS: Unable to update or restore
    http://support.apple.com/kb/ht1808
    Cheers,
    - Ari

Maybe you are looking for