Proclaim won't open

I have been here a couple of times before, and yet no help. I guess people don't like me. But it's not about me, it's about my church. I am the one that builds the announcements. I work mon. thru fri. 5 to 5. So I am not able to get into the church until Sunday morning. and these last cople of weeks we have had no announcements.

On to the problem. I didn't have any problems until an update, which I did. Since then it will log in and then flash the page and then it's off. I have tried moving to trash, and emptying the trash. Downloading again. But it still does the same thing. Someone said to send them a crash report. But since it doesn't really crash, there's no report. there is nothing with the name "proclaim" in ANY of the reports.

I would like to get this fixed. If this is not possible, then I will go every where I know to give Proclaim a bad review. Please don't make me do this.

Find more posts tagged with

Comments

Scott Alexander

The latest update (build 110) is causing an issue for users in timezones with a positive UTC offset. We just shipped a fix for this this evening so restarting the app should prompt you to update.

Not sure if this is the issue you're experiencing. It would help me diagnose your issue if you could post your log files by replying to this post. You can find the log files here

Mac:

/Users/[username]/(~Library)/Application Support/Proclaim/Logging/
The Library folder might be hidden. If so, hit CMD+Shift+G and enter "~/library" into the box.

Windows:

XP - %USERPROFILE%\My Documents\Proclaim Log Files\
Vista/Win7 - %USERPROFILE%\My Documents\Proclaim Log Files\

william peterson

https://community.logos.com/discussion/comment/347359#Comment_347359

Since it won't open, there are no log files. nothing. Nada. Zilch.

Scott Alexander

Since then it will log in and then flash the page and then it's off.

When you start the application do you see the login window as shown below? If so the logs should be generated. Are you running Lion? if so the Library folder will probably be hidden. To show it hit CMD+Shift+G and enter "~/library" into the box.

Another option is you could open the Console program (in Applications/Utilities) and see if there is any interesting output when you start Proclaim

william peterson

https://community.logos.com/discussion/comment/347457#Comment_347457

Well I finnally got it to give me a report. This is what it will send to Apple. And no I do not get the sign in page. I'll post video of what happens.

Well great! now your post will not let me post any files or video.

Great site, I'm outta here.

Walters Madre

https://community.logos.com/discussion/comment/347359#Comment_347359

Since William left, maybe you can assist me. Here are my logs:

Log1:

Program Version: 1.0 (1.00.0.0094)
Windows Version: 5.1.2600.196608
Time: 2012-02-18 21:05:35 -05:00 (2012-02-19T02:05:35Z)
Installed memory: 1,015 MB
Install path: C:\Documents and Settings\Teaching Matters Inc\Local Settings\Apps\2.0\M4TTMHBX.Z2Q\7REJZO3N.VYE\proc..tion_c830e69472a2fd73_0001.0000_0cd47d614cd743be\Proclaim.exe
Free install space: 50,434 MB
Temp path: C:\Documents and Settings\Teaching Matters Inc\Local Settings\Temp\
Free temp space: 50,434 MB

Error ID: 7909
Error detail: ArgumentNullException: Value cannot be null.
Parameter name: groupInfo

System.ArgumentNullException: Value cannot be null.
Parameter name: groupInfo
   at Logos.Proclaim.Common.Model.Group.Create(GroupInfo groupInfo)
   at Logos.Proclaim.Common.UserManager.DeserializeCurrentGroup(String currentGroupString, String currentGroup2String)
   at Logos.Proclaim.Common.UserManager.GetCurrentGroup(Int32 userId)
   at Logos.Proclaim.Common.AccountManager.<LoginWork>d__d.MoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1.ContinueExecution(Object unused)
   at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(Object state)
   at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

Log2:

*** Application Crash ***
Program Version: 1.0 (1.00.0.0094)
Windows Version: 5.1.2600.196608
Time: 2012-02-18 20:58:15 -05:00 (2012-02-19T01:58:15Z)
Installed memory: 1,015 MB
Install path: C:\Documents and Settings\Teaching Matters Inc\Local Settings\Apps\2.0\M4TTMHBX.Z2Q\7REJZO3N.VYE\proc..tion_c830e69472a2fd73_0001.0000_0cd47d614cd743be\Proclaim.exe
Free install space: 50,435 MB
Temp path: C:\Documents and Settings\Teaching Matters Inc\Local Settings\Temp\
Free temp space: 50,435 MB

Error ID: 7909
Error detail: ArgumentNullException: Value cannot be null.
Parameter name: groupInfo

*** Application Crash ***
Program Version: 1.0 (1.00.0.0094)
Windows Version: 5.1.2600.196608
Time: 2012-02-18 21:05:35 -05:00 (2012-02-19T02:05:35Z)
Installed memory: 1,015 MB
Install path: C:\Documents and Settings\Teaching Matters Inc\Local Settings\Apps\2.0\M4TTMHBX.Z2Q\7REJZO3N.VYE\proc..tion_c830e69472a2fd73_0001.0000_0cd47d614cd743be\Proclaim.exe
Free install space: 50,434 MB
Temp path: C:\Documents and Settings\Teaching Matters Inc\Local Settings\Temp\
Free temp space: 50,434 MB

Error ID: 7909
Error detail: ArgumentNullException: Value cannot be null.
Parameter name: groupInfo

Chris Martin

https://community.logos.com/discussion/comment/349619#Comment_349619

You'll have to wait for an official Proclaim staff member to get the lowdown on your issue, but it appears to my uneducated eyes that Proclaim is crashing because it thinks you aren't part of a group. You probably need to force it to start the login process over again, and make sure you choose a group during the setup.

There is a spiffy shortcut that will let you do that when you launch the program, but after trying to recall it I'm drawing a blank and a quick search of these forums didn't locate it either.

You could try uninstalling Proclaim and then reinstalling it. Since Proclaim pulls things from the cloud anyway, you shouldn't lose much in the way of time or work.

Just a thought, and likely not an entirely accurate one.

Hunter Clagett

https://community.logos.com/discussion/comment/349619#Comment_349619

Since William left, maybe you can assist me. Here are my logs:

Thank you for the information, Walters! I have passed your information on to our Developers.

If we need further information we will be in contact with you.

Thanks,

Scott Alexander

https://community.logos.com/discussion/comment/349619#Comment_349619

Since William left, maybe you can assist me. Here are my logs:

Following up offline.

Scott Alexander

https://community.logos.com/discussion/comment/349624#Comment_349624

There is a spiffy shortcut that will let you do that when you launch the program, but after trying to recall it I'm drawing a blank and a quick search of these forums didn't locate it either

Holding down Ctrl (or Command on Mac) will force the login prompt at startup.

Chris Martin

https://community.logos.com/discussion/comment/349828#Comment_349828

Thanks Scott.