Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Project startup halts if Alarm Logging RT is enabled

Created by: rogermanrique at: 10/1/2008 9:30 PM (9 Replies)

Rating (2)

Thanks 0

10 Entries

10/1/2008 9:30 PM	Rate (0)
rogermanrique Bronze Member Joined: 8/11/2008 Last visit: 7/25/2024 Posts: 67 Rating: (22)	Hello, all. My project was running fine, but without alarm logging/displaying, until now. As I put some alarms in the Alarm Logging Editor, I enabled the Alarm Logging RT checkbox in the computer properties. Now when I try to start the WinCC RT, the startup procedure halts when the Alarm Logging RT is "Initializing database connections...". As you can see in the attached picture, the CPU is almost idle (using 4%) and stays like this for a long time (I left for half an hour and then i got tired). Should I wait more or there is something I should do? I'm running WinCC 6.2 SP2 in an Intel Core 2 Duo processor with 1 GB RAM. Thank you. Attachment AlarmLoggingInitializingDatabaseError.JPG (129 Downloads)
	Roger A. Manrique roger@manrique.com.br +55 47 8802 3829
Suggestion To thank Quote Answer

10/1/2008 9:52 PM	Rate (0)
DimiCamp Posts: 168 Rating: (49)	Hi! Analyse the files inside "C:\Program Files\Siemens\WinCC\Diagnose". If you can't figure what's wrong, compact all of them and post a file.zip, so we can try to help...
DimiCamp Posts: 168 Rating: (49)
Suggestion To thank Quote Answer

10/1/2008 10:32 PM	Rate (0)
rogermanrique Bronze Member Joined: 8/11/2008 Last visit: 7/25/2024 Posts: 67 Rating: (22)	the zipped folder. thanks again. Attachment Diagnose.zip (83 Downloads)
	Roger A. Manrique roger@manrique.com.br +55 47 8802 3829
Suggestion To thank Quote Answer

10/2/2008 7:09 PM	Rate (1)
DimiCamp Posts: 168 Rating: (49)	Well, making a guess that you're from Brasil, here's a first suggestion: 1. Abra seu projeto no WinCC Explorer (mas não ative o runtime); 2. Vá em File -> Close, mas deixe o WinCC Explorer aberto até completar os outros passos; (Agora vou sugerir que você apague as mensagens de alarme em histórico, espero que não seja problema pra você) 3. Apague todos os arquivos dentro da pasta SeuProjeto\ArchiveManager\AlarmLogging; 4. Volte ao WinCC explorer, abre o projeto e tente ativar o runtime. Caso o problema persista, escreva de novo e tentaremos outras soluções. Os moderadores parecem não gostar muito de posts em português, mas sempre tem um bonzinho pra traduzir e ganhar parabéns. Em português é até bom que a gente pode fazer graça com os Alemães. Por falar nisso, conhece aquela frase que diz que o Alemão é o Português que aprendeu matemática?
DimiCamp Posts: 168 Rating: (49)
Suggestion To thank Quote Answer

10/2/2008 7:32 PM	Rate (1)
Danielle Posts: 1275 Rating: (123)	Hi Roger, mmm... bonzinho pra traduzir e ganhar parabéns? sempre eu que acabo traduzindo essas coisas! hehehehehehe... mas é que eu fico com pena dos chucrutes! ----------------------------------------------------------------------------------------------------- Translating DimiCamp's msg: 1. Open your project in WinCC Explorer (don't activate runtime); 2. Go to File -> Close,but leave WinCC Explorer open 'till you complete the other steps; (now I'll suggest that you delete the alarm history, hope it's not a problem for you) 3. Delete all file within the Project\ArchiveManager\AlarmLogging folder; 4. Go back to WinCC Explorer, open the project and activate runtime. --------------------------------------------------------------------------------------------------- Another easy way to delete the archive messages is through Alarm Logging -> Archive Configuration, right-click "Message Archive" and select the "Reset" option. Also... have you tried running the Reset_WinCC.vbs script? It supposedly resets all database connections... Best regards, Danielle
Danielle Posts: 1275 Rating: (123)	Last edited by: Danielle at: 10/2/2008 7:42 PM
Suggestion To thank Quote Answer

10/3/2008 1:19 AM	Rate (0)
rogermanrique Bronze Member Joined: 8/11/2008 Last visit: 7/25/2024 Posts: 67 Rating: (22)	thank you DimiCamp. thank you Danielle. i'll try this and, if things go bad again, i'll tell you. by the way, sim, eu sou brasileiro, but, is my english that bad?? hehehhe just kidding
	Roger A. Manrique roger@manrique.com.br +55 47 8802 3829
Suggestion To thank Quote Answer

10/3/2008 1:51 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	Nope, we got that from the screenshots of the "Gerenciador de tarefas do Windows" hehehe...
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

10/6/2008 8:00 PM	Rate (0)
highvoltage Posts: 10 Rating: (0)	Just wanted to say thanks for the above answers..... I had a similar problem and this worked fine for me !!! I still have a little automatic print box still popping up but you solved my major issue !!! blow is a pic of the pop-up I am getting.....maybe someone knows a quick way to disable this monster ? thanks beautiful people !!! Michael ................UPDATED Solved my problem above by de-selecting the checkbox next to "message sequence report" in the computer "properties" tab. many thanks again.......kinda just did a trial and error on it. mike Attachment print log message.jpg (84 Downloads)
highvoltage Posts: 10 Rating: (0)	Last edited by: highvoltage at: 10/7/2008 6:02 PM
Suggestion To thank Quote Answer

10/13/2008 4:47 PM	Rate (0)
Ahmetben Posts: 1 Rating: (0)	Dear Danielle; I have the same problem and done necessary actions as you have offered ,but unfortunatelly problem is still alive.. Two log files are inattached pdf file How do you think I should proceed ? Thanks in advance , Ahmet Attachment Log_files.pdf (77 Downloads)
Ahmetben Posts: 1 Rating: (0)
Suggestion To thank Quote Answer

10/13/2008 10:43 PM	Rate (0)
rogermanrique Bronze Member Joined: 8/11/2008 Last visit: 7/25/2024 Posts: 67 Rating: (22)	Danielle / DimiCamp / other folks, we tested your solution last week but things didn't work out. first we tested the dimicamp solution. we deleted the files you told me to delete and when we tried to run we got the same error. then we tried to reset, using danielle script and, again, the same error on startup. we formated the machine, reinstalled everything, step7, drive es, wincc and so on..... same error. formated again, installed only wincc.... guess what? so, i tried in other computer. the first time i ran everything was ok, icluding alarm and tag logging. so, i'm suspecting of the computer we are using. my configuration is: Dell Optiplex 755 Intel Core 2 Duo CPU E6850 @ 3.00 GHz 1GB RAM Windows XP SP2 WinCC v6.2, SP2 (V6.2.2.0) we called Dell and they suggested BIOS upgrade. we did it (from a08 to a11), reinstalled some drives and.... nothing. isn't the problem with dual processors solved in this version? will i have to buy another processor??? (we always use dual core, this is the first time we use core 2 duo) thank you again.
	Roger A. Manrique roger@manrique.com.br +55 47 8802 3829
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on