12:14:37,697 DEBUG (http-executor-threads - 11) sendRequestInner processing component exif, of type Metadata 12:14:32,386 DEBUG (EJB default - 2) IdentityManager.listCatalogs() invoked. 12:14:29,432 DEBUG (http-executor-threads - 11) using media engine localhost:40372 12:14:24,255 DEBUG (http-executor-threads - 11) Starting upload I’ve switched the server to debug mode and find the following in the server log: Unfortunately I get no response from server when uploading. What I’ve done is to replace the session id in the request header by the api token. I assume (even if the documentation is not describing this) that when uploading I still have to use the “old” http upload. NET, connection to restAPI will be established by an API token, which is working well so far. The next step is to sacrifice my dog.I’ve a question on uploading assets to Portfolio 2016 by restAPI. I've tried changing permissions/ownership. Still, can't remove the old font vault and it's remaining fonts.įont's that remain in the vault count: 93 entriesĬ:Users\\AppData\Local\Extensis\Suitcase Fusion\Suitcase Fusion.fontvault\SA\I\OTPS\Adobe Systems\Caliban, Eurostyle (various), Helvetica (various), Myriad Pro (various).Ĭ:Users\\AppData\Local\Extensis\Suitcase Fusion\Suitcase Fusion.fontvault\SA\I\OTTT\Microsoft\Mistral\2.10\1602175480\Mistral.TTF I've rebooted many times after attempting different voodoo medicines. Extensis support only gives the same tips they've been handing out for years – none of which work. I've searched the web numerous times for help. I'd like to give you a concise list of what all I've tried but I've been messing with this so long I've lost track. I've tried numerous ways to remove the vault and these leftover fonts. The vault seems to be locked by some other process and also the leftover fonts that are there. ![]() The message: 'Could Not Open The Font Vault At This Location'. When I tried to open my new install, it wouldn't open. As suggested, I moved my font vault to a different location (desktop) and planned to move it back with fonts intact after my upgrade. This came about as I was upgrading from Suitcase version 5 to 6. ![]() Once again ran into the remove font vault problem. ![]() However the version of Windows, or Mac OS, or version of Suitcase matters little since this has been an ongoing problem forever. Suitcase Fusion for Windows font vault problem.
0 Comments
Leave a Reply. |