• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerServer
  • PS application ran fine, then suddenly won't run.

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved PS application ran fine, then suddenly won't run.

  1. Issue
0
Votes
Undo
  1. mike S
    mike S
  2. PowerServer
  3. Tuesday, 12 December 2023 19:00 PM UTC

PS2022R2 build 2828  running on windows 11 HOME computer

disable AV, which did not help.

 

user no longer able to open up files (possibly the directories?) from PS.  ran fine for a week or so, no updates to the application, so it isn't failing on that. all other users run fine, no issues.

 

I ran the PS application from the command line and added /PBdebug:   mycloudapp.exe /pbdebug

this DOES generate a pbdebug file, and it provides a lot of great detail.  (be careful, you will need to manually edit the pbapp.ini file to REMOVE the runtime parameter otherwise it will continue to run in pbdebug mode)

 

anyway, from debug file i see:

 

C:\WINDOWS\SYSTEM32\WINMM.dll, 6.2.22621.2506, 184KB
C:\Users\username\AppData\Roaming\PBApps\Applications\Runtime\22.1.0.2828\pbresource.dll, 22.1.0.2828, 3916KB
C:\Users\username\AppData\Roaming\PBApps\Applications\Runtime\22.1.0.2828\pbjson.dll, 22.1.0.2828, 381KB
C:\Users\username\AppData\Roaming\PBApps\Applications\Runtime\22.1.0.2828\pbdwe.dll, 22.1.0.2828, 5597KB

Failure opening library myapp_es.pbd
Failure opening library myapp2.pbd
Failure opening library main.pbd

 

so the user for some reason is not able to open the directory, or maybe the files?  They all exist.  

 

I deleted all the directories and they all downloaded and the application is now fine.   Can't remote into a users machine everyday to manually delete directories, so doing that is not a solution.

 

has anyone else seen this?  any ideas on how to prevent this from occurring?

 

 

 

 

 

 

 

 

 

 

 

Datawindow retrieve timeout issue in Web API
signed PS launcher downloads from web and gets fla...
Responses (2)
Logan Liu @Appeon
Logan Liu @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 December 2023 06:37 AM UTC
  2. PowerServer
  3. # 1

Hi Mike,

I haven't seen this "Failure opening library" error yet. Here are some suggestions:

1) Could you see any error messages in Windows Event Viewer?

2) If you have backed up the downloaded pbd folder before deleting the folder, please compare the previous myapp_es.pbd folder with the newly downloaded myapp_es.pbd folder. If they are different, please submit the files to us via a support ticket.

Regards, Logan

 

 

 

Comment
mike S
  1. mike S
  2. Wednesday, 13 December 2023 14:26 PM UTC
"Failure opening library myapp_es.pbd"

so, that is actually a folder. I had remoted into the machine and was able to open the folder and look at all the files. the files in there all were the correct size, name, etc. I had renamed it and when the app redownloaded everything i was able to compare.



does that error message mean that it could not open the folder? If so, why could i open it under the users login (user was logged in, i used a screen share to get in).



I did not look at the windows event viewer and it is very difficult to get access to the users machine.
  1. Helpful
Logan Liu @Appeon
  1. Logan Liu @Appeon
  2. Thursday, 14 December 2023 03:17 AM UTC
Hi Mike,

This error doesn't seem to be caused by folder permissions, but "the logic to load the PBD" thought there was an invalid PBD file format being loaded.

Under the PowerServer/PowerClient solution, the PBD file is split into multiple independent files that can be downloaded as needed. It will be helpful if you can get them.

Regards, Logan
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 December 2023 13:21 PM UTC
  2. PowerServer
  3. # 2

Hi Mike;

  This sounds like the main folder or its subfolder / files somehow became corrupted. Once you deleted ...

C:\Users\username\AppData\Roaming\PBApps - then the App was redownloaded and it ran ok - tells me that the issue was caused by a local machine hiccup (my best guess). I've seen this happen the odd time after an O/S or AV software update. Especially after that the machines are not rebooted before running apps (not just PB ones). Maybe check the machine logs for what changed just prior to this issue. HTH

Regards... Chris 

Comment
mike S
  1. mike S
  2. Wednesday, 13 December 2023 14:29 PM UTC
Yes, the standard question is always: 'what changed'

If there was an AV update, the user probably doesn't know about it.

We did have them reboot.



Sophos Antivirus is the package. I'm trying to get a list of the ones that are in use in case there is a pattern.







  1. Helpful 1
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.