on 2023 Mar 16 5:18 PM
I made one small change to a query (checked the Retrieve Duplicate Rows box), and now the report will not open and returns the error "The action cannot be performed. (Error: INF WIS 30650)". I verified that the wid file exists, imported it into the Webi Rich Client, and received the same error. I also tried the Fiori launchpad and received an error (WSR 00400).
I actually had two versions of the report and unfortunately made the same change to both versions at the same time, and both have the error. I do have a 1 year old version on our test server; I moved that report to production and made the change again I got the same error. However, I am able to make that change successfully in test, and then move it to production.
So what would cause this error in production but not test?
We are on 4.2 SP9 Patch 7. There are a number of bugs introduced in this version, as is always the case unfortunately.
Request clarification before answering.
maybe the problem is related to the connection. Check if there are differences in the connection definition/driver between test and prod env.
also see KBA 2600202 - The action cannot be performed (WIS 30650) ***MASTER KBA***
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, do you mean the CMS connection? The report connection is the same, but I don't think it's even getting to that point when it brings up the error. I don't have access to check the CMS connection, I think that's in the setup isn't it?
Thanks for the link; I had searched the knowledge base on that error and that did not come up; I must have had other filters set. I looked through every one of those notes though and none apply to my situation.
Strangely I cannot duplicate the problem today -- I can move the old report from test to prod, make the change, save it, and it opens fine. But the corrupted report is still corrupted. Also strange is the sizes of both corrupted reports show they contain the data, but I had purged the data before saving. This tells me that there was an issue during the save process. But for it to be consistent with that report/change and not with others does not make any sense.
User | Count |
---|---|
48 | |
6 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.