Had my first Proclaim full lockup Sunday- not fun...

It was about 11:30 PST - trying to move past the second to last song to a prayer slide and to the final song. We had two iPads in front trying to control the program - not initially at the same time when the problem occurred, but as the problem became evident, we were both trying and kept getting the unable to change slide message on the iPads.

After the service I went back to the laptop and tried to move the program to the announcement loop we have at the end of the service and the program was completely locked. I had to manually shut it down Through the Task Manager (I'm on Windows 7). when I tried to restart the program it wouldn't start so I just shut the laptop down.

I see that there were some issues with the Proclaim servers yesterday - Is that what I was experiencing? I did notice as well that the OSB slides that we used were inconsistent at both services all morning. At times they would just pop up (changed with the iPad) with little or no perceived lag, and most times it would lag a full sentence or so. That makes it hard to judge when to move to the next slide!

This is the first Sunday I've had complaints about the service - the technology shouldn't be getting in the way like this...

How do we sort out what went wrong? My laptop is a Sony Vaio i7 with 8 gigs of ram and a separate graphics card with its own ram, plenty of hard disk space, Windows 7 up to date. I recall noticing when I shut it down that the Apple iTunes update message was running as well... could that have interfered with Proclaim?

Larry

Find more posts tagged with

Comments

Spencer McKimson

It could have been issues with the server but those were primarily in the morning and had been resolved by the time of your service. Have you started Proclaim since then? If so I could take a look at the logs. They should be located here:

%USERPROFILE%\My Documents\Proclaim Log Files\

I would like to take a look at the ProclaimCrash.txt file, the Proclaim.log file and the ProclaimError.Log file. Now for questions about the crash you occurred: What were you doing exactly when Proclaim locked up (viewing a video, showing a certain type of service item, etc.)? Can you reproduce the issue now? Which presentation were you having issues with? With this information, I should be able to investigate further.

Lawrence Becker

https://community.logos.com/discussion/comment/600487#Comment_600487

Thanks, Spencer,

I was in the 2nd to last song in our 10:45 service. The iPads locked on one of the slides and wouldn't move forward. I assume that's when the laptop locked.

Log files:

6013.ProclaimError.log

2046.Proclaim.log

4452.awesomium.log

I didn't find a ProclaimCrash.txt file on my laptop

I started Proclaim before I entered this post, exited it, and was presented with a BSOD. It MAY be an issue, then, with my pc? I did NOT have a BSOD on Sunday, and I used the laptop most of the afternoon on a PPT slideshow in a different room.

I'll try to reproduce it now, but wanted to post this before the pc hung again...

Thanks for your help!

Lawrence Becker

https://community.logos.com/discussion/comment/600570#Comment_600570

The first time I started Proclaim up it ran ok but gave an "Unknown error" message in the right panel of the laptop screen. Proclaim generated two new log files...

7851.awesomium.log

6740.Proclaim.log

Thanks!

Spencer McKimson

https://community.logos.com/discussion/comment/600574#Comment_600574

Hmm the logs aren't indicating any crash or any problems that I can see. I will check out your presentation and see whats up. Since you experienced a BSOD, I would suggest checking that all of your drivers are up to date (Including your video drivers), there are no security updates needed, etc. Once this is done, reload Proclaim and see if you run into any issues.

Also if you can reproduce the crash, please let me know!

Lawrence Becker

https://community.logos.com/discussion/comment/600575#Comment_600575

Windows needed several updates, and there was a new video driver from Nvidia - installed all those.

Another issue on our equipment side - Saturday night our DNS server went down in our server cabinet. USUALLY when that happens I have to reset all the equipment on our network so it can re-connect to the server. I did that with the printer, but when I checked the router/WIFI modem, it seemed to work ok so I thought - maybe it didn't go down. I guess it did. This time when I started up Proclaim, it gave me an error message in the right column: "Unable to resolve DNS name" or something close to that... When I restarted the router so it could reconnect with the DNS server, Proclaim was happier and it seemed to work more smoothly - and no DNS error...

Could that have contributed to our mess last Sunday?

Larry

Spencer McKimson

https://community.logos.com/discussion/comment/600649#Comment_600649

It is hard to say but a combination of old drivers and internet issues could have both contributed to your issues on Sunday. Now with all the updates on your computer, Proclaim should run smoothly; Just make sure the server is up and running and you should have no problems. If the server was down, then the remotes would not have worked since they require wifi to control a presentation.

Lawrence Becker

https://community.logos.com/discussion/comment/600772#Comment_600772

The server went down briefly at about 10 pm on Saturday night. I restarted it, but didn't force to router we use in the sanctuary to shut down and restart so it could reprovision its DNS address. I had to do that for one of our printers, and did check the router but it was showing a good WIFI connection and seemed to work ok. Indeed, it did work for our early service, but locked up in the second service. And when I tried restarting Proclaim on Monday it gave me an "unknown error" message in the right panel, and noted a problem finding a DNS name later, until I restarted the router - then all was ok. I think there was a momentary power glitch.

We DO have a massive battery backup unit on our server cabinet - but the batteries need replacing (for the 2nd time). They last 3 or 4 years, and at $30x8, it's a little pricey. My volunteer IT guy has been out of town and had other projects keeping him busy. I moved that up on his priority list. I imagine that you're exactly right though - a mix of slightly out of date drivers and the DNS issue...

Thanks so much! You all are so patient and kind to us!

Larry