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.
Related
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.
I'm using two laptops and stored my C# code in OneDrive.
I am aware that sharing code via OneDrive is not be the best approach, but that's what I'm dealing with now.
I noticed that on laptop 1 I have to define the following path to the data file (mdf):
C:\Users\ Diet\OneDrive\Personal\VisualStudio2019\Repos\project\project\App_Data\data.mdf
On laptop 2, the path is different because the user I'm logged in with has a different name (or at least that's what I believe is the cause)
C:\Users\ Dieter\OneDrive\Personal\VisualStudio2019\Repos\project\project\App_Data\data.mdf
Updating this in the Web.config fixed the connection to the database, BUT building the solution still returns an error, also related to a cloud operation, hence why I think it is caused by the path in OneDrive...
The error message:
CSC : error CS0041: Unexpected error writing debug information -- 'The cloud operation was unsuccessful.
I welcome your insights. Thank you for helping me out.
I have my projects stored in OneDrive and had this same issue. The fix was to set the entire Project folder contents to "Always keep on this device".
Seems that building the solution in VS was attempting to write to files that were not cached locally from OneDrive. As soon as I changed the setting, the build worked!
I was also storing my project on OneDrive, got the same error after installing a new ssd.
Rebuilding the solution was enough for me.
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.
The project I am working on has been having the issue of stored credentials in the rdl files not being reflected on the server we deploy to and it seems to be inconsistent in its behavior. We are NOT using a shared data source because we have to generate the data source connection dynamically so each report has its own data source embedded (even though they are all identical) and it has the credentials stored. I look in VS at the rdl file and see the credentials are stored, deploy to our test server, look on the test server and the credentials are set to "Not Required". Other strange thing is this doesn't happen to all reports all the time, some reports keep their credentials but not every time. It all seems very random.
Some settings and facts about the project that may be useful:
Using SQL Server 2008 R2
Using Visual Studio 2012 to deploy
ReportProject setting OverwriteDatasets = True
ReportProject setting OverwriteDataSources = True
I have had similar issues, delete the report on the SSRS server first, then deploy the report. SSRS does retain certain attributes of report it is very inconsistent when it does this and this is more of a workaround than an answer, but it works for me.
Environment: Visual Studio 2005, SSRS 2005 with Sharepoint 2007 integration
Have a project with two reports and one data source. Has already been deployed to production sharepoint farm.
Needs an enhancement. Change properties to point to test farm and try to deploy:
"Access to the path 'c:\documents and settings\\my documents....\RegLog.rds' is denied"
Path is correct, and properties of files are read-only (because the files are checked in to source control). Now, I understand that SSIS packages won't execute if they are read-only (which is stupid) but I am fairly certain I have deployed SSRS reports and data sources before without having to check them out first. On the other hand, I do know that deployment requires the file to be modified in some way. But the modified version will be in Sharepoint, not in visual studio, and its extension will be .rsds, not .rds (which is the VS name)
I also think it is unusual that the path has been lower-cased. Shouldn't matter in Windows, but it's the first time I have ever seen "documents and settings\\my documents" not all initial caps. So maybe it matters. But this project deployed before without problem.
I was having this problem as well. To fix it, I did a build of the report project (which before converting from 2005 to 2008 I'd never had to do before). Once I did that, it worked just fine.