Skip to Main Content

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Error message: \HsTbar.xla could not be found

user617249Dec 8 2011 — edited Dec 9 2011
Hello All,

We are experiencing an error message when we open excel via citrix. We have smartview and essbase excel addin installed on excel over citrix. When a user tries to open this excel, an error message pops up"

"C:\Hyperion\SmartView\Bin\HsTbar.xla could not be found. Check the spelling of the file name, and verify that the file location is correct. If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved or deleted"

This message comes around 15-20 times and user needs to click OK for 15-20 times and then excel opens normally.

I went through the addins in excel and unchecked hstbar over there. But when we close and open again, we can see that. So I contacted citrix team to see for that addin. But they dont see that listed on the excel over citrix server.

Please advice what would be the reason for this?

Thanks,

Comments

416310
I think the API allows you to specify whether you want standalone="yes" or standalone="no", see [http://java.sun.com/javase/6/docs/api/javax/xml/transform/OutputKeys.html#STANDALONE|http://java.sun.com/javase/6/docs/api/javax/xml/transform/OutputKeys.html#STANDALONE] but I am not aware of a way to ensure that no standalone pseudo attribute is output.
EJP
Is there any way to remove standalone attribute?
Why do you need to do that?
843834
ejp wrote:
Is there any way to remove standalone attribute?
Why do you need to do that?
The XML document I'm editing is part of another application and the other XML documents doesn't have "standalone" attribute in XML declaration.
843834
Martin_Honnen wrote:
I think the API allows you to specify whether you want standalone="yes" or standalone="no", see [http://java.sun.com/javase/6/docs/api/javax/xml/transform/OutputKeys.html#STANDALONE|http://java.sun.com/javase/6/docs/api/javax/xml/transform/OutputKeys.html#STANDALONE] but I am not aware of a way to ensure that no standalone pseudo attribute is output.
Thanks a lot. I read the documentation already. The default output (when not specified in OutputKeys properties) is standalone="no".
DrClap
bogdotro wrote:
ejp wrote:
Is there any way to remove standalone attribute?
Why do you need to do that?
The XML document I'm editing is part of another application and the other XML documents doesn't have "standalone" attribute in XML declaration.
And why is this a problem?
843834
Well, from my point of view this should not be a problem but theese XMLs I am editing are generated by some Tibco application so I do not want to change its XML definition. Anyway ... does anyone knows how to do that? I tried with 1.6 and 1.5 but no positive results.
DrClap
So it's just an aesthetic problem then? You don't actually have to deal with non-compliant parsers which can't handle that output? I don't believe you will find that Tibco specifies that the standalone pseudo-attribute has to be absent... or does it?
jtahlborn
bogdotro wrote:
Martin_Honnen wrote:
I think the API allows you to specify whether you want standalone="yes" or standalone="no", see [http://java.sun.com/javase/6/docs/api/javax/xml/transform/OutputKeys.html#STANDALONE|http://java.sun.com/javase/6/docs/api/javax/xml/transform/OutputKeys.html#STANDALONE] but I am not aware of a way to ensure that no standalone pseudo attribute is output.
Thanks a lot. I read the documentation already. The default output (when not specified in OutputKeys properties) is standalone="no".
so, did you try specifying standalone="yes"?
DrClap
As far as I can see from the XML Recommendation, a document with standalone="no" is equivalent to a document which doesn't have a standalone attribute. So unless you're dealing with a broken parser which can't handle the standalone attribute, it's a waste of time to fuss about the existence of one.
843834
Hi guys, I solved the problem.
There is no need to set in transformer OutputKeys.standalone property. The solution was:
workDocument.setXmlStandalone(true);
before creating the DOMSource.
EJP
Surely you mean 'false'? You said you were trying to remove it.
843834
For sure "true". If you set it "false" you cannot control it to appear or not. So setXmlStandalone(true) on Document. In transformer if you want an output use OutputKeys with whatever "yes" or "no" you need. If you setXmlStandalone(false) on Document your output will be always standalone="no" no matter what you set (if you set) in Transformer.
1 - 12
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jan 6 2012
Added on Dec 8 2011
2 comments
25,973 views