Dump when running macro
Hello Folks,
I have a alert creation macro in my planning book, the moment I run the macro it gives a dump. In ST22 transaction I get the name of run time error as "SAPSQL_INVALID_FIELDNAME".
The same macro works fine in my dev system properly without any issue, the issue given here does not work only in the Quality system. Looks like the SAP system generates a internal program where this dump is caused.
The abap'er could not debug the issue much as this is a internally created program.Some more details of the error are given below.
Runtime Errors SAPSQL_INVALID_FIELDNAME
Exception CX_SY_DYNAMIC_OSQL_SEMANTICS
procedure "SELID_GET"
contained field name "SEL_ZCPRODUCT" does not exist
Any kind of pointers to resolve this will be appreciated.
Regards,
Vasudevan
hi all ,
When u run consistency check for one planning area 1, then the internal table reflects the structure of first Planning Area, if u try running macro belonging to PA2 then there is dump becasue the internal table has the structure of the PA1.
This was due to the Table: /SAPAPO/TSAREATE (which has the internal table names of the planning area) having the same table for two plannig areas.
While one Planning area inconsistency was run it corrected for the existing planning area, affecting the other to work.
To rectify this delete one of the planning area table entry form table /SAPAPO/TSAREATE (for the inconsistent planning area) & then run the consistency check. This will create a new table for the second planning area and there will be no conflict.
That will give a permanent soultion.
Hope this helps.
Cheers
Anand
Similar Messages
-
ABAP dump when running an ALV report in a portal
Hi,
I have an ABAP report created in SAP R/3 4.7. Am using the ALV function module REUSE_ALV_GRID_DISPLAY to display the output. The programs runs correctly when run in R/3 using the SAP GUI.
When the report is run in the portal, I get a runtime error 'MESSAGE_TYPE_X'.
Please let me know if anybody has faced such issues.
I checked the OSS note 702732 which talks about increasing the threshold value of the start parameter. But this is not agreed by the BASIS team.
Thanks,
Best regards,
Ajith
The ST22 error log is as follows:
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
Short text of error message:
Data volume (84.550.400 bytes) is too large. (abap/alvgrid/size_nodod_mb
Technical information about the message:
Diagnosis
You tried to send a data record to the front-end that contains
84.550.400 bytes. However, the data volume is restricted to
52.428.800 bytes.
System Response
The running application program was terminated with a runtime
error.
Procedure
Restrict the data selection if possible or contact your system
administrator.
Procedure for System Administration
You can set the maximum size of these data volumes using the kernel
parameter 'abap/alvgrid/size_nodod_mb' (in megabytes).
Message classe...... "S>"
Number.............. 890
Variable 1.......... "84.550.400"
Variable 2.......... "52.428.800"
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"MESSAGE_TYPE_X" C
"SAPLAWRT" or "LAWRTU22"
"ITS_CHECK_ALV_DATA_SIZE"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Information on where terminated
The termination occurred in the ABAP program "SAPLAWRT" in
"ITS_CHECK_ALV_DATA_SIZE".
The main program was "Z_BW_RECON_INV_RPT ".
The termination occurred in line 25 of the source code of the (Include)
program "LAWRTU22"
of the source code of program "LAWRTU22" (when calling the editor 250).
Source code extract
000010 FUNCTION ITS_CHECK_ALV_DATA_SIZE.
000020 *"
000030 ""Lokale Schnittstelle:
000040 *" IMPORTING
000050 *" REFERENCE(DATA_TABLE) TYPE TABLE
000060 *"
000070
000080 data n type i.
000090 data currsize type i.
000100 statics maxsize type i.
000110 data par_value(56).
000120 if maxsize is initial.
000130 sy-subrc = 0.
000140 CALL 'C_SAPGPARAM' ID 'NAME' FIELD 'abap/alvgrid/size_nodod_MB'
000150 id 'VALUE' field par_value.
000160 if sy-subrc ne 0.
000170 maxsize = 52428800. " Default 50 MB
000180 else.
000190 maxsize = 1048576 * par_value.
000200 endif.
000210 endif.
000220 describe table data_table lines n.
000230 currsize = sy-tfill * sy-tleng.
000240 if currsize gt maxsize.
> message x890(s>) with currsize maxsize.
000260 endif.
000270 ENDFUNCTION.HI,
This is a Memory problem.
System is allocated with a Max Memory of 50 MB,(see the dump code, in the last it is hardcoded in the std code)
The data of your report is coming around 83 MB.
Restrict your selection criteria of the Object and run the same report and see. it will work.
Regards,
Anji -
Core dump when running the Proc Application
I have client that has decided to upgrade from Oracle 10g to Oracle11g version. Presently the client code is compiled with Oracle version 11.1.0.7. We have tuxedo version as 9.0 patch02. When running the ProC application, I am getting the core dump. The stack trace for dump is as follows :-
core 'core' of 7784: bp_Customer -C dom=KenanFX -g 5 -i 225 -u dsesun10 -U /users/denver/pc
ffffffff6e8d9bbc kill (2, ffffffff7ffe002c, 1, ffffffff7de3b9a0, ffffffff7ffe0028, ffffffff7e10b5a0) + 8
ffffffff7d27b1f4 skgesigCrash (ffffffff7ffe09a8, ffffffff7e10a070, 1a0c00, ffffffff7dfdbc40, d60a7c, 1) + 34
ffffffff7d27b81c skgesig_sigactionHandler (ffffffff7d6fb9a0, ffffffff7ffe1800, ffffffff7ffe0990, ffffffff7e10b578, ffffffff7ffe0998, ffffffff7ffe09a8) + dc
ffffffff6e8d62e0 __sighndlr (b, ffffffff7ffe1800, ffffffff7ffe1520, ffffffff7d27b740, 0, a) + c
ffffffff6e8c9e44 call_user_handler (ffffffff75f00200, ffffffff75f00200, ffffffff7ffe1520, 8, 0, 0) + 3e0
ffffffff6e8ca03c sigacthandler (0, ffffffff7ffe1800, ffffffff7ffe1520, ffffffff75f00200, 0, ffffffff6ea3c000) + 54
--- called from signal handler with signal 0 (SIGEXIT) ---
ffffffff7c24bb24 sqlrlc (ffffffff7e0f9fc0, 0, 60, c0, 4, 8) + 4
ffffffff7c253594 sqlbrl (ffffffff7e0f9fc0, 1004bc630, 1004bc658, 1004bc5d0, ffffffff7ffe1b30, 2) + 114
ffffffff7c2745ec sqlhvdsc (1004bc5c0, ffffffff7e0f9fc0, 8, ffffffff7fff27a0, 0, 1d676b0) + ac
ffffffff7c274e68 sqlshv (c, 0, e, 0, f, 1c) + 128
ffffffff7c25bd8c sqlsel (ffffffff7fff27a0, 1002d0850, 1002d0d80, 1, ffffffff7e0f9fc0, ffffffff7dd09d70) + 38c
ffffffff7c24ed18 sqlcmex (1, ffffffff7ffe1e80, 0, c, 1002d0850, 0) + 278
ffffffff7c24f724 sqlcxt (0, ffffffff74fd3800, ffffffff7fff27a0, ffffffff74e5d3e4, 16400, 0) + 44
ffffffff74c65aec selectCMF_XIDDB (788, 16450, 2, ffffffff74fbb978, ffffffff7fff4344, ffffffff7971de60) + f14
ffffffff79f5743c bp_AccountFind (0, 0, 1002b6118, 1002b6118, 1002b6118, 1002b6118) + 137c
000000010001748c commonServiceWrapper (30, 0, 558, 1, 100140428, ffffffff6fa08560) + cac
000000010001d1a4 I_AccountFind (100188220, 12336c, 2e60, 100186b80, ffffffff7fffa440, ffffffff6fa08560) + ec
ffffffff7f25ea34 _tmsvcdsp (100186b80, 0, 1001f7b60, 800, 100186b80, 1400) + 11ac
ffffffff7f28241c _tmrunserver (2bb4, 0, 100186b80, 10017c480, 10017d5a0, 0) + 11ac
ffffffff7f25d47c _tmstartserver (1, 2c00, 100144c90, 800, 10017ebe0, 1001444e0) + 1ac
0000000100014e4c main (1b, ffffffff7fffab18, ffffffff7fffabf8, ffffffff6e84b8e0, ffffffff75b05200, ffffffff75f00200) + 14
0000000100014d9c _start (0, 0, 0, 0, 0, 0) + 17c
Can you please help what is causing problem in the applications. Thanks in advanced.This forum is about C programming in general, and about using Oracle Studio C in particular.
Your question seems to be about a database application that now crashes when run on an updated version of Oracle database.
You mention "Proc" and ProC". If you are referring to the Pro*C compiler, that would also be a database question, since the Pro*C compiler is not related to Oracle Studio or Oracle Studio C.
You are more likely to find a helpful answer in a database programming forum. Start here:
https://forums.oracle.com/forums/category.jspa?categoryID=18 -
Short dump when running EWA report
Dear Expert,
I got error dump when generating EWA report: OBJECTS_OBJREF_NOT_ASSIGNED_NO
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_GUI_GP=====================CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "IF_GRAPHIC_PROXY~EXPORT" "(METHOD)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
Missing RAISING Clause in Interface
Program CL_GUI_GP=====================CP
Include CL_GUI_GP=====================CM017
Row 1
Module type (METHOD)
Module Name IF_GRAPHIC_PROXY~EXPORT
Trigger Location of Exception
Program CL_GUI_GP=====================CP
Include CL_GUI_GP=====================CM017
Row 19
Module type (METHOD)
Module Name IF_GRAPHIC_PROXY~EXPORT
Please advise asap since we need the report immediately.
Thank you in advance,
RudiHi,
[This note|https://websmp109.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=944541&_NLANG=E] will solve your problem.
feel free to revert back.
--Ragu -
Hi All,
I have a z-report which displays a ALV report. when I run this in background it gets canceled. when i see the log , it has dump and dump is as shown below.
A RAISE statement in the program "CL_GUI_CONTROL================CP" raised the exception condition "CNTL_ERROR".
Since the exception was not intercepted by a superior
program, processing was terminated.
What could be the problem, suggest me a solution if i have to add some code into my program or is it an application error which can be solved by SAP Notes.
Regards
Divakar Goud,Are you using GUI_UPLOAD or GUI_DOWNLOAD in the report then they will not work there.
Use OPEN DATASET instead to read or write.
Also, check weather there is a Container for OO ALV on the Report then use Docking Containe when SY_BATCH = 'X'.
If its an normal ALV then Change the GRID to LIST layout for Backgroud. Its not that we cannot display grid in background we can do that but we require some layout handling there.
ALV Grid in background job?
Regards,
Amit
Reward all helpful replies. -
Program giving dump when run in background
Hi All,
I have an ALV report in which I am using REUSE_ALV_GRID_DISPLAY.
The report works perfectly in foreground. But when I execute in background I am getting dump.
Dump details are given below.
ShrtText
Unable to fulfil request for 134217728 bytes of memory space.
What happened?
Each transaction requires some main memory space to process
application data. If the operating system cannot provide any more
space, the transaction is terminated.
What can you do?
Try to find out (e.g. by targetted data selection) whether the
transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again
If the error persists, ask your system administrator to check the
following profile parameters:
o ztta/roll_area (1.000.000 - 15.000.000)
Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000)
Amount of memory per user in extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000)
Amount of memory (malloc) for all users of an application
server. If several background processes are running on
one server, temporary bottlenecks may occur.
Of course, the amount of memory (in bytes) must also be
available on the machine (main memory or file system swap).
Caution:
The operating system must be set up so that there is also
enough memory for each process. Usually, the maximum address
space is too small.
Ask your hardware manufacturer or your competence center
about this.
In this case, consult your hardware vendor
abap/heap_area_dia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each dialog process.
Parameters for background processes:
abap/heap_area_nondia: (10.000.000 - 1.000.000.000)
Restriction of memory allocated to the heap with malloc
for each background process.
Other memory-relevant parameters are:
em/initial_size_MB: (35-1200)
Extended memory area from which all users of an
application server can satisfy their memory requirement.
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
More main memory area was requested.
However, all the available space has been used up.
Possible reasons:
- Many (large) internal tables.
- Many (large) programs active.
- Deep nesting of subroutines with a lot of local data.
Can you please help on this ?Hi,
Check you code properly.
The dump is because of an infinite loop which is running when you run the program in background and it is keeping appending or inserting the same table.
Check teh same.
regards,
Ankur Parab -
ABAP Dump when running S_ALR_87100205 (RFHABU00N)
Hi,
We are implementing New GL for a company code in Turkey. When I trying to run the report RFHABU00N for non-leading ledger, I am getting an abap dump because the program is not able to report the output for non-leading ledger documents. The report outputs correct information when executed for the leading ledger.
has any one else faced this issue in the past and if so how was it resolved.
We are currently on SAP ECC 6.04.
Thanks,
NitinHi,
What is the dump message exactly? Anyway, for execution of this report for non-leading ledger, please, consult the following notes:
1883338 - RFHABU00N Long runtimes and termination
1965855 - RFHABU00/RFHABU00N: General Ledger View
1965562 - SAPDBBRF: Fiscal year not correctly delimited for non-leading ledgers
1939154 - RFHABU00N: Documents from non-leading ledgers ignored
Regards,
Eli -
Dump when run J2I5 - Excise Registers Extraction
Hi,
When we run the J2I5 - Excise Registers Extraction (with Register RG23D), it is giving the run time error The ABAP/4 Open SQL array insert results in duplicate database records.
This error is showing after 04.08.2009 to till date..But before till 03.08.2009, it is working file...
What should be the problem????Hi,
Check notes:
965938 J2I5 extraction gives a dump for RG23D
957105 Short Dump while extracting RG23D register in J2I5
842079 Additional changes to NCCD,ECS - J2I5
1087108 RG23D:Short dump and timeout error in j2i6.
1094202 DUMP while cancelling the download of register RG23D in 46C
Regards,
Eli -
Dump when run Report RPTQTA00 - Generate Absence Quotas
Hi,
I run a report RPTQTA00 - Generate Absence Quotas. when we execute it, a runtime error display.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLHRP3" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "/1PAPA/FEAT000BIMAP " in
include "/1PAPA/FEAT000BIMAP " in
line 0:
"The program "/1PAPA/FEAT000BIMAP" is not Unicode-compatible, according"
" to its program attributes."
The include has been created and last changed by:
Created by: "DDIC "
Last changed by: "SAP* "
Error in the ABAP Application Program
The current ABAP program "SAPLHRP3" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Pl. help...thanks dear..
Please let me know, in Object Name, what should i insert...my program name or subroutine name where check of unicode not ticked.
My Program Name -
RPTQTA00
Subroutine -
/1PAPA/FEAT000BIMAP
plz help -
Hi,
I am using some functions under the Report Generation toolkit (LabView 7.1). We recently updated our test PCs from Office 2000 to 2003. The "WORD IMPORT MODULE.VI" returns error code -41113 when used with Word 2003. No problem on Word 2000.
In fact even the example VI available under Find Examples - Run Macro on Word Table fails and returns error code -41113 when "WORD IMPORT MODULE.VI" is called on Word 2003. Word 2000 is OK.
Any one faced this problem???? Any solution to this problem??
I would greatly appreciate your feedback / suggestions.
Thanks,
Mimdarren,
thanks for your reply.
After checking the the property "Trust access to Visual Basic Project" , I get the following error message:
Exception occured in Microsoft Word, Unable to run the specified macro. Help Path is C:\Program Files\Microsoft Office\OFFICE11\1033\wdmain11.chm and context 37401 in Word Run Macro.vi->SetFirstRowAsTableHeaderforWord(Macro).vi->Generate Report.vi
I can run the macro directly from Word.. no problem running macros in Excel dirently either. I get error message only when running macro from LabView. So, I doubt if it is an IT issue.
You don't have a problem with Word 2003 and Word Import Module.vi???
I am attaching my Vi-Report Generation.vi and the subvi. I would so much appreciate if you run ReportGenerate.vi on your PC and let me know if there is a problem.
Many Thanks for your help.
Mim
Attachments:
ReportGeneration.zip 75 KB -
Error "Not all data could be changed in LC" when running DP macro
We are getting the error, "Not all data could be changed in LC" when running DP macros and we are not sure why. It seems to only happen when we are executing it via a Process Chain but not using the DP background processing scheduling. Does anyone know why this is happening?
Hi Stacy,
I hope you are seeing this in message spool. This message comes up for various reasons. We used to see a message saying "No data saved".
Some of the reasons could be " the new value (lets say 3 ) after the macro execution is same as after execution (3)".
See if some of the values are fixed and could not be changed.
I would take a selection id with just few values and execute the job for that selection id and compare the pre and after results. That should answer all your questions. -
Runtime Error -GETWA_NOT_ASSIGNED when running COI
Hi ALL,
We are getting run time error - GETWA_NOT_ASSIGNED when running COI tasks.
Error analysis
You attempted to access an unassigned field symbol
(data segment 32995).
This error may occur for any of the following reasons:
- You address a typed field symbol before it is set using ASSIGN
- You address a field symbol that points to a line in an internal table
that has been deleted
- You address a field symbol that had previously been reset using
UNASSIGN, or that pointed to a local field that no longer exists
- You address a global function interface parameter, even
though the relevant function module is not active,
that is it is not in the list of active calls. You can get the list
of active calls from the this short dump.
How to correct the error
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"GETWA_NOT_ASSIGNED" C
"CL_UC_COI_ACT_PT==============CP" or "CL_UC_COI_ACT_PT==============CM00P"
"REDUCE_GOODWILL_ENTRIES"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Information on where terminated
The termination occurred in the ABAP program "CL_UC_COI_ACT_PT==============CP"
in "REDUCE_GOODWILL_ENTRIES".
The main program was "UCUWB000 ".
The termination occurred in line 722 of the source code of the (Include)
program "CL_UC_COI_ACT_PT==============CM00P"
of the source code of program "CL_UC_COI_ACT_PT==============CM00P" (when
calling the editor 7220).
702 call method do_inv_net_change->create_data_reference
703 exporting
704 i_type = cl_uc_coi_inv_net=>gc_ref_pt_block
705 io_model = do_model
706 importing
707 er_data = lr_t_data.
708 assign lr_t_data->* to <lt_share_block>.
709 call method do_inv_net_change->get_block
710 importing
711 et_pt_shares = <lt_share_block>.
712
713 create data lr_s_data like line of <lt_share_block>.
714 assign lr_s_data->* to <ls_share_block>.
715 * change due to selling invor's transaction
716 read table <lt_share_block> into <ls_share_block> index 1.
717
718 * direct shares prior to divestiture
719 assign component 'R_TH_DSH_OLD'
720 of structure <ls_share_block> to <lr_th_dsh_old>.
721 assign <lr_th_dsh_old>->* to <lt_dsh_old>.
>>>> create data lr_s_data like line of <lt_dsh_old>.
723 assign lr_s_data->* to <ls_dsh_old>.
724 assign component ucf6_cs_coi_fld-pcnt1
725 of structure <ls_dsh_old> to <pcnt1_7a>.
726
727 * change of direct shares in divestiture
Please provide your suggestions.
Edited by: VM2727 on Feb 10, 2012 3:27 AMOr even these ones:
SAP Note 1480856 - C/I: Program termination GETWA_NOT_ASSIGNED
Symptom
When you execute the consolidation of investments, a program termination
occurs (short dump GETWA_NOT_ASSIGNED in the method CREATE_OCI_LIST of the
class CL_UC_COI_ACT).
Note 1467924 - Termination GETWA_NOT_ASSIGNED in CL_UC_COI_ACT_PD
Symptom
When you execute the consolidation of investments, the program termination GETWA_NOT_ASSIGNED occurs in the method CALC_NET_INCOME_MEM of the class CL_UC_COI_ACT_PD. -
Opening Excel Workbook Fails when run from Scheduled Task on Windows Server 2008 Rw
Hi,
I have a little vbs script that instantiates the Excel.Application object and then opens a work book to perform some tasks on it. The script runs fine when run from the command line. When I attempt to run it as a scheduled task (it is supposed to update
data that is pulled from a SQL Server at regular intervals), it fails with the following error:
Microsoft Office Excel cannot access the file 'c:\test\SampleWorkbook.xlsm'. There are several possible reasons: .....
The file does exist. The path reported in the error is correct. The account under which the task is running is the same account I use to run it from the command line. User Account Control is not enabled, and the task is set up to run with highest privileges.
When I run the same script through the Task Scheduler from a Windows Server 2003 machine, it works without issue.
I was just wondering if somebody on this forum has run into a similar issue in connection with Windows Server 2008 R2 and figured out what the magic trick is to make it work. I'm sure it is rights related, but I haven't quite figured out what which rights
are missing.
Thanks in advance for any advice you may have.This is truly killing me ... trying to get it working on Windows Server 2012 without success.
I desperately need to automate running Excel macros in a "headless" environment, that is non-interactive, non-GUI, etc.
I can get it to work using Excel.Application COM, either via VBScript or Powershell, successfully on many other Windows systems in our environment - Windows Server 2008 R2, Windows 7 (32-bit), etc., -BUT-
The two servers we built out for running our automation process are Windows Server 2012 (SE) - and it just refuses to run on the 2012 servers - it gives the messages below from VBScript and PowerShell, respectively-
I have tried uninstalling and re-installing several different versions of Microsoft Excel (2007 Standard, 2010 Standard, 2010 Professional Plus, 32-bit vs. 64-bit, etc.), but it makes no difference.
Would be extremely grateful if any one out there has had any success in running Excel automation on Server 2012 in a non-interactive environment that they could share.
( I have tried adding the "%windir%\syswow64\config\systemprofile\desktop"
folder, which did fix the issue for me when testing on Windows Server 2008 R2, but sadly did not resolve it on Windows Server 2012 )
[VBScript error msg]
Z:\TestExcelMacro.vbs(35, 1) Microsoft Office Excel: Microsoft Office Excel cannot
access the file 'Z:\TestExcelMacro.xlsm'. There are several possible reasons:
• The file name or path does not exist.
• The file is being used by another program.
• The workbook you are trying to save has the same name as a currently open work
[Powershell error msg]
Exception calling "Add" with "0" argument(s): "Microsoft Office Excel cannot open or save any more documents because th
ere is not enough available memory or disk space.
To make more memory available, close workbooks or programs you no longer need.
To free disk space, delete files you no longer need from the disk you are saving to."
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation
You cannot call a method on a null-valued expression.
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull -
Hi
Creating an application to analyze .dmp files - all working well except this odd issue
If I open command prompt and enter this command:-
kd -z C:\Windows\MiniDump\042414-24632-01.dmp -c "!analyze -v"
Then it works and shows me all the output I need (shown at bottom of post)
If I run same command in VB.net using following code - then it doesn't give the same output - the bits I need at the end created by the !analyze -v switch don't appear
Any ideas why it is not seeing the switch correctly - setting a breakpoint and checking contents of startinfo seems to be showing correct cmd line i.e. "kd -z C:\windows\minidump\042414-24632-01.dmp -c "!analyze –v;q""
Dim myprocess As New Process()
myprocess.StartInfo.FileName = "C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\kd"
myprocess.StartInfo.Arguments = "-z C:\windows\minidump\042414-24632-01.dmp -c ""!analyze –v;q"""
myprocess.StartInfo.UseShellExecute = False
myprocess.StartInfo.RedirectStandardOutput = True
myprocess.StartInfo.CreateNoWindow = True
myprocess.Start()
TextBox1.AppendText(myprocess.StandardOutput.ReadToEnd())
Output when run from cmd prompt:-
C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86>kd -z C:\Windows\MiniDump\042414-24632-01.dmp -c "!analyze -v;q"
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MiniDump\042414-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0x82e3e000 PsLoadedModuleList = 0x82f874d0
Debug session time: Thu Apr 24 13:36:18.672 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:38.703
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlpa The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the
command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 50, {afa99150, 0, 88c557d7, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for HipShieldK.sys
*** ERROR: Module load completed but symbols could not be loaded for HipShieldK.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : mfehidk.sys ( mfehidk+377d7 )
Followup: MachineOwner
1: kd> kd: Reading initial command '!analyze -v;q'
* Bugcheck Analysis *
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: afa99150, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 88c557d7, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: mfehidk
FAULTING_MODULE: 82e3e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2e1e3e
READ_ADDRESS: GetPointerFromAddress: unable to read from 00000000
GetPointerFromAddress: unable to read from 00000000
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
afa99150
FAULTING_IP:
mfehidk+377d7
88c557d7 0fb70c06 movzx ecx,word ptr [esi+eax]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
LAST_CONTROL_TRANSFER: from 82e7eaa8 to 82ecb879
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ad0baf90 82e7eaa8 00000000 afa99150 00000000 nt+0x8d879
ad0bafa8 88c557d7 badb0d00 00000000 88c4ceb0 nt+0x40aa8
ad0bb040 88c4f97d 001a99b0 afa91000 00000000 mfehidk+0x377d7
ad0bb090 88c52b16 00770220 ad0bb0fc 00000010 mfehidk+0x3197d
ad0bb0bc 98d5fb73 ae770220 ad0bb0fc 00000010 mfehidk+0x34b16
ad0bb140 98d5fc43 ae738c30 98d6b62a aace7220 HipShieldK+0xb73
ad0bb168 98d6b882 ad0bb19c 00000000 98d77b44 HipShieldK+0xc43
ad0bb1b8 98d631a9 00000bd4 0000102c ad0bb208 HipShieldK+0xc882
ad0bb330 88c47795 00000bd4 0000102c ad0bb401 HipShieldK+0x41a9
ad0bb400 88c22b57 0000102c ad0bb460 85b3dee0 mfehidk+0x29795
ad0bb41c 88c232c6 ad0bb430 0000000c 8c4b6ce0 mfehidk+0x4b57
ad0bb43c 830a5acb adb6b9b8 0000102c ad0bb460 mfehidk+0x52c6
ad0bb4f4 830adaf8 adb16030 01b6b9b8 ad0bb550 nt+0x267acb
ad0bbc00 82e7b8c6 038ae710 038ae6ec 02000000 nt+0x26faf8
ad0bbc34 77a470f4 badb0d00 038ae3dc 00000000 nt+0x3d8c6
ad0bbc38 badb0d00 038ae3dc 00000000 00000000 0x77a470f4
ad0bbc3c 038ae3dc 00000000 00000000 00000000 0xbadb0d00
ad0bbc40 00000000 00000000 00000000 00000000 0x38ae3dc
STACK_COMMAND: kb
FOLLOWUP_IP:
mfehidk+377d7
88c557d7 0fb70c06 movzx ecx,word ptr [esi+eax]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: mfehidk+377d7
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: mfehidk.sys
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
quit:
output when run in my app:-
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MiniDump\042414-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0x82e3e000 PsLoadedModuleList = 0x82f874d0
Debug session time: Thu Apr 24 13:36:18.672 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:38.703
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlpa The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the
command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 50, {afa99150, 0, 88c557d7, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for HipShieldK.sys
*** ERROR: Module load completed but symbols could not be loaded for HipShieldK.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : mfehidk.sys ( mfehidk+377d7 )
Followup: MachineOwner
Darren RoseTry it by opening the Cmd prompt as the actual process and passing the Filename and its arguments as the arguments of the Cmd process. If you notice there is a "-C" before the Filename and Arguments in this example. The "-C"
tells the cmd to execute the commands and then close itself. You can also use a "-K" which tells the cmd to execute the commands and keep itself open. Being you are not showing the cmd window you don`t want to keep it opened because the
user can`t close it so, that is why i used "-C".
I don`t have the program so, you can just experiment to see what it does. Maybe you should try using "-K" and show the cmd window by commenting out the CreateNoWindow line so you can see what is in the cmd window while testing.
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim filepath As String = """C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\kd"""
Dim args As String = " -z C:\windows\minidump\042414-24632-01.dmp -c ""!analyze –v;q"""
Dim p As New Process
With p.StartInfo
.FileName = "cmd.exe"
.Arguments = "-c " & filepath & args
.UseShellExecute = False
.CreateNoWindow = True
.RedirectStandardOutput = True
End With
p.Start()
TextBox1.Text = p.StandardOutput.ReadToEnd
End Sub
If you say it can`t be done then i`ll try it -
Short dump while running Payroll
Dear Experts,
I am getting short dump while running the payroll for around 150 employees, but am not able to see the short dump also as it says that "process terminated".
please help me in this regard and also let me know if there could be any configuration errors.
Regards
ShansarThank you all for the response.
The issue has been resolved. i have learnt that log field should not be flagged when you are executing payroll for more than 50 employees.
Regards
Shansar
Maybe you are looking for
-
Hi All, I have one page. In this page i want to create 4 hyperlinks.Ex:A,B,C,D If i click A .It will show one region with 6 Hyperlinks.Ex:X,Y,Z. If i click X.It will Show one report. This is the task.What is the best way to do it. If any helpi
-
About two days ago, a symbol I have never seen before showed up on my BB Curve 8530 homescreen. I have had this phone for about 2 years. It appears at the top of the screen next to where it shows an envelope and the number of unread emails I have. It
-
ISE and Citrix Netscaler for LB
I'm working on a solution where we have NetScaler load balancers distributing radius requests from the NADs to respectvie PSNs. Authentication works and redirect URLs work etc.. The challenge we're having is with EAP-TLS sessions. The user get's a pr
-
Hi, I need to determine file's path based on URL object provided. I don't have access to File object. I tried to use method getPath in URL, but that returns some strange characters. How can I create File object out of URL, or what other approach shou
-
Hello, my iTunes dates are crashed on my mac, how can I download all my itunes match songs and save on my mac?