C++ Debug Assertion Failed! - when printing with LOCL method G and GUI 620

Hi all
I've just raised an OSS message with SAP but don't think they'll help as the GUI version is no longer supported... if anyone else has come across this though and has any suggestions that would be great...
Thanks
Ross
Hi
We recently upgraded a few users to the 720 SAP GUI and had issues with LOCL printing, as we were still using the older "F: Printing on Front End computer" method of printing. As per SAP Note "Note 821519 - Front-end printing with control technology" the solution is to use method "G: Front end printing with Control Tech".
However, we now get an issue with SOME users who are running the SAP GUI 620 patch 57. When they try and print to LOCL they get a pop up dialog box error:
"Microsoft Visual C++ Debug Library
Debug Assertion Failed!
Program: C:\Program Files\SAP\FrontEnd\SAPgui\saplogon.exe
File: fputs.c
Line: 48
Expressiom: steam != NULL"
I appreciate that this old GUI is no longer supported BUT the SAP note states that 620 patch 56 is the minimum level for method "G" to work - and previous testing showed that it DID work ok. It seems only some of the 620 patch 57 users are affected - just wondering if you can advise why and if there is a 'quick fix' for this, perhaps an updated fputs.c file or something?
The issue is that we literally have thousands of users on this version and cannot roll out 720 quickly enough & without some additional testing/costs etc. We have a 710 patch 18 version we can roll out but this can cause IE8 issues... neither do we wish to revert to control method "F" as this will then 'break' printing for those users.
We have created a LOCL_OLD printer with method "F" but some users (for various reasons, including hard coded printers in bespoke transactions) cannot select this and have to use LOCL...
If you are aware of the C++ debug assertion error and have any possible solutions that would be much appreciated.
Many thanks
Ross

> I appreciate that this old GUI is no longer supported BUT the SAP note states that 620 patch 56 is the minimum level for method "G" to work - and previous testing showed that it DID work ok. It seems only some of the 620 patch 57 users are affected - just wondering if you can advise why and if there is a 'quick fix' for this, perhaps an updated fputs.c file or something?
fputs.c is a source file that is used to compile the GUI. The assertion is thrown because an expected condition is not met. So even if you would take out the assertion, there's no guarantee it'll work because "something" on the operating system is not right.
I suggest you compare installed software and windows hotfixes on the affected PCs vs. those who don't show this error. The error may also be that after the installation of the SAPGUI another software product was installed that replaced certain DLLs that are also used by the SAPGUI.
Markus

Similar Messages

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
Anyone have an idea on other things to try to debug/resolve this?
Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
Thanks!

After a week's worth of debugging, I found the issue.
The Java type returned from the call was defined as ArrayList. Changing it to List resolved the problem.
I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid. And, why it works in Debug mode and not in Release build is even stranger. Maybe someone can shed some light on the logic here to me.

HP Laserjet 6MP fails to print with parallel-to-USB converter cable

I have a LaserJet 6 MP parallel printer which I was using in 10.3.9 with a parallel-to-USB converter cable. The Printer Utility saw it natively as a USB device and it printed just fine most of the time, although it would occasionally fail to print, so I installed a different driver called usbtb 1.0.15, and after that it printed very reliably.
Now I've upgraded to 10.4.9, and the Printer Utility still detects the HP printer natively as a USB device, and I also installed the formerly-reliable usbtb driver again, but the printer now fails to print with either driver. It acts like it's going to, but then it quits.
When I choose Print, all the features of the printer are shown, and I can select which tray to take paper from etc., and the printer dialogue box says "Printing," the activity light on the printer flashes just as it always does when printing is in progress, but then, instead of printing, the activity light stops flashing and the print job disappears from the dialogue box.
Can anyone tell my why this printer is failing to print now, and how I might be able to get it working again?
Thanks,
Tom

Wait a minute! It's only certain Indesign documents that won't print.
All TextEdit docs will print.
I created a few scribbles in Photoshop and they print.
But with InDesign, there is no predicting which documents will print or will not print. On some that will not print, if I remove all but one text box, then they will print. On other documents that do print, if I copy some text off of one that won't print and paste it in, then that one stops printing too.
On some that won't print, if I erase everything on the page and create a new text box and type a few words into it, the page will print. If I revert to the previously saved version, once again the page won't print.
What kind of craziness is this, anyway? It seems random. I can't figure it out.
Even on the documents that won't print, when I try to print them the printer's activity light blinks as though it is just about to print, but then the light goes out without printing.
Anybody got any ideas what this problem is and how to fix it?
All I know is that EVERYTHING printed before I upgraded from 10.3.9 to 10.4.9.
Tom

Proc "debug assertion failed!"

hi,
i m working on oracle 9i on windows ,when i run a proc then i get these error at end of proc, tell y m i getting these error
debug assertion failed!
program:preptty.exe
file:fprintf.c
line:56
expression:str !=null
for information on how your program can cause an assertion
failure,see the visual c++ documentation on asserts.
(please retry to debug the application)
and then
APPLICATION ERROR
this instruction at "0x0040809c" referenced memory at "0x00000010".
the memory could not be "read".
click on OK to terminate the program
click on CANCEL to debug the program
now i came to know that in my proc where i used lots of time printf command
fprintf(ptr,"Calculation Terminated Sucessfully!!!\n");
there i m having this problem but when i coment these printf commands i didnt get this error
id idnt know why this error coming now and how to resolve it ?
thanks

Why do you suspect an operating system issue?
I'm guessing you are on Windows. If you look at fprintf.c and line 55/56 you should see:
VALIDATERETURN( (str != NULL), EINVAL, -1);
VALIDATERETURN( (format != NULL), EINVAL, -1);
These are the checks for the file pointer and the format control string and if either is NULL an assertion is raised.
Here's an easy way to see this:
{noformat}
* this will cause an assertion
fprintf(NULL, "bad!");
{noformat}
{noformat}
* this will cause an assertion
fprintf(fp, NULL);
{noformat}
Have you confirmed that the assertion is raised from:
fprintf(ptr,"Calculation Terminated Sucessfully!!!\n");
Since you have "expression:str !=null" that is an indication that the file pointer is NULL. Perhaps you are not checking the file pointer before using it and it is NULL?
Regards,
Mark

AutoCAD 2009 crashes when printing with HP Laserjet CP1525nw via wireless connection

Printing to CP1525nw via wireless connection crashes AutoCAD 2009 on a WIndows 7 Home OS + Sony VAIO VPCL21M1E
Works fine printing from any other application.

I'm facing the same problem but, i'm AutoCAD 2012 and it crashes when printing with HP Laserjet CP1525n via USB or network cable

Color shift when printing with LR 3.6

LR 3.6, win 7, screen Nec PA 241 W, Epson R 3000. When printing with colors managed by LR and paper/R 3000 profiles, I get prints with a strong color shift (printer pilot "mode" : desactivated) . How can I correct it ?

You answered your own question: CS5. There have been a slew of reports of workflows spun upside down when upgrading to CS5. It may require updating your system software and/or Adobe applications, along with any printer driver updates that may be lurking out there somewhere. The twist to your situation is ( and is very common ) that everything was working before and now it does not. Or there is a certain print disorder of some sort. Very troubling. I wish I had a smoking gun answer for you, but I don't. It sounds like you have a very viable workflow in place that worked before and damn well should perform for you now. I'd stick with what works and dump what doesn't ( if you can ).

Black ink faded/Gray when printing with HP Envy 5530

When printing with my new HP Envy 5530 the black ink looks gray or faded. I tested the color and this prints dark and clear. I have power cycled, plugged into different power outlets and re-inserted the cartridge. Any thoughts...or could it just be a "bum" cartridge?
Thanks in Advance for your help...

Howdy. After tinkering around with my Envy having the same issue, I found out that after replacing my black cartridge because it was low, I was having the same issue.
Turns out the color cartridge will simulate a black in an to preserve both the tri color cartridge and the black cartridge for as long as possible, which is why even if you've never printed any color, both your cartridges should be low. Once the color cartridge starts getting low, the printer doesn't have a sensor to realize which of the tri color is mixing in the most, so it continues to mix it in either way.
I was having this issue where I would print one page and it would be okay and then any page following would slowly look worse.
Long story short, just print without the color cartridge in and you shouldn't have the issue unless your black is really low. Replacing that should fix it overall though.

MOVED: [Athlon64] Failed Bios update with both Live Update and Dos version = badchecksum shutdown

This topic has been moved to AMD64 nVidia Based board.
[Athlon64] Failed Bios update with both Live Update and Dos version = badchecksum shutdown

Sometimes bios recovery is a long shot .
But the award bios v.6 is supposed to be able to do it if the bootblock is still intact.
Best way seems to be to strip it down to minimal configuration , disconnect all drives except floppy , one ram module , perhaps without video card also .
Look here :
http://pages.sbcglobal.net/jefn/bootblock.html

Assertion Failed editting list with taxonomy field

I have lists with a taxonomy column in them. when editing the list, jsgrid looks to be throwing an assertion failed. Digging into the call stack, it is calling GetDisplayControl, the assert is "Sys.Debug.assert(displayControlName in displayControlsSingletonMap);
Rolling back a bit, the order of calls on the call stack
Sys$_Debug$fail
Sys$_Debug$assert
GetDisplayControl
RegisterPropType
RegisterNewCustomPropType
SP_UI_Taxonomy_ControlRegistration$RegisterGridControls
Init
The displaycontrolName at the point of the assertion error is "" so it defininately isn't in displayControlsSingletonMap, which is why the assert is happening.
Anyone have any solutions?

Hi SP Yogi. No fix for it, no. I had opened a support ticket with Microsoft to deal with the issue, but we never could get together at the same time to work on it. I did provide complete log files to them, but that's as far as it went. My company then decided
to go with SP2010 environment instead of SP2013, so became a moot point for us and I figured someone else would start screaming.
If anyone else raises it with Microsoft, you could have them look at
case # 113041510367364, which is the ticket I created for raising the issue. Might speed things along, help discount environment issues, etc.
Good luck and please report back any progress!

OLE Program works in debug mode fails when run from F8

Hello,
I have implemented a code from this forum for sending documents to printer, as below, but although it works well in debug mode, it fails when I execute directly from SE38? Any idea?
Best Regards,
Didem GUNDOGDU
CREATE OBJECT gs_word 'WORD.APPLICATION'.
SET PROPERTY OF gs_word 'Visible' = '0'.
CALL METHOD OF gs_word 'Documents' = gs_documents .
CALL METHOD OF gs_documents 'Open' = gs_newdoc
EXPORTING
#1 = p_filep .
CALL METHOD OF gs_word 'ActiveDocument' = gs_actdoc.
CALL METHOD OF gs_actdoc 'PrintOut' .
CALL METHOD OF gs_word 'Quit' .

Hi Didem,
Just a suggestion: could you print syst-subrc after each method call? Perhaps that can give you a clue.
Regards,
John.

"ASSERT FAILED" when java.exe ends

What kind of error message is this:
ASSERT FAILED:
Executable: java.exe PID 218 Tid b04 Module kswdmcap.ax, 4 objects left active at line blablablablabla
This happens when my java class ends from where I called a c++ method (that controls the windows media encoder sdk). It return without an error message from the c++ part, but when java.exe tries to end the class does this error message appear on the screen (Windows XP). Does anybody have a clue what that might be?

I wouldn't say problem.
Presumably the library you call does something. While doing that it creates "resources" of some sort. It could be a socket. Or a memory allocation. Or something else.
But it expects you to tell it when you are done. Either with the library or with some specific aspect of the library. And you are not doing that before you exit.
Keep in mind that I am only guessing. There could certainly be other explainations - like a bug in the library.

HP D110 AIO printer. Prints jam when printing with wireless, but not when hooked to USB cable! HELP!

I have a HP D110. It jams the paper when I print with wireless, but not when I use USB cable. Any ideas?

From what you describe you are having issues printing from MS Office. Have you had trouble printing from other resources on your computer (e.g. from the internet or another program)? The first thing I am going to suggest is that we start by uninstalling and reinstalling the printer from the resources available online.
First if you use a USB cord, make sure to remove it (this is important). Do not plug it back in until the software directs you to. Then go through the Devices and Printers, Programs and Features and Device Manager folders and insure that all copies, files, and programs related to the printer are removed. Then as directed, restart the computer.
In the START menu type "%temp%" and press ENTER. Here I want you to press Ctrl+A and hit DELETE. Some of the files will not allow you to delete them, skip those files and delete the majority that allows it.
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=3562006&lang=en&cc=us...
Install that and let me know the result!
Have a great day!

Getting unknown error when printing with latest version(using HP Laserjet 1200). I can't print at all using this version. Able to print previously.

I ceased to be able to print when the latest version of FireFox was
downloaded. I can print from the same websites using I. E.
My printer is a HP Laserjet 1200 series. I only get the error(an unknown error occurred while printing) when trying to print through FireFox. I can print email fine and any other instance as long as I'm not going through FireFox.

Hello Josh,
We are using a couple of EFI (Fiery) controllers with our Canon copiers and I have been told by Canon support that we need to be using the MacTel (Universal Binary) versions of drivers for Leopard. Luckily for us we have mostly new models of RIPs and the UB drivers exist for these models, but I know that they are not available for all models, which I believe includes your X3e.
To determine if you have a driver or RIP issue, you could save the file as either PS or PDF and then use the EFI utilities, such as Command Workstation, to import the file to the RIP (select Process and Hold) and then see if you can print your multiple copies that way. If that works then you know that the RIP is probably okay.
The next test would be to create a generic PS queue to the X3e and print using this queue. If this works then you can narrow your issue down to the driver.
PaHu

Header problem with photosmart 8180 when printing with company letterhead

I print many letters through MS Word 2003. When I print a letter on plain paper, it looks fine and is the correct distance (1 1/2") from the top of the page(s). Our letterhead consists of a 1" dark band with our logo included and our address across the bottom of the page. I then insert our letterhead to print a final, the printer moves the letter (date, name, address and body) down another 1", meaning the printer is using the bottom of the band to measure the top margin. It also ignores the bottom margin of 1" and just prints into the address, instead of going to the next page. Both types of paper are the same 8 1/2 X 11.
We have Konica network printer and I previously had a HP 930 printer and never have seen this before. I have uninstalled the printer and reinstalled and the only change I have made since is to change the the paper type, under "Print", "Properties", "Features", "Paper Type", from Automatic to Plain Paper. Neither helps.
I have an extended email list with HP Customer Care, telling me everything from installing a 990C driver (or virtual printer?) to have me check to make sure I knew how to load paper.
I then spent over an hour on the phone with an HP rep and even gave him control of my computer, to no avail. He thinks he fixed the problem by having me reduce the top margin, to say 1/2" and basically trick the printer into printing at the correct place below the band, but the second page is now too far up because of that.
I hope someone can help. I found it hard to believe that this has only happened to me.
Thanks for any help.
Dean

Hello,
at first, what kind of intemec priter do you use? Is it host or stored ipl mode?
value for intermec pm4i in host mode:
my suggestions is the labelsoftware for this printer and the addon tool for r3.
Best regards,
Nino

Adobe reader 10.1.3 closed and go away when print with no error.

I have tried all the methods that posted to fix adobe reader when print. I have even upgraded to latest version of reader 10.1.3 and it still closed when I choose to print. As a matter of fact it will do the same when I choose Preferences, too. The only way to fix this problem is to Uninstall Microsoft patch KB2624667. This is not a good solution. As a background, I have the Adobe reader 10.1.3 on Windows 2003 server 64 bit. The printing problem was there since version 10.1.x. Any help will greatly appreciated. Thanks.

Update: It's been two months since my original post and it has finally been verified my theory was correct. After Mcafee's on-access scan (v.8.8) was disabled I never experienced any of the problems above. For example, I had a test box that experienced the issues I described in my orginal post and Reader had failed to install over 450 times (yes that number is accurate); after Mcafee's on-access scan was disabled the installation was successful.

C++ Debug Assertion Failed! - when printing with LOCL method G and GUI 620

Similar Messages

Maybe you are looking for