Asteward Posted February 1, 2023 Posted February 1, 2023 After updating Publisher with the latest update (2.0.3 to 2.0.4) I tried to open the file and was given this message (please see attched). For conteext the the Publisher file and all linked images and file were stored on a local NAS. Thank you Quote
Staff Pauls Posted February 1, 2023 Staff Posted February 1, 2023 I'll have to get a developer to look at that file Asteward 1 Quote
anweid Posted February 1, 2023 Posted February 1, 2023 Oooooh, what a pity! I can also not read your file, but get the same error message. With one document of mine (from my post 'weird pin behaviour'), several other people got this error message, too. Today I tried to load that old document of mine into Publisher version 2.04 on a second PC, and it worked properly. Therefore, I thought this bug was already fixed in the meantime, but apparently not. As a reminder: I myself could always properly read my document on the PC on which I originally wrote it. Other people could not read that document, but received the above error message instead (directly after version 2.0 came out, and no other was available). This bug is the reason why I currently do not use Publisher 2 anymore – I always fear that any document I write will be screwed up, so that I cannot properly load it anymore in the future. Writing and loading files should be the most reliable features in any software, but – alas! – that's not the case with Publisher anymore. I'm depressed... Andreas Weidner Quote
walt.farrell Posted February 2, 2023 Posted February 2, 2023 1 hour ago, anweid said: I myself could always properly read my document on the PC on which I originally wrote it. Other people could not read that document, but received the above error message instead (directly after version 2.0 came out, and no other was available). You may have been experiencing a problem that was resolved in 2.0.4. There is a different one recently reported, which @Asteward may be experiencing, that 2.0.4 did not fix. One of the Moderators has suggested that it may be due to Saving with History, and an error interpreting the saved History data within the file when reopening. Perhaps the developers will be able to confirm that with the file provided here. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.