OPEN DATAST DUMP

Hi,
i use this code for open dataset and i have dump in bold line
  OPEN DATASET file_n FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
  LOOP AT it_d INTO wa_it.
    TRANSFER wa_it TO file_n.
  ENDLOOP.
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_FILE_OPEN_MODE', was not
caught, which
led to a runtime error. The reason for this exception is:
The system tried to access the file "C:\Documents and
Settings\user\Desktop\CSV\xx.TXT" but found that this file was
not opened. For this reason, it could not access the file.
what can be the problem?
Regards

hi alvro ,
Thanks,
i try to write in gui download but the problem is
that when i open the file i have lot of space between rows of table
like line 50 empty rows and after anther line ,
becouse that the file is huge
how i can avoid that?
i think it because of table in bold.
TYPE-POOLS:truxs.
types truxs_t_text_data(4096) type c occurs 0.
DATA: da_tab TYPE truxs_t_text_data.
CALL FUNCTION 'SAP_CONVERT_TO_CSV_FORMAT'
EXPORTING
i_field_seperator = ';'
i_appl_keep = 'X'
TABLES
i_tab_sap_data = it_d
CHANGING
i_tab_converted_data = da_tab
EXCEPTIONS
conversion_failed = 1
OTHERS = 2.
CALL METHOD cl_gui_frontend_services=>gui_download
EXPORTING
filename = file_n
filetype = 'BIN'
append = 'X'
codepage = 'UTF-8'
CHANGING
data_tab =  da_tab
EXCEPTIONS
file_write_error = 1
no_batch = 2
Regards

Similar Messages

  • Open dataset dump.

    hi guys,
    I am getting OPEN DATASET SHORTDUMP using below code.
    can somebody suggest me alteration of code..
    Dump says error in READ statement.
    DATA : BEGIN OF IT_EDIT OCCURS 0,
             CNO(5)         TYPE C,
             DATE(8)        TYPE C,
             VENDOR(10)     TYPE C,
             MATERIAL(18)   TYPE C,
             STARTDT(8)     TYPE C,
             ENDDT(8)       TYPE C,
             QUANTITY(13)   TYPE N,
           END OF IT_EDIT.
    OPEN DATASET P_INFILE FOR INPUT IN TEXT MODE ENCODING DEFAULT.
      DO.
        IF NOT SY-SUBRC IS INITIAL.
          EXIT.
        ELSE.
    <b>      READ DATASET P_OUFILE INTO IT_EDIT.</b>
          APPEND IT_EDIT.
        ENDIF.
      ENDDO.
      CLOSE DATASET P_OUFILE.
    Regards
    Chandra.

    hi,
    pls chk this sample code.
    report zfiles_0001.
    Parameters: d1 type localfile default '/usr/sap/TST/SYS/Data1.txt',
                d2 type localfile default '/usr/sap/TST/SYS/Data2.txt'.
    data: itab type table of string.
    data: wa type string.
    start-of-selection.
    Read file
      open dataset d1 for input in text mode.
      if sy-subrc = 0.
        do.
          read dataset d1 into wa.
          if sy-subrc <> 0.
            exit.
          endif.
          append wa to itab.
        enddo.
      endif.
      close dataset d1.
    Copy to new file
      open dataset d2 for output in text mode.
      loop at itab into wa.
        transfer wa to d2.
      endloop.
      close dataset d2.
    Delete the first
      delete dataset d1.
    regards
    anver
    if hlpful pls mark points

  • Opening screen dumps

    I've created a series of screen dumps for a project I'm working on, and I use Appleworks 6.2 to open and edit them with its paint program.
    To open one, I use "Painting" as my document type, and "All Available" for the file format. This is fine for the occasional file, but when I have a lot of them to open, it gets tedious when I have to click on this options every single time.
    I'm just wondering if there's any way to keep those options as a default setting, at least until I'm finished with this project.
    Thanks.

    Open the Script Editor in the /Applications/AppleScript/ folder and run the following:
    tell application "Finder"
    repeat with A in (get selection)
    tell application "AppleWorks 6"
    open (A as alias) as document type painting document
    end tell
    end repeat
    end tell
    Select all the screen captures in the Finder, and press the Run button in the Script Editor.
    (22992)

  • Open PO / SA Dump in SAP 4.7

    Hi All,
    Please suggest which is the best way to take open PO dump. open Pos are to be converted in to new POs with new material master. which is the best option pls let me know. 4.7 sap
    ME2M - WE101 - alv grid OR  can we take dump form any tables ?

    closed

  • Short dump while scheduling infopackage

    Hi,
    im getting short dump while scheduling infopackage  for( 0cfm_init_positions )as it is giving  dump like MESSAGE_TYPE_X runtime error in BI test system but in dev it's working fine if anybody knows how to resolve??.

    hi
    this is due to existence of TRFC-Packages for old failed requests in the source system.
    so for this QM-Action in the request monitor change manually to red.
    if you wont find the solution contact basis team.
    or
    use SE16. Look at RSSDLINIT table. Match up the LOGSYS with your OLTPSOURCE (for the infopackage that is causing the problem). Delete that line(s) Now you can open the infopackage. (be sure to delete the initialization) before you run the info pack again.)
    Also you can check SAP Note : 852443
    check this links
    Short dump MESSAGE_TYPE_X while trying to open infopackage
    DUMP IS COMMING WHILE CREATING INFOPACKAGE

  • Itunes makes my screen go BLACK and restart- will not work at all!

    hello fellow apple distressers,
    hoping someone can help me as i would really appericiate it:):)!
    everytime i try and open itunes my computer freezes then the screen goes black. after the screen goes black the computer restarts all on its own! when i log back into windows, after it has restarted, it tells me it has recovered from a +serious error+. when i searched for more information it gave me this error signature:
    BCCode : 100000ea BCP1 : 8A1357A8 BCP2 : 8A0AD290 BCP3 : F78BACB4
    BCP4 : 00000001 OSVer : 512600 SP : 3_0 Product : 768_1
    i have tried uninstalling and reinstalling itunes annnddd quicktime, but still itunes refuses to co-operate, although funnily enough quicktime does work....
    please help as i really need itunes to upload songs on to my ipod.
    Btw, this happened after a virus and although this virus has been removed from the computer i think it may have damaged the itunes files:(
    thanking you for reading this,
    lovelifesmilepeace

    wow blue screen of death that sounds bad...
    Technically they're called STOP messages (because the PC stops after you get one of them). But "blue screen of death" (or BSOD) is the common terminology (because the PC stops after you get one of them).
    C:\DOCUME~1\Abigail\LOCALS~1\Temp\\WERfd36.dir00\Mini012710-01.dmp
    Good ... we've got the PC generating minidumps of the crashes. So we'll be able to interrogate those using Windows debugging tools to try to work out what is causing the crash.
    First, track down where they are being stored on the PC. Usually that will be in the C:\Windows\Minidump\ directory. There should be files in there with names like "Mini(number-numbers).dmp"
    (If you have "Hide filename extensions for known file types" enabled in Windows, the ".dmp" extension may not appear on the dump files. The numbers in the file name will be different for each minidump, if minidumps are present.)
    Once you've found where they're being stored, we'll have a look at them using windbg.
    1. Download and install the Windows debugging tools from here:
    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    2. Go to Start, All Programs, Debugging Tools For Windows, Windbg
    Once you open Windbg, you will presented with a blank screen.
    3. Click on "File > Symbol File Path". Here you will enter the symbols
    path. Symbols are needed to effectively debug.
    The path will be:
    SRVc:symbolshttp://msdl.microsoft.com/download/symbols
    4. Enter in this path and click OK. Now, go to "File > Save Workspace"
    so that your symbols path is saved for future use.
    5. Go to "File > Open Crash Dump" and load the file.
    (An "Open Crash Dump" screen will appear ... doubleclick "My Computer", doubleclick "Local Disk", doubleclick "Windows", doubleclick "Minidump", and doubleclick on one of the minidumps in there.)
    You will/should get a message to save base workspace information. Choose no.
    Now you will get a debugging screen. It takes a little bit to run it,
    as the symbols have to be downloaded as they are needed.
    After the "bugcheck analysis" part of the screen comes up, look for the component that seems to be causing the crash. (It'll say "Probably caused by" ...)
    Let us know the precise name of the component. (Include any file name extensions like .dll or .sys.)
    If you can, have a look at several of your crash dumps. Are all the crashes being caused by the same component? If not, could you let us know the names of the various components being cited in the various crash dumps?

  • Error while installing NW7.3 ABAP for DB2 on z/OS Install DB CLI driver

    Dear Experts,
    i'm installing for the first time NW7.3 ABAP for DB2 on z/OS with AIX application server. Central Services was installed succesfull but next step Install Database on AIX stoped with error (establishConn.log):
    db2radm (release: "720", patch level: "000", version: "Jan 14 2012") begin:28.02.2012 10:54:39
    This is db2radm release: "720", patch level: "120", version: "Jan 14 2012".
    This is db2radm setting up DB2 Connect.
    Message file is /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log.
    db2radm called as: /usr/sap/DW8/SYS/exe/uc/rs6000_64/db2radm -m db2i -P 456 -L DW8DDF -S DW88 -H s10d1 -u SAPADM -p ******** -W primary_only -l /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log
    Adjusting environment
      dbs_db2_ssid=DW88
      SAPDBHOST=s10d1
      dbs_db2_user=SAPADM
      dbs_db2_schema=SAPADM
      dbs_db2_schema8=1
      dbs_db2_pw=********
    Checking environment
      DB host    = s10d1
      SSID       = DW88
      SAPSYSTEMNAME = DW8
    DB2Trc:    000000 CLI_ALLOC_ENV 1
    connect.ini file used: 'connect.ini.for.db2radm'
    Fail over connection list of this application server:
    NAME       = DW88_on_s10d1             
    USER       = SAPADM                    
    PASSWORD   = <***>                     
    SCHEMA     = SAPADM                    
    PS         = SAP0907U                  
    LOCATION   = DW8DDF                    
    SSID       = DW88                      
    HOST       = s10d1                     
    PORT       = 456                       
    RETRY_CNT  = 3                         
    SLEEP_TIME = 0                         
    DB2Trc: trace level of dbdb2cli set to 1
    COLLECTION ID used is "SAP0907U"
    DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W  There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD.  SQL
    use lib_dbsl for DB2 version V9.
    Callback functions for dynamic profile parameter registered
    DbSl library successfully loaded.
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    SQL DRIVER VERSION is "09.07.0003"
    DB2Connect driver identified as THIN CLIENT
    Now I'm connected to DW88_on_s10d1
    DB2 DBMS version 09.01.0005
    DB2 LOCATION name DW8DDF
    (HYB): Info: Using OLD dbsl support.
    DB2 connect shared library loaded successfully.
    09.07.0003DB2Connect driver identified as THIN CLIENT
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
    DBSLHA: Using new Failover Support
    DBSLHA: Using user(  SAPADM) and password(<pwd>) from profile.
    DBSLHA:
    DBSLHA:Connection List
    DBSLHA:
    DBSLHA:NAME      |HOST      |SSID|COLLECTION  |PLAN    |PORT             |SCHEMA  |OWNER   |LOCATION  |RETRY|SLEEP|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM  |SAPADM  |DW8DDF    |00003|00000|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    GetHaProfile: GetHaProfile: found 1 connections in connection profile.
    GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1  in connection profile
    connection profile /usr/sap/DW8/SYS/global/connect.ini opened.
    >>>>>> dump of connection profile
    ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000
      [DEFAULT_GROUP]
      CON1=DW88_on_s10d1
      [DW88_on_s10d1]
      SSID=DW88
      HOST=s10d1
      PORT=456
      LOCATION=DW8DDF
    <<<<<< end of dump of connection profile
    ssid DW88 found in connection profile, section DW88_on_s10d1.
    >>> analyse line:  * ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000
    >>> analyse line:  [DEFAULT_GROUP]
    >>> analyse line:  CON1=DW88_on_s10d1
    >>> analyse line: 
    >>> analyse line:  [DW88_on_s10d1]
    section DW88_on_s10d1 found.
    >>> analyse line:  SSID=DW88
    >>> analyse line:  HOST=s10d1
    >>> analyse line:  PORT=456
    >>> analyse line:  LOCATION=DW8DDF
    >>> analyse line:  section DW88_on_s10d1 found and data matches.
    backup connection profile /usr/sap/DW8/SYS/global/connect.ini .
    switch connection profile /usr/sap/DW8/SYS/global/connect.ini .
    check for adapted connection profile.
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
    DBSLHA: Using new Failover Support
    DBSLHA: Using user(  SAPADM) and password(<pwd>) from profile.
    DBSLHA:
    DBSLHA:Connection List
    DBSLHA:
    DBSLHA:NAME      |HOST      |SSID|COLLECTION  |PLAN    |PORT             |SCHEMA  |OWNER   |LOCATION  |RETRY|SLEEP|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM  |SAPADM  |DW8DDF    |00003|00000|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    GetHaProfile: GetHaProfile: found 1 connections in connection profile.
    GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1  in connection profile
    ssid DW88 found in connection profile, section DW88_on_s10d1.
    check for adapted connection profile passed.
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
    DBSLHA: Using new Failover Support
    DBSLHA: Using user(  SAPADM) and password(<pwd>) from profile.
    DBSLHA:
    DBSLHA:Connection List
    DBSLHA:
    DBSLHA:NAME      |HOST      |SSID|COLLECTION  |PLAN    |PORT             |SCHEMA  |OWNER   |LOCATION  |RETRY|SLEEP|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM  |SAPADM  |DW8DDF    |00003|00000|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    GetHaProfile: GetHaProfile: found 1 connections in connection profile.
    GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1  in connection profile
    WARNING: schema with 8 bytes length allowed; shadow upgrate will not work
    dbs/db2/use_accounting != 1 -> DB2 accounting is switched off
    dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used
    dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on
    dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off
    DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini
    DBSLHA: Using new Failover Support
    DBSLHA: Using user(  SAPADM) and password(<pwd>) from profile.
    DBSLHA:
    DBSLHA:Connection List
    DBSLHA:
    DBSLHA:NAME      |HOST      |SSID|COLLECTION  |PLAN    |PORT             |SCHEMA  |OWNER   |LOCATION  |RETRY|SLEEP|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    DBSLHA:DW88_on_s1|s10d1     |DW88|SAP<DB2Conne|        |                 |SAPADM  |SAPADM  |DW8DDF    |00003|00000|                                                                               
    DBSLHA:--|||||||||-|---|                                                                               
    SQL DRIVER VERSION is "09.07.0003"
    DB2Connect driver identified as THIN CLIENT
    DB2Trc: 00 000000 cli_get_cli_driver_bld_level 1 s101006
    SQL DRIVER NAME is "libdb2.a"
    SQL DBMS NAME is "DB2"
    SQL DBMS VERSION is "09.01.0005"
    DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"
    The bind is skipped since collection for ssid DW88 is already bound.
    To force the bind, use option "-B force".
    DB2TRC: 0000000000 00      000000   CLI_DISCONNECT
    DB2TRC: 0000000000 00      000000   CLI_FREE_DBC 1
    DB2TRC: 0000000000 00      000000   CLI_FREE_ENV 1
    DB VERSION is 09.01.0005.
    Starting Grants .
    DB2Trc:    000000 CLI_ALLOC_ENV 1
    COLLECTION ID used is "SAP0907U"
    DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W  There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD.  SQL
    Connecting to <DW88_on_s10d1> on connection 0 ...
    Now I'm connected to DB2 (09.01.5)
    SQL DRIVER NAME is "libdb2.a"
    SQL DBMS NAME is "DB2"
    SQL DBMS VERSION is "09.01.0005"
    DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"
    New functions of DB2 V9 are switched on
    Profile parameter dbs/db2/cli_trace_dir is not set
    dbdb2dic.c 1709 INFO    Profile: SDB2_DEBUG=<UNSET>                                                                           
    dbdb2dic.c 1733 INFO    Envrmnt: sdb2_debug=<UNSET>                                                                           
    dbdb2dic.c 1733 INFO    Envrmnt: SDB2_DEBUG=<UNSET>                                                                           
    DB2 Call 'CLI_EXECUTE' Error: sqlcode = -204 : [IBM][CLI Driver][DB2] SQL0204N  "SAPADM.#LOBU" is an undefined name.  SQLSTATE=42704
    dbdb2dic.c 2251 INFO    rc=103,sqlcode=-204: ExeRead                                                                          
    dbdb2dic.c 1709 INFO    Profile: dbs/db2/max_retry=<UNSET>                                                                    
    dbdb2dic.c 1733 INFO    Envrmnt: DB2_MAX_RETRY=<UNSET>                                                                        
    dbdb2dic.c 1709 INFO    Profile: dbs/db2/retry_on_924=<UNSET>                                                                 
    dbdb2dic.c 1733 INFO    Envrmnt: DB2_RETRY_ON_924=<UNSET>                                                                     
    dbdb2dic.c 1709 INFO    Profile: dbs/db2/no_retry_on_10=<UNSET>                                                               
    dbdb2dic.c 1733 INFO    Envrmnt: dbs_db2_no_retry_on_10=<UNSET>                                                               
    dbdb2dic.c 1733 INFO    Envrmnt: DBS_DB2_NO_RETRY_ON_10=<UNSET>                                                               
    DB2 Call 'SQLEndTran' Error: sqlstate = 08003 : [IBM][CLI Driver] CLI0106E  Connection is closed. SQLSTATE=08003
    [dbdb2dic.c  1873:rc=99: COMMIT WORK failed]
    dbdb2dic.c 1873 ERROR   rc=99: COMMIT WORK failed                                                                             
    [dbdb2dic.c  2019:rc=99,sqlcode=268435455: ExecDDL failed (DB error)]
    dbdb2dic.c 2019 ERROR   rc=99,sqlcode=268435455: ExecDDL failed (DB error)                                                    
    DB2 Call 'SQLEndTran' Error: SQLCODE = -99999 : [IBM][CLI Driver] CLI0106E  Connection is closed. SQLSTATE=08003
    ROLLBACK failed with SQL error '-99999'
    ERROR: couldn't connect to DB
    rc = 99
    error message returned by DbSl:
    rc=99,sqlcode=268435455: ExecDDL failed (DB error)
    DB2RADM EXITCODE: 12
    db2radm finished (0012)
    db2radm stop:28.02.2012 10:54:39
    i've patched db2radm and sapinst to the latest version.
    May be i should manually create "SAPADM.#LOBU"?
    Please help to solve these issue.
    Best regards,
    Alexander V

    Hi ,
    Please check if Note 1581637 - Installing a System with DB2CODEPAGE other than the default is useful.
    Award points if useful.
    Thanks,
    Ravi

  • Computer shuts down when I click on the list or grid display button

    I've uninstalled an reinstalled 3 times and instead of the computer shutting down when I start itunes as it was doing, it only does it when I click on the display as a list, grid or cover display button. However it seems to unistall some parts at the same time as I can't open it all afterwards (error message says its not installed). This started to occur after a couple of weeks of non use and when I last used it I purchased songs from itunes. I now have current version but didn't when it first statred to happen. Help!!

    Okay ... we'd better have a closer look at the minidumps the PC has been producing to see if they can turn up any additional information on what we're dealling with here.
    Open "My Computer", and see if you can find a directory called C:\Windows\Minidump. (That's where minidumps usually go on a PC, so long as the Systemroot hasn't been set to some other folder.)
    If it's been collecting minidumps, there should be files in there with names like "Mini(number-numbers).dmp"
    (If you have "Hide filename extensions for known file types" enabled in Windows, the ".dmp" extension may not appear on the dump files. The numbers in the file name will be different for each minidump, if minidumps are present.)
    Once we've tracked down some minidumps, we can have a go at analysing them.
    1. Download and install the Windows debugging tools from here:
    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    2. Go to Start, All Programs, Debugging Tools For Windows, Windbg
    Once you open Windbg, you will presented with a blank screen.
    3. Click on "File > Symbol File Path". Here you will enter the symbols
    path. Symbols are needed to effectively debug.
    The path will be:
    SRVc:symbolshttp://msdl.microsoft.com/download/symbols
    4. Enter in this path and click OK. Now, go to "File > Save Workspace"
    so that your symbols path is saved for future use.
    5. Go to "File > Open Crash Dump" and load the file.
    (An "Open Crash Dump" screen will appear ... doubleclick "My Computer", doubleclick "Local Disk", doubleclick "Windows", doubleclick "Minidump", and doubleclick on one of the minidumps in there.)
    You will/should get a message to save base workspace information. Choose no.
    Now you will get a debugging screen. It takes a little bit to run it,
    as the symbols have to be downloaded as they are needed.
    After the "bugcheck analysis" part of the screen comes up, look for the component that seems to be causing the crash. (It'll say "Probably caused by" ...)
    Let us know the precise name of the component. (Include any file name extensions like .dll or .sys.)
    If you can, have a look at several of your crash dumps. Are all the crashes being caused by the same component? If not, could you let us know the names of the various components being cited in the various crash dumps?

  • Apple iTunes 10.0.1 = BSOD in Windows 7

    Okay! I always upgrade to the latest version of software, chiefly as a test bed for others with whom I consult. I have been running Windows 7 since it was released (well before actually ).
    I have never ever had a BSOD for any reason on ANY of my Windows 7 machines. Until today. I upgraded iTunes from 10.0.68 to 10.0.1, and now, as I navigate around iTunes, I either get a program has stopped working and will be closed message, or the BSOD. The BSOD message, high flyover is the error was in Memory_Management.
    Here are my computer specs:
    Model: HP Pavilion DV6756
    OS: Windows 7 64-bit
    Memory: 3 Gigabytes
    CPU: Intel Centrino
    Anyone else having as much fun as I am?

    I see the system has been saving memory dumps for the crashes. With any luck, if we interrogate the dump files with the 64-bit version of WinDbg, we can track down the component causing the crash.
    1. Download and install the 64-bit version of Windows debugging tools from here:
    http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx
    2. Go to Start, All Programs, Debugging Tools For Windows, Windbg
    Once you open Windbg, you will presented with a blank screen.
    3. Click on "File > Symbol File Path". Here you will enter the symbols
    path. Symbols are needed to effectively debug.
    The path will be:
    SRVc:symbolshttp://msdl.microsoft.com/download/symbols
    4. Enter in this path and click OK. Now, go to "File > Save Workspace"
    so that your symbols path is saved for future use.
    5. Go to "File > Open Crash Dump" and load the file.
    (An "Open Crash Dump" screen will appear ... navigate to C:\Windows\MEMORY.DMP\, or C:\Windows\Minidump\, and doubleclick on one of the dump files there.)
    If you get a dialog at this point saying you don't have permission to open the file, try this: OK out of the permission warning dialog. Right-click on the dump file (In the "Open Crash Dump" screen), and select "Properties". Click the "Security" tab. Click the "Advanced" button. Click "Continue". Check the "Include inheritable permissions from this object's parent" checkbox, and click OK. Click Yes when the Windows security box comes up. Close the "properties" screens at this point, and go back to "Open Crash Dump", and try doubleclicking on the dump file again.
    You will/should get a message to save base workspace information. Choose no.
    Now you will get a debugging screen. It takes a little bit to run it,
    as the symbols have to be downloaded as they are needed.
    After the "bugcheck analysis" part of the screen comes up, look for the component that seems to be causing the crash.
    Let us know the precise name of the component. (Include any file name extensions like .dll or .sys.)
    If you can, have a look at several of the dumps that seem to be associated with the BSODs. Are all the crashes being caused by the same component? If not, could you let us know the names of the various components being cited in the various crash dumps?

  • HELP!!! I am trying to save data in a spreadsheet

    I have tried several things but can not get this, should be pretty simple.
    1) I have a loop which sends command and read serail buffer and parse data. This works fine and my program is 3 seconds behind my actual device. Now I want to save the data I parse out in a spreadsheet but only every minute becasue my program will be running for 8 hours. Do you guys think that Excel would be handel such a big matrix.
    my data is something like this:
    I am receiving the day of the year which is 338 as string. the time which is also a string but updates as my loop is running which is approximately 3 seconds behind my actuall hardware shows but thats not a problem because I acutally want to save the data rather than viewing purpos
    e.
    2) If some one can show me a approach where user is asked to save-as file option (where to save the file) when I am start my loop when I am actually sending command and receving data and parsing data and if the file exist already then name another file.
    3) the format I want to put my data to spreadsheet is as:
    day-time (actual number)
    01 70
    02 80
    03 90
    04 76
    so on untill i read 36 channels and their corresponding temperatues. Next time i append the next data set after a minutes should look like:
    day-time day-time
    01 70 01 72
    02 80 02 81
    03 90 03 95
    04 76 04 78
    36 90 36 98
    this would be a pretty big metrix if i append data every minute and my program would run for 8 hours.
    As I mentioned I want to save the data only every minutes while my program acquiring data every 3 seconds. Thanks for your help

    Hi,
    My name is Michel Carrière, from montreal.
    I save directly to excel large amounts of data all the time. My first solution is a VI called "SAVE TO EXCEL". With this subroutine, you can open excel dump data and save your file.
    Secondly, I have a small VI that acquires data and saves it when I want, check it out. ("WattmetreHP_1CHAN_V2.vi")
    Attachments:
    SAVE_TO_EXCEL.zip ‏53 KB
    WattmetreHP_1CHAN_V2.vi ‏298 KB

  • MySQLDump and Batch Files

    Hello all,
    I've been using the mysql connector package to populate and retrieve data from a mysql database. Two questions. First, I have recently become very fond of the mysqldump feature attached with the mysql package. Is there a way to call somthing like that from my connector module? ... or any other mysql "-esque" commands for that matter? (ie show tables, show create table someTable) ...
    I know that the first command I issue is actually a "USE myDatabaseName" to point the connector module at the correct databse. If the USE command is a mysql command, then I'm lead to believe that commands like SHOW will also be legit. However, what would the return structure be? ... would that also be some kind of ResultSet?
    Anyway the other question would be about the execution of batch files like the ones a mysqldump command would generate. I know that I am able to open the dumped text file and populate and run the commands via the methods:
    addBatch(String sql)throws SQLException // to populate
    executeBatch() // to run.. but is there a method that already does that?
    Thanks in advance
    -Curt

    Hi,
    Try Runtime.getRuntime().exec("batchfile.bat");
    Check out Class Runtime for more info.
    -adam

  • Import the table with 0 rows

    Hi
    I have a problem to import a dump that contains the tables with 0 rows.
    When i exported from ORACLE 11.2 64 bit on SERVER 2008 i noticed that log didn't confirm the tables with 0 rows.
    When i want to import to ORACLE 11.2 64 bit on other SERVER 2008 i have a lot of errors on this tables with 0 rows.
    In the log i get the same tables with 1 row at least, but no one with 0 rows.
    I open my dump in TEXTPAD and i see it contains "CREATE ....." these tables.
    I don't understand why it happens. I used FUll DUMP by SYS, it didn't help.
    This is not first time when i export and import dumps,no errors.
    I'm using command "EXP" and "IMP" and every time it's ok.(IF it's a releavent)
    Why it happens? any solutions for this issue?
    Thanks

    I've found (i guess so) solution to this issue
    here are two links to this new feature that is called deffered segment creation
    The reason for this behavior is 11.2 new feature ‘Deferred Segment Creation‘ – the creation of a table sent is deferred until the first row is inserted.
    As a result, empty tables are not listed in dba_segments and are not exported by exp utility
    http://www.nativeread.com/2010/04/09/11gr2-empty-tables-skipped-by-export-deferred-segment-creation/
    http://antognini.ch/2010/10/deferred-segment-creation-as-of-11-2-0-2/
    And this is i've found in official documentation from oracle
    Beginning in Oracle Database 11g Release 2, when creating a non-partitioned heap-organized table in a locally managed tablespace, table segment creation is deferred until the first row is inserted. In addition, creation of segments is deferred for any LOB columns of the table, any indexes created implicitly as part of table creation, and any indexes subsequently explicitly created on the table.The advantages of this space allocation method are the following:A significant amount of disk space can be saved for applications that create hundreds or thousands of tables upon installation, many of which might never be populated.Application installation time is reduced.There is a small performance penalty when the first row is inserted, because the new segment must be created at that time.
    To enable deferred segment creation, compatibility must be set to '11.2.0' or higher. You can disable deferred segment creation by setting the initialization parameter DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override the setting of the DEFERRED_SEGMENT_CREATION initialization parameter.
    +Note that when you create a table with deferred segment creation (the default), the new table appears in the _TABLES views, but no entry for it appears in the SEGMENTS views until you insert the first row. There is a new SEGMENTCREATED column in _TABLES, _INDEXES, and _LOBS that can be used to verify deferred segment creation+
    Note:
    The original Export utility does not export any table that was created with deferred segment creation and has not had a segment created for it. The most common way for a segment to be created is to store a row into the table, though other operations such as ALTER TABLE ALLOCATE EXTENTS will also create a segment. If a segment does exist for the table and the table is exported, the SEGMENT CREATION DEFERRED clause will not be included in the CREATE TABLE statement that is executed by the original Import utility.

  • BSOD when iPod is connected

    I use Windows Vista and the latest version of iTunes. I have a 30gb iPod 5th gen.
    I have always used Winamp to sync music onto my iPod but on my old PC I had to install iTunes, after this it told me to restore my iPod, so I did, and then everytime I plugged it in I would restore, then it would ask me to restore again. This was on XP. I have since bought a new Vista PC and plugged in my iPod, I formatted it through Windows and when it came up in iTunes I restored it. Now whenever I plug it into the USB port I get the BSOD and an "0x00000007f" error.
    Help is much appreciated.

    Thank you kindly, adam. Although it didn't give us a name of a component, that screen indicated that the PC has been collecting dumps of the crashes, which indicates a way forward.
    First we'd better check to see if the PC has been collecting minidumps (rather than other forms of memory dump.
    Go Start and click "Computer".
    Doubleclick "Local Disk" (Usually it's your C: drive.)
    Doubleclick "Windows".
    Is there a folder called "Minidump" in there? If so, doubleclick on that.
    Are there files in there called "Mini(number-numbers).dmp"?
    (If you have "Hide filename extensions for known file types" enabled on the PC, the ".dmp" extension may not appear on the dump files. The numbers in the file name will be different for each minidump, if minidumps are present.)
    If you can track down where the minidumps are being located, next we'll use WinDbg (Windows Debugging tools) to interrogate the minidumps to see if that turns up the name of a component (or components).
    1. Download and install the Windows debugging tools from here (If you've got a 64-bit Vista, use the 64-bit version of the tools):
    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    2. Go to Start, All Programs, Debugging Tools For Windows, Windbg
    Once you open Windbg, you will presented with a blank screen.
    3. Click on "File > Symbol File Path". Here you will enter the symbols
    path. Symbols are needed to effectively debug.
    The path will be:
    SRVc:symbolshttp://msdl.microsoft.com/download/symbols
    4. Enter in this path and click OK. Now, go to "File > Save Workspace"
    so that your symbols path is saved for future use.
    5. Go to "File > Open Crash Dump" and load the file.
    (An "Open Crash Dump" screen will appear ... doubleclick "Computer", doubleclick "Local Disk", doubleclick "Windows", doubleclick "Minidump", and doubleclick on one of the minidumps in there.)
    *If you get a dialog at this point saying you don't have permission to open the file, try this:* OK out of the permission warning dialog. Right-click on the minidump file (In the "Open Crash Dump" screen), and select "Properties". Click the "Security" tab. Click the "Advanced" button. Click "Continue". Check the "Include inheritable permissions from this object's parent" checkbox, and click OK. Click Yes when the Windows security box comes up. Close the "properties" screens at this point, and go back to "Open Crash Dump", and try doubleclicking on the minidump again.
    You will/should get a message to save base workspace information. Choose no.
    Now you will get a debugging screen. It takes a little bit to run it,
    as the symbols have to be downloaded as they are needed.
    After the "bugcheck analysis" part of the screen comes up, look for the component that seems to be causing the crash. (It'll say "Probably caused by" ...)
    Let us know the precise name of the component. (Include any file name extensions like .dll or .sys.)
    If you can, have a look at several of your minidumps for iPod-connection-related-crashes (fingers crossed, the date-and-time-created for the minidump files, or the numbers in the filename of the minidumps which indicate the date of the crash, might be able to allow you to identify the ones associated with plugging in the iPod). Are all the crashes being caused by the same component? If not, could you let us know the names of the various components being cited in the various crash dumps?

  • DBase Driver problems

    I have been using Crystal for about 15 years, mostly producing reports from FoxPro tables.  Over the years, the drivers would periodically get broken and eventually fixed. 
    The application was stuck on 8.5 for years for a couple of reasons.  IT WORKED, and Crystal 9+ changes required application changes.  With Crystal 2008, I finally convinced the client we had to change.
    Most of the simple reports ported successfully with no significant changes.  However, the same cannot be said for the complex reports.  200 page reports that used to take about a minute to produce now fail with 'Unexpected error' or 'memory error' after 10-15 minutes, or they may actually work sometimes after several minutes.  Forget about producing reports that are 2000 pages!
    The reports have been rewritten to work in smaller pieces, and through the viewer I am able to simulate paging by swapping files between 'groups' of pages.  This seemingly works, but the errors pop up again when trying to export the 'groups' to PDF files. 
    My question is this:  Does anyone know of older xbase drivers that work better?  I've noticed posts that suggest there are ones out there that may be better.  I am using crdb_p2bxbse 12.0.0.683.
    At some point in my testing I've tried modifying the reports to use the ADO drivers instead.  This was somewhat successful, but not overwhelmingly.
    I'm about to downgrade back to working code (Crystal 8.5 based), but don't really want to do that.  Any other suggestions

    Hi Steven,
    That's a serious amount of memory leaking. Go to Microsofts WEB site and download a tool called : DebugDiag.
    Run it and set it for Memory leaks and Handles and select your EXE. When the app crashes Debug will generate a dump file. You can then open the dump file using this same tool. It should show where the memory leak is and in which component.
    Next we need to know what reporting engine are you using? RDC, RAS, CRPE32 or OCX etc.?
    If it does not or it's not obvious where the leak is I suggest you purchase a support incident and have a dedicated engineer take the case. If you do add a note and have the case assigned to me, I have access to all our source and drill into where the issue may be. If it's an issue I can track it to get resolved.
    Have you tried a simple report to see if it also has issues? I'm curious if it's report complexity or the amount of data being returned.
    Thank you
    Don

  • Computer will not recognise ipod and crashes computer

    Working on windows xp, I have reset the ipod but it will not come up on the side bar, therefore I cannot download music, instead it just turns off the computer.
    I am lost somebody please help!!!!!!!

    Sorry I haven't a clue re the computer it was made to my spec.
    Fair enough. Okay, we'll try analysing minidumps of the crash with Windows Debugging Tools to see if that can tell us which component or driver is causing the issue.
    Open "My Computer", and see if you can find a directory called C:\Windows\Minidump. (That's where minidumps usually go on a PC, so long as the Systemroot hasn't been set to some other folder.)
    If it's been collecting minidumps, there should be files in there with names like "Mini(number-numbers).dmp"
    (If you have "Hide filename extensions for known file types" enabled in Windows, the ".dmp" extension may not appear on the dump files. The numbers in the file name will be different for each minidump, if minidumps are present.)
    Once we've tracked down some minidumps, we can have a go at analysing them.
    1. Download and install the Windows debugging tools from here:
    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
    2. Go to Start, All Programs, Debugging Tools For Windows, Windbg
    Once you open Windbg, you will presented with a blank screen.
    3. Click on "File > Symbol File Path". Here you will enter the symbols
    path. Symbols are needed to effectively debug.
    The path will be:
    SRVc:symbolshttp://msdl.microsoft.com/download/symbols
    4. Enter in this path and click OK. Now, go to "File > Save Workspace"
    so that your symbols path is saved for future use.
    5. Go to "File > Open Crash Dump" and load the file.
    (An "Open Crash Dump" screen will appear ... doubleclick "My Computer", doubleclick "Local Disk", doubleclick "Windows", doubleclick "Minidump", and doubleclick on one of the minidumps in there.)
    You will/should get a message to save base workspace information. Choose no.
    Now you will get a debugging screen. It takes a little bit to run it,
    as the symbols have to be downloaded as they are needed.
    After the "bugcheck analysis" part of the screen comes up, look for the component that seems to be causing the crash. (It'll say "Probably caused by" ...)
    Let us know the precise name of the component. (Include any file name extensions like .dll or .sys.)
    If you can, have a look at several of your crash dumps. Are all the crashes being caused by the same component? If not, could you let us know the names of the various components being cited in the various crash dumps?

Maybe you are looking for

  • Capturing HD video directly into my computer using HDD Cam & FCE 3.5

    I have a JVC Everio GZ-HD7. Unfortunately, I didn't realize how "crappy" these HDD cams can be, in time to be able to return it. It records in 4GB sections, which is bad for me because I record at a studio and I can't have songs being cut off all the

  • Report for login and logout time

    Dear All, Please can some one help me urgently. I have to find out users login and logout time over the last six months. I need to find out how many hours per user are being used.  What report do I need to run to find out ?

  • BlobDomain to File and Reverse

    Hi, I need to create a java.io.File from oracle.jbo.domain.BlobDomain and need also to reverse the operation, the files should be in the server, and its not UploadedFile a code like this: Blob to File public static File blobDomainToFile(BlobDomain bl

  • Logiacal path deactivate in IDOC

    Dear Sir, We are doing the hardware migration project. hence we have  installed new SAP system in new H/W and completed the data migration from  production system. Now we are in the testing phase, so we would like to disable the entry temporarily in

  • Sort Icon/option in ALV tree repot using classes and methods

    Hi all, I have done an alv tree report using the class cl_gui_alv_tree and i need to let users re-sort the report by using a sort icon(as visible in a normal alv report).Is there any possibility to create an icon and set the functionality such that t