SQL error in the database when accessing a table.

Hi,
I got below error at production server. Please suggest how to reslove this error.
<br>
<br>
<br>
Runtime Errors         DBIF_RSQL_SQL_ERROR
<br>
Exception              CX_SY_OPEN_SQL_DB
<br>
Date and Time          02.01.2011 15:55:06
<br>
<br>
<br>
<br>
<br>
Short text
<br>
SQL error in the database when accessing a table.
<br>
<br>
<br>
How to correct the error
<br>
Database error text........: "[10054] TCP Provider: An existing connection was
<br>
forcibly closed by the remote host.
<br>
[10054] Communication link failure"
<br>
Internal call code.........: "[RSQL/INSR/SWFCNTBUF ]"
<br>
Please check the entries in the system log (Transaction SM21).
<br>
<br>
If the error occures in a non-modified SAP program, you may be able to
<br>
find an interim solution in an SAP Note.
<br>
If you have access to SAP Notes, carry out a search with the following
<br>
keywords:
<br>
<br>
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
<br>
"CL_SWF_CNT_FACTORY_SHMEM======CP" or "CL_SWF_CNT_FACTORY_SHMEM======CM001"
<br>
|    "ADD_INSTANCE"         
<br>
<br>
<br>
Information on where terminated
<br>
Termination occurred in the ABAP program "CL_SWF_CNT_FACTORY_SHMEM======CP" -
<br>
in "ADD_INSTANCE".
<br>
The main program was "SAPMSSY1 ".
<br>
<br>
In the source code you have the termination point in line 16
<br>
of the (Include) program "CL_SWF_CNT_FACTORY_SHMEM======CM001".
<br>
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
<br>
procedure "ADD_INSTANCE" "(METHOD)", but it was neither handled locally nor
<br>
declared
<br>
in the RAISING clause of its signature.
<br>
<br>
The procedure is in program "CL_SWF_CNT_FACTORY_SHMEM======CP "; its source
<br>
code begins in line
<br>
1 of the (Include program "CL_SWF_CNT_FACTORY_SHMEM======CM001 ".
<br>
<br>
<br>
<br>
Source Code Extract
<br>
<br>
Line
SourceCde
<br>
<br>
1
METHOD add_instance .
<br>
2
<br>
3
data: ls_id type swfcntbuf.
<br>
4
<br>
5
check buffer method - store in local buffer if necessary
<br>
6
retcode = cl_swf_cnt_factory=>add_instance( ibf_por = ibf_por instance = instance ).
<br>
7
<br>
8
CHECK m_buffer_method EQ mc_buffer_shared.
<br>
9
<br>
10
append key to list of tasks to add stored in database table SWFCNTBUF
<br>
11
will be evaluated by build process for shared memory area (UPDATE_BUFFER method)
<br>
12
<br>
13
ls_id-mandt = sy-mandt.
<br>
14
ls_id-id    = ibf_por.
<br>
15
<br>
>>>>>
INSERT swfcntbuf CONNECTION r/3*wfcontainer
<br>
17
FROM ls_id.
<br>
18
<br>
19
IF sy-subrc EQ 0.
<br>
20
Commit seems to be necessary always, even if INSERT has failed, to get rid of
<br>
21
database locks
<br>
22
COMMIT CONNECTION r/3*wfcontainer.
<br>
23
ENDIF.
<br>
24
<br>
25
ENDMETHOD.
<br>

duplicate here SQL error in the database when accessing a table.
Do not post the same question in more than on forum.

Similar Messages

  • DBIF_RSQL_SQL_ERROR with SQL error in the database when accessing a table.

    dear all,
      i have done a system copy from production server into quality server. quality was scrapped and freshly installed with SAP then used the DB flush method to carry out the system copy. i had to change the DBS_ORA_SCHEMA in environment variables to SAP<SOURCE SID> from SAPSR3. the sap version is ECC6.0,DB is ORACLE10.2 on WIN NT.
      after MMC opened, i get "SQL error in the database when accessing a table" error is coming. in SM21, I am getting "Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000 )
    Database error 8103 at SEL access to table TBTCO
    Run-time error "DBIF_RSQL_SQL_ERROR" occurred
    Database error 8103 at FET access to table TBTCP
    Run-time error "DBIF_RSQL_SQL_ERROR" occurred
    > Short dump "081018 130339 sibqty_Q TY_00 " generated
    Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
    > Short dump "081018 130339 sibqty_Q TY_00 " generated
    Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
    Delete session 001 after error 023
    Database error 8103 at DEL access to table TMSALOGAR
    Run-time error "DBIF_RSQL_SQL_ERROR" occurred
    > Short dump "081018 130432 sibqty_Q TY_00 " generated
    Database error 8103 at FET access to table SNAP
    Run-time error "DBIF_RSQL_SQL_ERROR" occurred
    > Short dump "081018 130432 sibqty_Q TY_00 " generated
    Transaction Canceled SY 002 ( SQL error in the database when accessing a table. )
    Database error 8103 at FET access to table TSP02"
    please find the st22 DUMP:
    ow to correct the error                                                                          |
    Database error text........: "ORA-08103: object no longer exists"
    Internal call code.........: "[RSQL/READ/TBTCO ]"
    Please check the entries in the system log (Transaction SM21).
    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:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "SAPMSSY2" or "SAPMSSY2"
    "INITIATE_JOB_START"
    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.
    The exception must either be prevented, caught within proedure
    "INITIATE_JOB_START" "(FORM)", or its possible occurrence must be declared in
    the
    RAISING clause of the procedure.
    |   
    please do me this favor if you know to avoid this problem..
    thanks a lot..

    Hello Anuj,
    This is because the COUNT(*) is returning a value which is longer than the INT4 data type it is expecting. If you restrict the selection by introducing a WHERE clause, then you won't get the dump:
    DATA: dyn_from    TYPE string,
          dyn_where   TYPE string,
          gx_sql_err  TYPE REF TO cx_sy_open_sql_error,
          gv_text     TYPE string.
    dyn_from  = `DD01L INNER JOIN DD02L ON DD02L~AS4LOCAL = DD01L~AS4LOCAL AND DD02L~AS4VERS = DD01L~AS4VERS`.
    dyn_where = `DOMNAME LIKE 'Z%'`.
    TRY .
        SELECT COUNT(*) FROM (dyn_from) WHERE (dyn_where).
        WRITE: / sy-dbcnt NO-GROUPING.
      CATCH:  cx_sy_open_sql_db             INTO gx_sql_err,
              cx_sy_dynamic_osql_semantics  INTO gx_sql_err,
              cx_sy_dynamic_osql_syntax     INTO gx_sql_err.
    ENDTRY.
    IF gx_sql_err IS BOUND.
      gv_text = gx_sql_err->get_text( ).
      WRITE: / gv_text.
    ENDIF.
    BR,
    Suhas

  • DBIF_RSQL_SQL_ERROR: SQL error in the database when accessing a table

    Hi Gurus,
    Im getting DBIF_RSQL_SQL_ERROR: SQL error in the database when accessing a table error while I was importing support pack in the system. This is ERP 6.0 with EHP4 with MS SQL in back ground and I was applying the BASIS SP 04. It was in the TEST scenario and in the SPDD_SPAU_CHECK phase it threw the error.
    Short text
        SQL error in the database when accessing a table.
    What can you do?
        Note which actions and input led to the error.
        For further help in handling the problem, contact your SAP administrator
        You can use the ABAP dump analysis transaction ST22 to view and manage
        termination messages, in particular for long term reference.
    How to correct the error
        Database error text........: "[601] Could not continue scan with NOLOCK due to
         data movement."
        Internal call code.........: "[RSQL/FTCH/E071 ]"
        Please check the entries in the system log (Transaction SM21).
        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:
        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
        "SAPLSVRT" or "LSVRTU01"
        "TR_LAST_IMPORT_OF_OBJECT"
    SPAM  is ending with the above short dump. I have checked the space availability and it is OK.
    Kindly help.
    Renju Aravind.

    Hi,
    this error is very often seen in case of a database corruptions. Please follow note 142731 and perform a complete database check. Send the results when they show errors.
    Best regards
      Clas

  • Getting error "SQL error in the database when accessing a table."

    Hi All,
    We are getting Dump Error SQL error in the database when accessing a table for the batch job EISSD/REQUISITION 14 / which includes program AQ20FD==========A2============. Please reply. The Dump error details are as follows
    Short text
        SQL error in the database when accessing a table.
    How to correct the error
        Database error text........: "ORA-01555: snapshot too old: rollback segment
         number 21 with name "_SYSSMU21$" too small"
        Internal call code.........: "[RSQL/FTCH/VBRK ]"
        Please check the entries in the system log (Transaction SM21).
    Thanks
    Padmakar Kudtarkar
    Edited by: Rob Burbank on May 19, 2011 9:38 AM

    The query where we are getting error in Standard program AQ20FD==========A2============ for Job
    EISSD/REQUISITION 14 / is as follows:
    select VBRKBUKRS VBRKFKART VBRKFKDAT VBRKFKTYP VBRKGJAHR VBRKKUNAG VBRKKUNRG VBRKKURRF VBRKVBELN VBRKWAERK VBRP~AUBEL
           VBRPAUPOS VBRPFKIMG VBRPKVGR2 VBRPKZWI1 VBRPMATNR VBRPMWSBP VBRPNETWR VBRPPSTYV VBRPVBELN VBRPVGBEL VBRP~VGPOS
           VBRPVKBUR VBRPVKGRP VBRPVRKME VBRPWAVWR
    into (VBRK-BUKRS , VBRK-FKART , VBRK-FKDAT , VBRK-FKTYP , VBRK-GJAHR , VBRK-KUNAG , VBRK-KUNRG , VBRK-KURRF , VBRK-VBELN
         , VBRK-WAERK , VBRP-AUBEL , VBRP-AUPOS , VBRP-FKIMG , VBRP-KVGR2 , VBRP-KZWI1 , VBRP-MATNR , VBRP-MWSBP , VBRP-NETWR
         , VBRP-PSTYV , VBRP-VBELN , VBRP-VGBEL , VBRP-VGPOS , VBRP-VKBUR , VBRP-VKGRP , VBRP-VRKME , VBRP-WAVWR )
    from ( VBRK
           inner join VBRP
           on VBRPVBELN = VBRKVBELN )
           where VBRK~BUKRS in SP$00004
             and VBRK~FKDAT in SP$00001
             and VBRK~KUNAG in SP$00002
             and VBRK~VBELN in SP$00006
             and VBRP~MATNR in SP$00003.
      %dbacc = %dbacc - 1.
      if %dbacc = 0.
        stop.
      endif.
      check SP$00004.
      check SP$00001.
      check SP$00002.
      check SP$00006.
      check SP$00003.
      add 1 to %count-VBRK.
      %linr-VBRK = '01'.
      extract %fg01.
      %ext-VBRP01 = 'X'.
        extract %fgwrVBRP01.
    endselect.

  • Root cause of "SQL error in the database when accessing a table. "

    Dear experts,
    I meet this dump "SQL error in the database when accessing a table" when executing a sql.
    Sql:
        SELECT sesssessno poscrm_serplan_id poscrm_ser_h_id poscrm_ser_i_id
               possolution_id sessbundle_id sessdbid sessinstno pos~crm_ordered_prod
               sessdbid sessinstno
          INTO CORRESPONDING FIELDS OF TABLE et_sess_list
          FROM dsvassessadmin AS sess JOIN service_posn_sm AS pos
            ON possession_id     = sesssessno
          FOR ALL ENTRIES IN lt_contractno
          WHERE sess~contractno = lt_contractno-contract_no
           AND sess~status IN lt_status_range
           AND bundle_id IN lt_bundle_id
           AND pos~solution_id GT 0
    This sql works well in dev system SD7, however, it causes dump in another dev system "SMV".
    Can anyone give me any ideas?
    Thanks

    Hi Jovito,
    This is info from ST22
    Short text
        SQL error in the database when accessing a table.
    What can you do?
        Note which actions and input led to the error.
        For further help in handling the problem, contact your SAP administrator
        You can use the ABAP dump analysis transaction ST22 to view and manage
        termination messages, in particular for long term reference.
    How to correct the error
        Database error text........: "SQL0101N The statement is too long or too
         complex. SQLSTATE=54001"    Internal call code.........: "[RSQL/OPEN/DSVASSESSADMIN ]"
        Please check the entries in the system log (Transaction SM21).
        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:
        "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
        "CL_AGS_SERVICE_SERV===========CP" or "CL_AGS_SERVICE_SERV===========CM018"
        "GET_OVS_SESSION_LIST"
        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.
        The exception must either be prevented, caught within proedure
        "GET_OVS_SESSION_LIST" "(METHOD)", or its possible occurrence must be declared
         in the
        RAISING clause of the procedure.
        To prevent the exception, note the following:
    It seems that after translation the native sql is too long. But I think this can be solved.

  • Inbound-Queue SYSFAIL: SQL error in the database when accessing a table

    Hi,
    we send around 80 IDoc simultaneously, there 15 are stuck.
    They all have SYSFAIL in SMQ2 with message: SQL error in the database when accessing a table
    I already unlocked the queues and try to resend. Nothing happend!
    I ran RSQIWKEX for the single queus but now there are new queues in Status SYSFAIL.
    I already checked some entries in forum and blogs, but nothing worked out yet!
    Can someone help?! it's urgent!!
    br

    Hi, well as mentioned i searched and found this already.
    But in ST22 i got error concerning
    Laufzeitfehler         DBIF_RSQL_SQL_ERROR
    Ausnahme               CX_SY_OPEN_SQL_DB
    So i guess it's something more serious.
    Any more ideas?!
    Can i simply delete the stucked queues and reporcess them?!
    br

  • Loading issue : Error: sql error in the database while accessing a table

    Hello,
    where as one of the DTP in the process chain failed due to  *Error: sql error in the database while accessing a table*, where as in the short dump it showing as Transaction log of data base is full., but i checked the data base space in DB02, more space is available . once we run the same DTP by manually its successful. its not through  any errors.
    could u please help me out solve the problem.
    Thanks
    siva kumar.

    it might be a lock. do you drop index before loading?
    the database might be full at the moment of loading and not later if many loadings happen at the same time on the same system...
    when you then rerun your dtp manually, it can go through as it's perhaps the only one running at that moment...
    you can try to set the btch parameter to 1...this will help in some cases.
    M.

  • SQL error occurred in the database when acces

    Dear All,
    I am getting following error message while doing file to file scenario.
    source side messages are pickedup and entering into the Queues .receiver side i cant able to see any souce messages.
    SYSFAIL Message is showing in the Queues when i was double click that message its giving following message.
    SQL error occurred in the database when acces
    a table.
    Plz, help me in this regard.
    Thanks,
    Mahesh

    Hi Mahesh,
    Did you get a chance to check the IPC log directories
    Also usually for a sysfail message you can check the smw01
    You will see a bdoc with status F05. What does it say there?
    or
    Is it "Scheduled for outbound processing" or "recorded for outbound processing".
    I guess the message has not been processed, so the next step is to go to transaction SMQ2, and check for info as to why it is not processed.
    If you see a queue status of SYSFAIL, first try resetting it to "Ready" again. If it still fails then, delete that particular LUW. And if you still have some more messages in the queue just click the unlock queue button.
    Reward points if this helps
    Regards
    Pragathi.

  • Error ODS activation - sql error when accessing a table.

    Hi,
    sometimes occurs an error by activation ODS. I have proces chain and when is loaded second packet an error occurs. In monitor>>
    -RSMPC 128, datapacket 3 is wrong, with status number 9
    -RSMPC 131
    -RSDRO 108 - communcation error (sql error when accessing a table)
    In sm21>
    -sql error when accessing a table
    -The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was  
    either                                                      caught nor passed along using a RAISING clause, in the procedure <b>"UPDATE_ATAB"</b>   "(FORM)"                                                                    
    Since the caller of the procedure could not have expected this exception     
       to occur, the running program was terminated.                               
      The reason for the exception is:                                             
      The database system recognized that your last operation on the database      
      would have led to a deadlock.                                                
      Therefore, your transaction was rolled back                                  
      to avoid this.                                                                       
      ORACLE always terminates any transaction that would result in deadlock.      
      The other transactions involved in this potential deadlock                   
      are not affected by the termination.
    I have BW 3.5.
    Thank You very much.

    There are a few different scenarios that I can think of where this might come up that all involve what might resulting in parallel (concurrent)processes:
    Loading packets in parallel - that is there are X number of processes loading packets concurrently. This could be set in your IMG settings system wide or in the InfoPackage for just this datasource.   You seem to indicate that you don't have this.
    Database parallel processing - RSAMDIN - ORA_PARALLEL_DEGREE ( there was a different RSADMIN parm for older versions - forget what SP the change came with).
    You have multiple InfoPackages for the datasource, each loading what should be a different range of data, and they run atthe same time.
    You could be loading from two different datasources to the ODS at the same time.
    If any of these are true, I would look at bumping the INITRANS setting up.  Your DBA will probably need to do this for table and its indices.  There is a Note - 831234 that allows you to create a parameter in RSADMIN that will specify a INITRANS value (e.g. 20) rather than using the default. The ODS would need to be activated to pick this new setting up for the table to be altered. 
    You could also look at the Processing settings for the InfoPackage and change to PSA first, then target to see if that helps. 
    Or if you are loading from two different datasources at the same time, you might adjust your schedule so that doesn't happen.
    Pizzaman

  • TS2518 Help, I had aperture open and working on a image and did not have a battery in and bumped the power off. As a result it will not open my master, it is locked. when I try to open that Library  it says There was an error opening the database for the

    Help, I had aperture open and working on a image and did not have a battery in and bumped the power off. As a result it will not open my master, it is locked. when I try to open that Library  it says There was an error opening the database for the library. I have tried every thing. I updated the other libr but now it will not open the main to update. What do I do?

    Try starting Aperture with the command and option keys held down.  You'll get 3 options.
    Try each, starting at the top, in order, checking after each to see if it fixes the issue.

  • Error message in TRFC 'An SQL error occurred when accessing a table'

    Hi all,
    Can any one tell what this below error message is about in while go into TRFC
    'An SQL error occurred when accessing a table'.
    and please tell me how to solve this problem.

    Hi
    Try to see what all tables are accessed by data source. and see if there is any lock on that..
    If some other job is accessing that table - then there might be lock on that which is causing failure..
    1) Try looking at ST22 dump also..
    2) Try to do RSA3 in R/3 and if see if its is fetching any records or not..
    Hoep it helps
    --SA

  • Error in the module RSQL accessing the database interface

    I have written the following query.
    SELECT  a~no
             a~hist_no
             a~chk_stat
             a~chk_date
             a~user as chk_user
             b~name as chk_by
             into corresponding fields of table hist
             from zhist as a INNER JOIN zuser as b on
             auser = bbname
             where pspnr = v_pspnr
             and   chk_no = v_chk_no.
    I am getting the dump "Error in the module RSQL accessing the database interface".
    Please provide me the solution.
    Thanx,
    Selva.

    Hi,
    As i have analysed your query in that you are putting the data in the internal table 'hist' which is also a standard structure and if you check in SE11 'hist' is the standard structure for 'Tablespace History' and might be because of that it is causing the problem.
    Kindly check by changing the name of the internal table to tt_hist and then try.
    I think that will solve the problem.
    Regards,
    Harsh Goel

  • When I try to open my aperture library, I get the message "There was an error opening the database for the library "/Users/alyssabouma/Pictures/Aperture Library.aplibrary". help!

    When I try to open my Aperture Library, I get this message: "There was an error opening the database for the library “/Users/alyssabouma/Pictures/Aperture Library.aplibrary”.
    I have already uninstalled and reinstalled the library....Help!!

    lyssalou,
    what is your Aperture version and what is your MacOS X version?
    What happened, before this problem occurred? Did you import images, install software, move the Aperture library?
    I have already uninstalled and reinstalled the library....Help!!
    What do you mean by reinstalling the library? Did you reinstall Aperture?
    You might start the trouble shooting with using the Aperture Library First Aid Tools - repairing the permissions, repairing the library, and rebuilding, if necessary, see:
    Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library
    Before rebuilding the library, make a backup of the Aperture Library, if you do not have one.
    Regards
    Léonie

  • When I try to open aperture (which has been working fine for months), I get this response: There was an error opening the database for the library "~/Pictures/Aperture Library.aplibrary". Please help!!

    When I try to open aperture (which has worked great for months), I get this response:
    There was an error opening the database for the library “~/Pictures/Aperture Library.aplibrary”.
    Please help!! Thank you!! =)

    Sonny3300, your signature says "Aperture 2" - is that correct? Then you need this trouble shooting guide:
    Aperture 2: Troubleshooting Basics: http://support.apple.com/kb/HT2945
    What is your Operating system version and where is your library located? Have imported new images recently or changed the location of your library?
    Regards
    Léonie

  • When i try to open aperture, i get a box popup that says;  Warning-There was an error opening the database for the library "~/Pictures/Aperture Library.aplibrary".

    When i try to open aperture, i get a box popup that says; 
    Warning-There was an error opening the database for the library “~/Pictures/Aperture Library.aplibrary”.
    Can anyone help? I cannot accesss aperture. this is the 1st time this has ever happened...
    thanks,

    Try running a repair on the library. Hold the command and option keys down while starting Aperture, this will open the repair window. Select Repair Library.
    See Aperture 3: Troubleshooting Basics
    If you still have problems post back

Maybe you are looking for

  • How to display selection screen of logical database on a screen

    Hi Experts, I create a screen 100, how do I display a selection screen of logical database on this screen. Thanks! Anthony

  • Abstract classes and static methods

    I have an abstract report class AbstractReportClass which I am extending in multiple report classes (one for each report, say ReportA, ReportB, ...). Each report class has its own static column definitions, title, etc., which I have to access through

  • Game Help, please?

    I downloaded Bejeweled for my iPod using my mom's account (which is verified on my computer) and it says I'm not authorized to play the game, yet I can still listen to music downloaded from her account. Any idea how to fix this? Any help would be gre

  • Material autorization in requisition order

    Hi, I want to restrict autorization to use a material in a requisition order. What I have to do to make the user authorized or not creating a purchase order for this material..? Thanks for your reply.. Rgards,

  • Problem with LoadVars and stopping/playing

    I've got a flash movie set up online that isn't working properly. The details are this: the movie has two frames, the first being a blank loading frame meant to keep anything from being displayed till the variables are delivered by my PHP script, and