MailEnable Webmail - messages and folders will not display - webmail

OS is Win2012
Plesk 11.5 panel
ME Pro 7.5
ME diagnostics are green
There have been no configuration changes to the server. It's been running without issue for some time.
Today found that folders will not display in webmail, and therefore no messages are accessible in webmail. This includes the inbox, deleted items, sent items, etc... If I create a new folder, it says it is created successfully, and in fact I can see the directory appear on the file system. But it will not display in the web browser. I've tried with Chrome, IE, and Firefox.
The only branch that displays are the Mailbox-username and the My Files. Selecting the Mailbox-username branch I get the summary in the main pane that lists the number of messages in the inbox, junk e-mail, and deleted items as well as other data. but I am unable to access any of the folders themselves. They are not even listed in the navigation pane.
As far as I can tell, file permissions are correct. I have even run MEINSTALLER to run the verification. And procmon is not showing any access denied errors.
I have tried removing _index.xml from the user root as well as individual folder directories.
No errors are displayed on the page.
Event log does show errors that about not being able to access _activity.blk. However, those are for mailboxes that no longer exist. But other than that, no other errors found.
I'm out of ideas.
thank you,
michael

The issue is caused by a .Net Framwork update (KB3186539) . The update breaks webmail so that it will not display folders and messages. This affects multiple versions of MailEanble webamil, including the current version.
Here is a ME thread on the topic
http://forum.mailenable.com/viewtopic.php?f=7&t=41791
At this time, while there are beta updates for ME, if you have an older version or do not wish to upgrade to a beta, the work around is to make a change to web.config.
In the Mail Enable\bin\Netwebmail directory and adding the following between the and tags:
<caching><cache disableExpiration="true"/></caching>
Updating the web.config resolved the issue on our server.

Related

How to fix msedgewebview2 error in VS2022 when admin?

I have installed the relatively fresh Visual Studio 2022 on a Windows installation. The work I do often requires administrative privileges (local IIS). To do this I have two users, one 'normal' account that is logged in to Windows and one administrator account. When starting VS2022 with the administrator account, an error keeps coming. It happens especially during debugging and it reads as follows:
Microsoft Edge can't read and write to its data directory:
C:\Users\<administrator_user>\AppData\Local\Temp\VSWebView2Cache\<guid>\EBWebView
What appears to happen is that Microsoft Edge WebView2 (msedgewebview2.exe) is running as the user that is logged in to Windows, while trying to write temporary files for the administrator user where it does not (and should not) have write or read access.
Here we can see the process details that says the application user is the logged in user and not the administrator:
Does anyone know how to fix this issue?
The error happen even when I run debugging on a .net 5 console application. In that particular situation I don't see why it needs to run anything in a WebView instance, but apparently some background process is running something anyway. Is this something that can be turned off?
My best solution so far is to create a shared folder.
I decided to make C:\Users\<administrator_user>\AppData\Local\Temp\VSWebView2Cache\ shared. The "VS" prefix indicates that this is a Visual Studio-specific folder, and I think it is acceptable that my normal user can have access to that folder as it seems to contain temporary Visual Studio files.
To do so I logged in to Windows with the administrator account.
I navigated to the folder and made it a shared folder. I added my no-admin user with "Read/Write" privileges.
I then tested by logging out of the admin account and into my no-admin account. There I first tried the full path in File Explorer and was granted access to the folder. I then tested with VS2022 and during debugging no error box appeared and files were generated in the folder.
If anyone finds a better approach, I'd really like to hear about it. Also if you have knowledge to why this approach is either good or bad, that would be highly appreciated as well.
I only had to create the folder "VSWebView2Cache" with my normal Windows account and after that it worked.

Cannot install latest version of moodle4mac on Catalina

I'm trying to install moodle4mac on Catalina via a .dmg file. The .dmg file mounts okay. However, when I try to drag the MAMP folder to the Applications folder, I get the message "The operation can’t be completed because you don’t have permission to access some of the items."
When install dialog is showing 4 folders;
.DocumentRevisions-V100
.TemporaryItems
.Trashes
.fseventsd
The first three have no go signs on the folders suggesting that these are the problematic ones. I have checked the read/write permissions of the Applications folder, which looks fine. I have also run sudo spctl --master-disable which gives me the opportunity to download apps from anywhere, but this does not make any difference.
Any pointers greatly welcome!
Okay. It turns out the culprit was Sophos Home Antivirus. There was no indication in any of the error messages that Sophos was blocking this, hence I did not put two and two together. However, a warning message about the mounted volume popped up this morning, and I was able to trace this back to Sophos. It would be great if Sophos / MacOS could provide more detailed messages regarding such errors in future.

Why error "Access Denied" when creating a adhoc report in JasperReports Server?

When adding new users to the JasperReports Server (v6.2), everything works fine.
The new user
can use predefined adhoc reports
can use predefined reports
is able to change predefined reports
But if the user tries to create a new adhoc report, he gets an error Access is denied. Unfortunately the error message (it is a very long log) doesn't show to which component or folder the access is denied.
What I tried so far:
Recreating the user
Changing rights for the Domain (tried Read-Only / Execute-Only)
Checked folder structure if rights are set correctly (they appear to be correct)
What am I missing?
Turns out there has been a change in the required rights for the Data Source from version 6.0.x on (comment from here):
Appears to be a regression in 6.0.1 and at least a Read-Only permission on a Data Source is now required,
while Execute-Only was sufficient in 5.5.
The adhoc creation works without a problem now.

Packages not appearing in proget feed

I am using proget to upload packages, I am manually uploading from disk, but when I go to check if the package exists in the feed it isn't there. When I logon to the server which is hosting proget and go to the PackagesRootPath I can see the package is indeed on the server!
Any ideas why it's not showing up in the feed?
p.s. I have restarted the website/application pool and ProGet service and still doesn't work.
If you're not seeing any packages in the web application (and you've verified that they are, in fact, in the right place on disk), this means that the packages aren't getting indexed by the ProGet Service.
Since you've already restarted the ProGet web service, it's likely a problem with the individual package.
Check to see if there are "indexing errors" in the admin section; this will give some insight into what the problem might be. Often times, the file name does not match the package name/version; this is a requirement. If you're package is named MyFoo and is version 3.0.1, it must be MyFoo.3.0.1.nupkg and have an appropriately named MyFoo.nuspec within it.
If there are no errors logged, then you can try to run the service interactively. Simply stop the Windows service, then run the .exe file and select the appropriate option to run.
Another option to verify that the indexing is working OK is to pull a package from a remote connector (like JQuery or something), then drop that package in another feed (that doesn't use a connector).

What can cause a display bug on different devices in a meteor web app and only once bundled

My problem is that my content does not show at all on particular device/browser and only once bundled. The wep app display correctly in debug (running it from meteor) whatever the device or browser are.
EDIT : I can see the navbar and the footer but not the yield on affected devices/browsers
Affected devices/browser known to date are Chrome on Nexus 4 (not on Note3) and Dolphin on Note 3.
Dev environment is Windows and prod is Linux.
I've also tried to run the app through meteor directly on server and the problem is not here but is back even when I bundle the app from the server.
Any idea about what can cause that and/or how to troubleshoot that?
EDIT 2
I can finally confirm that it's a client side bug.
Here is the error from chrome console on the device
Exception from Deps recompute function: ReferenceError: Lists is not defined
at Object.Template.layout.helpers.lists (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:31:25567)
at http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:10:5624
at Object.e.call (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:27:20793)
at HTML.DIV.HTML.UL.UI.Each.UI.block.e [as __sequence] (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:27:28178)
at http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:10:4102
at http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:9:3419
at a (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:2:4791)
at n.extend._compute (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:2:5846)
at new e.Computation (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:2:5183)
at Object.n.extend.autorun (http://example.com/8f6c9295e0ef7b38e613447d9a44d5c7af448efa.js:2:7042)
But the Lists collection is defined, published and subscribed. And the weirdest part is that everything works well when debugging through Meteor
In my specific case, Collections definitions were located in a /collections folder at the root of the app. That caused the app to load them after the /client folder but only once deployed and on some devices/browsers only!
To fix that, I've just move the /collections folder into /lib, bundled it again, push it to the server and everything now works flawlessly whatever the device/browser is.