Postman native app keeps failing to open #4602

connelhooley · 2018-05-25T09:42:34Z

Describe the bug
Postman keeps failing to open. The issue appears intermittent. Sometimes the splash screen comes up. Sometimes not even that appears. If I try and open Postman several times, then I can see several Postman instances running in the background inside Task Manager. I then kill all of the Postman processes and sometimes it begins to work again for a little while, it then regresses again.

To Reproduce
Steps to reproduce the behavior:

Open Postman via a start menu shortcut

Expected behavior
The splash screen should appear, followed by the main window.

Screenshots
N/A

App information (please complete the following information):

App Type: Native app
Postman Version: 6.1.2
OS: Windows 10

Additional context
I've tried modifying the shortcut in my start menu to disable GPU (as I saw a recent bug that recommended turning it off if it fails to open properly) but this doesn't appear to fix it:
C:\Users\USERNAME\AppData\Local\Postman\Update.exe --processStart "Postman.exe --disable-gpu"

The text was updated successfully, but these errors were encountered:

connelhooley · 2018-05-25T09:55:58Z

Just tried opening from the command line. I get the message:
Shared window not present

I then went back to Task Manager and killed all instances of Postman.

I then tried again from the command line and got this error. This time the app stopped during the splash screen:

ORM initialization failed:  { Error: EPERM: operation not permitted, rename 'C:\Users\username\AppData\Roaming\Postman\archive~' -> 'C:\Users\username\AppData\Roaming\Postman\archive'
  errno: -4048,
  code: 'EPERM',
  syscall: 'rename',
  path: 'C:\\Users\\username\\AppData\\Roaming\\Postman\\archive~',
  dest: 'C:\\Users\\username\\AppData\\Roaming\\Postman\\archive' }
Uncaught errors TypeError: Cannot read property 'collections' of undefined
    at bootstrapModels (C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\main.js:94:27)
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\bootstrap-models.js:26:14
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\waterline\lib\waterline.js:918:25
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\waterline\lib\waterline.js:719:25
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\waterline\node_modules\async\dist\async.js:952:25
    at iteratorCallback (C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\waterline\node_modules\async\dist\async.js:995:17)
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\waterline\node_modules\async\dist\async.js:847:20
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\async\lib\async.js:52:16
    at done (C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\async\lib\async.js:241:17)
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\async\lib\async.js:44:16
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\common\adapters\waterline-shared-nedb.js:320:29
    at newArguments.(anonymous function) (C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\executor.js:29:17)
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\persistence.js:305:26
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\persistence.js:138:23
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\storage.js:105:30
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\node_modules\async\lib\async.js:485:30
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\storage.js:102:70
    at FSReqWrap.oncomplete (fs.js:135:15)
Uncaught errors Error: Callback was already called.
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\waterline\node_modules\async\dist\async.js:844:36
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\async\lib\async.js:52:16
    at done (C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\async\lib\async.js:246:17)
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\async\lib\async.js:44:16
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\common\adapters\waterline-shared-nedb.js:342:18
    at newArguments.(anonymous function) (C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\executor.js:29:17)
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\persistence.js:308:15
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\persistence.js:140:12
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\storage.js:105:30
    at storage.flushToStorage (C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\lib\storage.js:56:97)
    at C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\node_modules\async\lib\async.js:597:23
    at fn (C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\node_modules\async\lib\async.js:582:34)
    at Immediate._onImmediate (C:\Users\username\AppData\Local\Postman\app-6.1.2\resources\app.asar\node_modules\nedb\node_modules\async\lib\async.js:498:34)
    at runCallback (timers.js:781:20)
    at tryOnImmediate (timers.js:743:5)
    at processImmediate [as _immediateCallback] (timers.js:714:5)

harryi3t · 2018-05-25T12:58:42Z

@connelhooley Can you try our latest canary build and follow the steps mentioned here
#4594 (comment)

jemerald · 2018-05-28T22:57:19Z

@harryi3t the workaround to disable GPU fixes the issue for me. But is there going to be a permanent fix coming soon?

connelhooley · 2018-05-29T14:05:03Z

I'm still seeing the issue in the latest canary build, with the environment variable set. I'll try and run it via the command line again to get some logs.

I can also confirm a few other devs on my team are seeing the same behaviour.

connelhooley · 2018-05-29T14:08:41Z

Disabling hardware acceleration
ORM initialization failed:  { Error: EPERM: operation not permitted, rename 'C:\Users\username\AppData\Roaming\PostmanCanary\window~' -> 'C:\Users\username\AppData\Roaming\PostmanCanary\window'
  errno: -4048,ppUpdate' }
  code: 'EPERM', name: 'booted', namespace: 'requester' }
  syscall: 'rename',)
  path: 'C:\\Users\\username\\AppData\\Roaming\\PostmanCanary\\window~',
  dest: 'C:\\Users\\username\\AppData\\Roaming\\PostmanCanary\\window' }
Uncaught errors TypeError: Cannot read property 'collections' of undefined
    at bootstrapModels (C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\main.js:107:27)
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\bootstrap-models.js:26:14
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\waterline\lib\waterline.js:918:25
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\waterline\lib\waterline.js:719:25
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\waterline\node_modules\async\dist\async.js:952:25
    at iteratorCallback (C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\waterline\node_modules\async\dist\async.js:995:17)
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\waterline\node_modules\async\dist\async.js:847:20
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\async\lib\async.js:52:16
    at done (C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\async\lib\async.js:241:17)
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\async\lib\async.js:44:16
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\common\adapters\waterline-shared-nedb.js:320:29
    at newArguments.(anonymous function) (C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\executor.js:29:17)
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\persistence.js:305:26
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\persistence.js:138:23
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\storage.js:105:30
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\node_modules\async\lib\async.js:485:30
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\storage.js:102:70
    at FSReqWrap.oncomplete (fs.js:135:15)
Uncaught errors Error: Callback was already called.
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\waterline\node_modules\async\dist\async.js:844:36
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\async\lib\async.js:52:16
    at done (C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\async\lib\async.js:246:17)
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\async\lib\async.js:44:16
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\common\adapters\waterline-shared-nedb.js:342:18
    at newArguments.(anonymous function) (C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\executor.js:29:17)
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\persistence.js:308:15
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\persistence.js:140:12
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\storage.js:105:30
    at storage.flushToStorage (C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\lib\storage.js:56:97)
    at C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\node_modules\async\lib\async.js:597:23
    at fn (C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\node_modules\async\lib\async.js:582:34)
    at Immediate._onImmediate (C:\Users\username\AppData\Local\PostmanCanary\app-6.1.3-canary01\resources\app.asar\node_modules\nedb\node_modules\async\lib\async.js:498:34)
    at runCallback (timers.js:781:20)
    at tryOnImmediate (timers.js:743:5)
    at processImmediate [as _immediateCallback] (timers.js:714:5)

harryi3t · 2018-05-31T07:21:44Z

@connelhooley That's weird. Normally the user should have permissions on the appData directory.
Can you try

Running the app as administrator. If this works then we know the issue is with permissions.
If the above works, can you try changing the owner of the C:\Users\username\AppData\Roaming\PostmanCanary directory to yourself recursively.

Am not sure how to change owners in windows, but maybe right click on Postman -> properties -> securities might help.

connelhooley · 2018-05-31T15:41:57Z

I have checked the permissions for the %APPDATA%\PostmanCanary directory and I have access to all the files. It's impossible to say for sure, as the bug is intermittent, but I have been unable re-create it when running the application as administrator. Is there a way of knowing which files it can't read? Running as admin isn't an option for me as my admin account doesn't have access to the internet (company policy).

connelhooley · 2018-06-08T13:17:31Z

Just realised the filename is in the exception message, my mistake.

I've just had Postman also fail to rename the "archive~" file in the same directory so its probably something on my work machine that's stopping the renames somehow.

RobertTBoyerPhD · 2019-03-28T22:23:28Z

I am running into the same hang on start issue.
Running by hand I found a EPERM failure, which I tracked down to a read-only setting on both of the directories C:\Users\Owner\AppData\Roaming (and I changed ...\Local for good measure).
Although it fixed the permission failure, it still hangs on start-up. I can only see the window with icon, but no menu. The output from by-hand-execution is:

C:\Users\Owner\AppData\Local\PostmanCanary>
1553811507687 main info "Booting PostmanCanary 7.1.0-canary01, win32-6.3.9600 on x64"
1553811507688 main info "EventBusinitialize - Success"
1553811507696 main info "UpdateHandlerinit - Success"
1553811507698 main info "RuntimeExecutionServiceinitialized: Success"
1553811507776 main info "ProtocolHandlerinit - Success with status: true]"
1553811508002 main info "PluginHostbootHost: Booted - 1"
1553811508521 main info "Bootstrap-modelsbootstrap - Success"
1553811511415 pluginHost info "Booting Plugin Host for PostmanCanary 7.1.0-canary01, win32-6.3.9600 on x64"
1553811511421 pluginHost info "PluginsHost: Booted"
1553811511431 pluginHost info "PluginInstallationService~_shouldReInstallPlugin",{"installedVersion":"0.0.10","currentVersion":"0.0.10"}
1553811511436 pluginHost info "PluginInstallationService~_shouldReInstallPlugin",{"installedVersion":"0.0.1","currentVersion":"0.0.1"}
1553811511438 pluginHost info "PluginsHostinstallOrUpdatePlugins: Synced all plugins",[{"pluginId":"postman.openApi","version":"0.0.10","status":"skipped"},{"p
luginId":"postman.sample","version":"0.0.1","status":"skipped"}]
1553811545945 main info "MainAppEvents - Received booted event for process shared"
1553811572966 main info "UpdateHandlerapp-update-events - Received event",{"name":"checkForElectronVersionUpdated","namespace":"appUpdate"}
1553811572968 main info "MainAppEvents - Received booted event for process requester"

wlarch · 2020-01-16T20:04:23Z

I had the same issue because I launched Postman with root privileges. The solution is to set permissions and ownership correctly for my user :

$ sudo chown -R user:user /home/user/.config/Postman/

terrynguyen255 · 2020-08-05T04:41:39Z

To me, @wlarch 's answer is the most helpful solution on the internet.

I had the problem when I updated Postman:

Downloading the newer version required root privilege, so did the update progress
After installed, executing Postman without sudo (like launching from app dock)

@wlarch saved my day 👍

harryi3t self-assigned this May 25, 2018

harryi3t added the needs-investigation label May 25, 2018

harryi3t added the pending-close label May 25, 2018

harryi3t added waiting-for-response and removed pending-close labels May 31, 2018

connelhooley closed this as completed Jun 8, 2018

cailyoung mentioned this issue Mar 5, 2019

Add support for installing in user profiles on share path #4559

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Postman native app keeps failing to open #4602

Postman native app keeps failing to open #4602

connelhooley commented May 25, 2018

connelhooley commented May 25, 2018

harryi3t commented May 25, 2018

jemerald commented May 28, 2018

connelhooley commented May 29, 2018 •

edited

Loading

connelhooley commented May 29, 2018

harryi3t commented May 31, 2018

connelhooley commented May 31, 2018

connelhooley commented Jun 8, 2018

RobertTBoyerPhD commented Mar 28, 2019

wlarch commented Jan 16, 2020 •

edited

Loading

terrynguyen255 commented Aug 5, 2020

Postman native app keeps failing to open #4602

Postman native app keeps failing to open #4602

Comments

connelhooley commented May 25, 2018

connelhooley commented May 25, 2018

harryi3t commented May 25, 2018

jemerald commented May 28, 2018

connelhooley commented May 29, 2018 • edited Loading

connelhooley commented May 29, 2018

harryi3t commented May 31, 2018

connelhooley commented May 31, 2018

connelhooley commented Jun 8, 2018

RobertTBoyerPhD commented Mar 28, 2019

wlarch commented Jan 16, 2020 • edited Loading

terrynguyen255 commented Aug 5, 2020

connelhooley commented May 29, 2018 •

edited

Loading

wlarch commented Jan 16, 2020 •

edited

Loading