I'm trying to open my newly installed Postman when an error occurs which says something like this:
**Could not open Postman**
Error: Migration: IndexedDB schema migration failed. IndexedDb was not upgraded succesfully after `dexie.open`.
Please try restarting the app. If the issue persists, please refer to http://go.pstmn.io/troubleshoot-could-not-open
As it says, the error really persists. The website above only provides suggestions like "reinstall the app" "upgrade the app", which are not really helpful. And as I dig into the Internet, it occurs to me that such error hardly happens (found nobody have the same question like me).
"IndexedDb" was mentioned in the error message, and I just know (from the Internet) that it's a nosql database provided by explorer. Maybe the problem can be solved by reinstalling the database, I guess?
I had a similar problem and found this description: https://github.com/postmanlabs/postman-app-support/issues/4897
Short answer is, delete the Postman configs directory at ~/.config/Postman (for Linux) and then try running again. This will delete any saved Postman data you have, but for a newly-installed instance that's not an issue.
Go to installation folder of Postman:
C:\Users\Davoud\AppData\Local\Postman
delete the older version's folder. It fixed my problem. Actually I also deleted update.exe too.
Can you try just by deleting the “Postman” folder or renaming it to “Postman.old” from below two locations and then reinstall the latest version from here and see if that helps?
C:\Users\<user>\AppData\Local and C:\Users\<user>\AppData\Roaming
I tried it as I was facing the same issue and, it solved for me.
Use this: It worked for me.
pkill -fi Postman
For Windows 10 - in my case, I have to:
Open Task Manager and kill/end the Postman application.
Go to %appdata% and search the "Postman" folder.
Inside "Postman" folder, select the "Postman_Config" folder1. Delete it.
Try to open your Postman instance again.
1 The "Postman_Config" folder contained (in my case) another folder called "0" and inside this folder, an "userconfigs.json" file - which only contained these characters:
{}
If you have additional information,please, make a copy of these files in order to have a backup - if needed.
For Windows -
Kill the process that says, postman from the task manager
Run the installer again, it resolved the issue for me.
disable hardware acceleration in the Postman menu in macOS, or the Help menu in Windows or Linux.
I had a similar problem installing Postman when I was on a VPN (on Windows). It started up but then got a popup error saying "TypeError: Cannot read property 'id' of undefined," and a blank white screen afterwards. So I uninstalled it, deleted any Postman folders, turned off the VPN, and re-installed it with no problems! After it installed successfully, I was able to turn on my VPN and had no further issues.
For reference, I had these errors in my C:\Users\<user>\AppData\Roaming\Postman\logs\renderer-requester.log file
[20076][1645655031650][requester][info]["Migrations: Committing IndexedDB upgrade"]
[20076][1645655031665][requester][error]["Could not complete migration.",{"name":"Error","message":"Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.","stack":"Error: Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:477:1448541\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:3000934\n at Ve (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996146)\n at ze (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996903)\n at IDBOpenDBRequest.<anonymous> (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2997272)"},{"0000_initial":"started","0001_add_archived_resources_table":"started","0002_add_variable_sessions_table":"started","0003_add_editor_tables":"started"}]
[20076][1645655031673][requester][error]["Migration: Could not complete migration.",{"name":"Error","message":"Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.","stack":"Error: Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:477:1448541\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:3000934\n at Ve (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996146)\n at ze (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996903)\n at IDBOpenDBRequest.<anonymous> (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2997272)"},{"0000_initial":"started","0001_add_archived_resources_table":"started","0002_add_variable_sessions_table":"started","0003_add_editor_tables":"started"}]
[20076][1645655031676][requester][info]["booted - requester"]
[20076][1645655031686][requester][error]["Could not complete migration.",{"name":"TypeError","message":"Cannot read property 'id' of undefined","stack":"TypeError: Cannot read property 'id' of undefined\n at t.default (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:477:1193039)\n at
......
I have set up an elastic beanstalk deployment of Drupal to host a Drupal built website.
When I start up my ec2 instance, I go through the installation steps of setting up Drupal.
However, when the instance is Restarted, or Stopped, restarting the instance goes back to this page!
How can I configure the instance so that these installation steps do not need to be repeated even when the instance goes down. This is quite worrying as I am looking to host my website this way.
Any help on this issue would be greatly appreciated!
This step means that drupal can't find database or it can find it but installation is not done yet (required tables are not created). So if you pass installation and you see again this screen it can mean 2 things:
Your database configuration is lost, so drupal can't find DB.
DB configuration file is ok, but DB it self is lost so configuration must be done again.
So first check what is the problem in your case and then solve it. Probably since you are installing in instance, DB configuration is then recorded and then lost when your box expires. If so...find a way to make permanent change do config file (should be /sites/default/settings.php).
I was adding modules and installing them yesterday and I get this error now: "The website encountered an unexpected error. Please try again later." I can't login at all or access anything from the url. I tried deleting the modules but it still isn't working. Any suggestions?
To expose what's up, add the following line to your settings.php
$config['system.logging']['error_level'] = 'verbose';
What's happening is that the code is failing fairly deep into the execution and it may not even be a syntax error. In my case, it was the MySQL user was not associated with the MySQL DB, so the connection was failing as what the application
The models are probably still in database even though you deleted it from code ?
If you have access to drush, you can in-install it via drush. If not you need to change entries in the database tables
We recently upgraded our Single Instance API Manager from 1.90 to 1.10. Upgrade seemed to be mostly successful, but anytime I try to load one of the services in the publisher, it freezes up and the log reports:
Error while retrieving the lifecycle actions for lifecycle: APILifeCycle in lifecycle state: null
at org.wso2.carbon.governance.api.common.dataobjects.GovernanceArtifactImpl.getAllLifecycleActions(GovernanceArtifactImpl.java:783)
at org.wso2.carbon.apimgt.impl.APIProviderImpl.getAPILifeCycleData(APIProviderImpl.java:3306)
... 101 more
Caused by: org.wso2.carbon.registry.core.exceptions.RegistryException: Resource at '/_system/governance/apimgt/applicationdata/provider/<User>/<API>/v1/api' not associated with aspect 'APILifeCycle'
at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.getResourceAspect(EmbeddedRegistry.java:2592)
at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.getAspectActions(EmbeddedRegistry.java:2627)
at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.getAspectActions(CacheBackedRegistry.java:474)
at org.wso2.carbon.registry.core.session.UserRegistry.getAspectActionsInternal
And Also (I replaced sensitive info with <>):
org.wso2.carbon.registry.core.exceptions.RegistryException: Resource at '/_system/governance/apimgt/applicationdata/provider/<USER>/<SERVICE>/v1/api' not associated with aspect 'APILifeCycle'
at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.getResourceAspect(EmbeddedRegistry.java:2592)
at org.wso2.carbon.registry.core.jdbc.EmbeddedRegistry.getAspectActions(EmbeddedRegistry.java:2627)
at org.wso2.carbon.registry.core.caching.CacheBackedRegistry.getAspectActions(CacheBackedRegistry.java:474)
I have spent a ton of time trying to locate the code that this error occurs with no luck (I'm not a java developer anyway). Do you guys have any ideas on what is causing this error? All of the services that are registered were registered pre-upgrade.
UPDATE:
As suggested below, this is because the migration is failing. I dug in a little deeper and discovered that the migration is failing due to bad SQL. Within the migration client, specifically the file MigrateFrom19To110.java, on Line 189 it is executing an Ad Hoc SQL statement :
"UPDATE IDN_OAUTH2_ACCESS_TOKEN SET AUTHZ_USER = ? WHERE AUTHZ_USER = ?"
This throws this error:
Must declare the scalar variable "#P0WHERE"
It seems like there is something wrong with the code that is building this statement, because the #POWHERE seems to be coming from the jdbc driver code. Can anyone shed more light on this?
Did you run the migration client during the upgrade? seems like migration hasn't gone correctly. Steps are given in https://docs.wso2.com/display/AM1100/Upgrading+from+the+Previous+Release
The reason I'm saying this is because as part of the migration we attach 'APILifeCycle' lifecycle to existing apis. Since the error says the api is not associated with the lifecycle I can guess the problem is with the migration
I'm trying to install some packages on Sitecore 6.2 solution. I'm receiving a strange packager error:
“Package generation failed: Root element is missing" . I checked logs and nothing appear.
Sitecore’s packager wasn't able to generate a package.
It appears that in the process of generating the zip, it needs to access the temp folder during the creating process.
I meet this error few times and it doesn't work allways to give access just for AppPoolIdentity.If it's not working give access for role Everyone.
Here you find a nice article about this error .
I think a probable reason for this failure could be that you created package of an item or a number of items, but its template might be missing.
Alternatively, please check that your AppPoolIdentity, (ideally Network Service, to check AppPoolIdentity Name, goto IIS Manager, Application Pools and select the AppPool of your website, and in Action Pane on right side, say Advanced Settings, you will be able to see the Name of Process Model -> Identity) has read-write rights on C:\Windows\Temp directory.
Do let me know after trying the above two things on your solution
Hope this helps!
Regards,
Varun Shringarpure