Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Raport printing problem "Printit.exe" application error window

Created by: gras at: 3/23/2007 9:55 AM (3 Replies)

Rating (0)

Thanks 0

4 Entries

3/23/2007 9:55 AM	Rate (0)
gras Posts: 11 Rating: (0)	Hi Since switching into WinCC 6.0 SP 4 we began to have problems with printing large amount of data from tag logging archive. Print job window shows "reading data" info and next stops. System window Printit.exe" application error appears with text message that it can not read memory (with some addresses given). It appears when the number ofarchive tagsto be printedexcedes some limit. We did not have problems with the same projects before changing into SP4. Can I find somwhere a limit for the number of dataI can print in one print job? Is my conclusion true that such limit for 6.0 SP4 is less than for SP1,2 ? Regards Bogdan
gras Posts: 11 Rating: (0)	Last edited by: gras at: 23.03.2007 14:20
Suggestion To thank Quote Answer

3/23/2007 1:07 PM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi please attach ALL WinCC log files from folder "..\wincc\diagnose" in the forum. How much RAM and which Intel CHIP is inserted in your PC? nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

3/23/2007 2:19 PM	Rate (0)
gras Posts: 11 Rating: (0)	Hi PC It is Siemens industrial PC : PC577 40GB HD, 230 AC TOUCH 15" TFT Display, 1024 x 768 Celeron 2,0 GHz, 400MHz FSB, 128 KB SLC 1 Gbyte DDR SDRAM (2 x 512 MB)Windows XP SP 2 Log files in an attachment. Have a nice weekend. Bogdan Attachment Diagnose.zip (155 Downloads)
gras Posts: 11 Rating: (0)	Last edited by: gras at: 23.03.2007 16:16
Suggestion To thank Quote Answer

3/23/2007 8:07 PM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi having a look at your logfiles I cannot detect a real reason for your problem... how much data do you intend to print at one print job? If this project has worked in the version before I am convinced it should work in the next version as well. => perhaps you should open a support request at simatic support and ask whether this behaviour is already known or even fixed. nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on