TM1 Forum

Guys,

I'm getting the erro below when trying to open an excel file in TM1 web. I've managed to open the file on the server in the excel version there and I've also checked the file extension. Any ideas????

Cheers,

Jim.

Jim, when the spreadsheet is being converted to the ultimate HTML necessary for TM1 Web, Excel is automated in the background in order to analyse the spreadsheet. HRESULT's are errors occuring in this automation process. I'd check your spreadsheet for anything funky: corrupt named ranges; oddball shapes, pictures or graphics; any VBA trapping workbook or application events (maybe any VBA full stop); check for the used range on each sheet not being anything too dramatic; etc etc.

Thanks for that. I think you may be right. I inherited this from an IBM POC so god knows what they did in there!!

It's got nothing to do with any hidden cells, corupt files or anything else. I have uploaded a direct slice of a cube with no changes and I still get the same error.

You can also get that message when the service account that TM1 is running under doesn't have the proper rights to the TM1Web folder(s).

I got a message similar to this when I started testing in 10.1 and as mentioned by tomok it was due to the whole privilege set up (not that anything had changed since upgrading...)

Got around it for now by changing the Excel service to run under administrator log-on instead of the local.
Quick way to check is starting it as a standalone instance via the prompt.

Cheers guys,

I was starting to lean this way as pass through authentification was failing within IIS.

I'm glad I'm not sitting next to a brick wall right now as it would hurt.

Here's what happened:

I changed teh excel user to a local admin it looked like it was going to work, however it came back with an error saying process failed. I then opened a view to make sure that worked and it did. After this I tried the excel sheet again and low and behold it worked. How bizzare.

Luckily (Or not) I had another service running with an excel sheet uploaded and I was able to replicate the exact same behaviour. I tried opening an excel sheet without success, I then opened a view and low and behold the excel sheet started working.

This is just plain old bizzare. It can't be to do with cached values as the views are different. (In the second test case the cube also)

Has anybody else met anything like this??

Cheers,

Jim.

This is the error I get. (I have restarted the server. Once again I get the error, then again if I open a view it starts working.)

jim, I am getting the same "Operation Failed" error and cannot seem to find a solution. Any luck

erakeman wrote:jim, I am getting the same "Operation Failed" error and cannot seem to find a solution. Any luck

What exactly have you tried?

Hi All,

I'm working in TM1 v10.1.0

I have a TM1 worksheet with an active form published to TM1 web. I have been testing data entry - I enter data, then hit an action button that runs a ti to save data across versions and send data from input cube to reporting cube. 9 times out of 10 it works flawlessly. 1 time in 10 I get the same Operation Failed error message. I then have to close the application and re-open it and it works fine again.

Out TM1 support have taken a look at it and have suggested that it is a drop in the network communication as it works most of the time. Not sure whether that was a credible argument or a cop out. Either way I'm not sure exactly how I investigate that to rule it out or not.

Anyway - thought you may be interested to know that I get the same error - albeit inconsistently.

Cheers

Mike

erakeman wrote:jim, I am getting the same "Operation Failed" error and cannot seem to find a solution. Any luck

We didn't take it any further. The customer added to their documentation that after any restart the view has to be opened to make sure it is available. This does seem (from the posts) very sporadic and something that is not easily solved. If was down to network connectivity why would it always fail the first time for us? Oh and web and TM1 are on the same box so I don't buy the feedback from IBM on this one.