Smartview 11.1.2 & Excel 2003 SP3-Replace All Error

My client has Smartivew 11.1.2 with Excel 2003 and is doing a private connection to an Essbase cube for ad-hoc analysis. All comes back fine but client does the Excel replace-all functionality and it throws the "Smartview handled an unknown exception thrown by Microsoft Office"....client can hit ok and the replace-all works but not sure why we get the error. This issue is not happening with Excel 2007...anyone see this? Thanks so much!
Edited by: 895068 on Nov 4, 2011 6:28 AM
Edited by: 895068 on Nov 4, 2011 6:28 AM

Hi,
thanks for your answers. From all I could find out from Oracle support, I'll have to wait until 11.1.2.1 is GA and then try again :-(
Or will there be a patch for 11.1.2.0 as well?
Best regards,
Markus

Similar Messages

  • Error when opening XLSX file with Excel 2003 SP3, file does open but in read only mode with temporary name

    I am using Excel 2003 SP3 and have the Office 2007 compatibility pack installed.  When I open Office 2007 formatted Excel files (XSLX) directly in Windows Explorer, I receive the following error if I do not have Excel already opened:
    "Windows cannot find '<path to file>'.  Make sure you typed the name correctly, and then try again.  To search for a file, click the Start button, and then click Search."
    Even though I receive the error, the file does open; however, it opens in Read Only mode with a name such as "Xl0000024.xls".  The number seems to increment up each time it happens.
    Now here is the strange part.  If I have Excel already open and try to open the file in Windows Explorer, the file opens fine in Modify mode with no error and with the correct file name.
    I Googled the error I was getting and found KB211494.  It says I should uncheck the box in Options on the General tab that says "Ignore other applications", but this box is already unchecked in my case.  Any other ideas?  This is
    really frustrating as a small percentage of our company has upgraded to Office 2007 with the rest still on Office 2003.

    This may be a file association problem.  To solve that:
    In Windows 7:
    1. Right-click the file,
    2. Select "Open With" 
    select [Your Program Here]
    3. Check always use this program. 
    In Windows XP:
    1. Locate the file as you have described above
    2. Right click the file
    3. Select Open with from the pop-up menu
    4. Click Choose default program…
    5. Select Excel in the Recommended Programs box
    6. Check Always use the selected program to open this kind of file
    7. Click on OK.
    1.  Make Excel not available from Office 2007 listed under Programs and Features in Control Panel.
    2. Take a registry backup using the steps given here
    3. In the registry editor window expand HKEY_CLASSES_ROOT and navigate to .xls right and delete it.
    4. Exit Registry Editor
    5. Undo Step 1 to make Excel available.
    6.  Restart the computer and verify it the issue is fixed.
    If this answer solves your problem, please check Mark as Answered. If this answer helps, please click the Vote as Helpful button. Cheers, Shane Devenshire

  • Best practice for Smartview when upgrading from Excel 2003 to Excel 2007?

    Does anyone know the best pratice for Smartview when upgrading from Excel 2003 to Excel 2007?
    Current users have Microsoft Excel 2003 with Smartview 9.3.1.2.1.003.
    Computers are being upgraded to Microsoft Excel 2007.
    What is the best pratice for Smartview in this situation?
    1. Do nothing with Smartview and just install Excel 2007.
    2. Install Excel 2007 and then uninstall and reinstall Smartview
    3. Uninstall Smartview, Install Excel 2007, and then install Smartview
    4. Somthing else??
    Thanks!

    We went with option 1 and it worked out fine. Be aware that SV processes noticeably slower in Excel 2007 than 2003. Many users were/are unhappy with the switch. We haven't tested SV v11 yet, so I'm not sure if it has improved performance with Excel 2007 or not (hopefully it does).

  • Crystal 8.5 Export to Excel 2003 Error after Excel SP3 install

    Post Author: tecboy
    CA Forum: Exporting
    Just upgraded Office 2003 to SP3. When exporting a Crystal 8.5 report to Excel 2003..I now receive an error message...file error data may have been lost crystal...i click ok then the Excel spreadsheet opens. all the data appears to be there. I have tried switching between extented and not and also tried switching between application and disk file...same results...SP3 for Office changed something...Just trying to determine what i need to correct to make this error go away...

    Post Author: tecboy
    CA Forum: Exporting
    Yes and no.....I replaced the export dll for Excel with a newer one...the newer dll removed the error message but the layout of the exported crystal reports was screwed up...so i went back to older version. I think it may have something to do with the default speadsheet or tab name that Crystal Reports creates that SP3 for Excel doesnt like...If i recall...i ran into something similar when i was on Crystal 7 and upgrade to Office 2003....

  • Smartview Excel 2003 / 2010

    Hi,
    we have some users who have both excel 2003 and excel 2010 installed on the same p.c. with Smartview.
    Initial install of Smartview works okay, but subsequently I find that Smartview add-in becomes disabled.
    Re-enabling fixes the problem for 2010, but not for 2003 - and even full re-install thereafter does not fix it for me.
    Anyone encounted this / have a fix?
    thanks for any pointers,
    Robert.

    Hi Jasmine,
    I don't think your fix applies to my version of excel.
    i.e. On Excel *2003*
    I can go to Tools\Add-Ins
    Under there I see => Oracle Hyperion Smartview for Office, Fusion Edition
    I can un-tick this option, but there is no 'remove' beyond that.
    If I do so I can then browse, but excel expects either .xla or .xll at this point.
    Correct me if I am misunderstanding!
    regards and thank you,
    Robert.

  • ? Office 2013 to support Excel 2003 (XLS) spreadsheets containing VBA CommandBars references

    Thanks in advance for reading this and offering any wisdom you have! I am not an expert in any of the following, so apologies if off base.
    The basic problem is: I need to use Excel 2013 to support Excel 2003 (XLS) spreadsheets containing VBA 'CommandBars' references which don't seem to work in Excel 2013. Details below.
    Most of our users are still using older desktop windows PCs and Office 2003!  We are beginning to upgrade to laptops running Windows 8.1 with Office 2013.  Of course, we IT technical people are using the new laptops first. These new laptops are
    64 bit.
    Years ago, someone did a lot of development with spreadsheets here in Excel 2003 file formats that automates many activities and routines. Now we with the new laptops are having to support this development using new machines.
    There is a basic compatibility issue that appears when first opening these Excel 2003 files that have VBA code that I'll detail below; I seem able to get by that problem.
    The current problem appears to be that the existing Excel 2003 VBA code has many references to: "For Each bar In Application.CommandBars". As I've learned, the Application.CommandBars VBA functionality is focused on older MS Office versions' menu
    commands, but "...Starting from Office 2007 the Fluent UI is used instead."  In other words, because MS Office isn't menu-driven beginning with version 2007 (uses 'the ribbon'), it appears that these references to: "For Each bar In Application.CommandBars"
    create a basic incompatibility to opening these spreadsheets in Office 2013.
    For a spreadsheet, after I resolve the issue detailed below and save it, when I reopen it I encounter error "Compile error: can't find project or library." 
    For example, the following code snippet:
    Private Sub Workbook_Open()
    For Each bar In Application.CommandBars
            bar.Enabled = False
        Next
    results in: "Compile error: can't find project or library." 
    (Sorry, can't include images yet, I am not a VERIFIED USER of this forum yet.)
    I went into VBE's menu: Tools>References and check for anything marked MISSING, which I deselected. But I am still receiving this error.
    I don't want to get into changing the code a lot to support both Excel 2003 and 2013 (I am no VBA expert, just a dabbler).
    And Microsoft officially says that Office 2003 is incompatible with Windows 8 although Application.CommandBars seem to be somewhat supported in Office 2013 .
    Are you aware of a quick VBA workaround to get by this?
    •I could comment out the validations, commands for: "For Each bar In Application.CommandBars" but then the spreadsheet code probably won't work for users using Office 2003.
    Alternatives would be:
    •Installing Office 2003 on my Win 8.1 64 bit laptop anyway, in spite of MS's saying incompatible, since this thread discusses at least one person has been able to use Office 2003
    •Keeping one older PC with Office 2003 on it for us to support the old Office 2003 code until everyone upgrades their systems
    Thanks
    Basic compatibility issue that seems solvable:
    Opening these spreadsheets displays this error:
    Compile error:
    The code in this project must be updated for use on 64-bit systems.
    Please review and update Declare statements and then mark them with the PtrSafe attribute.
    This seems resolvable by going into the VBA code and just adding element 'PtrSafe' where functions are declared; in other words, replacing VBA code "Declare Function" with "Declare PtrSafe Function" seems to get by this.

    Hi Allan_L,
    Please try the methods that provided above. And this is the forum to discuss questions and feedback for Microsoft Excel, your issue is related to Excel DEV, if you have further question, I recommend you post the question to the MSDN forum for Excel
    http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
    The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • PDFmaker files missing using Excel 2003

    I have a workstation that gets the "PDFmaker files missing" message whenever using acrobat to create a Excel 2003 file PDF.
    Using Office 2003 and Acrobat 8.1.3 on Windows XP SP3
    I have seen may posts on this but have not seen a resolution.  Has this been resolved??  If so what is the solution??
    Yes we can print to a PDF from Excel but the user wanted to just use Acrobat instead of having to load the files in Excel each time.
    Thanks  Jack
    Message was edited by: Jack1376

    Having the same problem here.  Doing a repair install did not fix it.
    Vista 32-bit with 9.4.4 acrobat installed. 
    I have a test machine that is also Vista 32-bit with 9.4.3 and confirmed that it indeed does work.  Going to update that machine and see if I can duplicate the issue.
    Printing to PDF did work tho with 9.4.4.

  • Unable to see the Hyperion tab in Excel 2003

    Hi Hyperion gurus,
    Can anybody shed light on an issue that a user encountered with Smartview? This user installed Smartview and had been using it without any problems. We just started parallel testing and he needed to use Smartview as part of the process. He is now unable to see the add-in in Excel 2003. He has no Hyperion tab and we cannot find any evidence that it has been installed. We reinstalled Smartview but even after reinstalling Smartview he is still unable to see the Hyperion tab in Excel. What is puzzling is that he does have the Hyperion tab in Word and is able to connect.
    Would appreciate any help provided? Thanks.

    I have seen the same exact problem at my company regarding the missing Hyperion tab in Excel (but present in MicroSoft Word). If you go into Excel, then select 'Help', then About MicroSoft Excel, then you'll see 'Disabled Items'. Scan the list for HSAddin.Dll. If this is on the list, highlight it, then select the 'Enable' button. (this is my first suggestion). I've also had to do the following in some isolated cases:
    You should also try re-registering the following 3 SmartView DLL files. To do this, simply locate where these 3 files are stored on your local machine (the file names are):
    HSAddin.dll
    HSSpread.dll
    HyperionSmarttag.dll
    Usually these are stored within the following path: C:\Hyperion\Smartview\bin
    To Register the files:
    Open DOS (start->run->cmd) and change your path to C:\Hyperion\SmartView\bin
    Type in the following, hitting enter key after each line:
    regsvr32 hsaddin.dll
    regsvr32 hsspread.dll
    regsvr32 hyperionsmarttag.dll
    You should receive a 'success message' for each file you register. Reboot your machine following this, and go back to Excel. Your menu should now be in place.
    Thanks,
    James Pryal

  • Return String from Oracle stored proc using Excel 2003 VBA

    Hi to everyone,
    I've got a problem that remains unsolved for many days. I am trying to return a value of an oracle stored procedure using Excel VBA. It might seem trivial, however it's not for someone, who has never done it before...
    OS: Win XP SP3
    Excel 2003
    Ora Client: 11g
    By trying different things I have noticed, that I could have troubles with the ODBC-connection. Maybe I am not using the right one. To store data returned from select statements I have an ODBC-Connection (Driver: Oracle in XE), which works perfectly, e.g.:
    Sub Extract_Data()
    Dim cn As ADODB.Connection
    Dim rs As ADODB.Recordset
    Dim db_name, UserName, Password As String
    cn.Open db_name, USerName, Password
    sql_statement = "SELECT some_text FROM some_table"
    Set rs = cn.Execute(sql_statement)
    rs.MoveFirst 'jump to the first entry in the data list
    Row = 2
    While Not rs.EOF
    'save the data to a worksheet
    ip.Cells(Row, 2) = rs(0).Value
    Row = Row + 1
    rs.MoveNext
    Wend
    End Sub
    Now I need to execute a stored procedure to return a semi-colon delimited string.
    I have tried the following:
    Public Sub obj_class()
    Dim cn As New ADODB.Connection
    Dim strSQL, cn As String
    Dim adoCMD As ADODB.Command
    Dim adoRS As ADODB.Recordset
    Set wb = Excel.ActiveWorkbook
    Set ih = wb.Sheets("InfoSheet")
    cn.Open db_name, UserName, Password
    Set adoCMD = New ADODB.Command
    With adoCMD
    .ActiveConnection = cn
    .CommandText = "S#mdb$stg_da_extr_util.get_all_classes_of_classif"
    .CommandType = adCmdStoredProc
    .Parameters.Refresh
    '------ and here comes the error saying:
    '------ could not find the object in the collection corresponding to the name or ordinal reference requested by the application
    .Parameters("i_caller").Value = "'STG_DATA_REQUEST'"
    .Parameters("i_obj_classif_id").Value = 120
    Set adoRS = .Execute()
    End With
    End Sub
    I did asked on the forum:
    http://www.access-programmers.co.uk/forums/showthread.php?p=1241667#post1241667
    but unfortunately without success.
    Could it be, that my ODBC-connection is wrong? When debugging the connection string, I find the Provider=MSDASQL5.1.
    I have moderate knowledge in VBA, but absolutely a newbie with Oracle DB. Is there any source of information that can help solving this issue? Looking forward to hearing from you, as I am almost giving up... ;(

    My VBA is super rusty. Does that error come after Parameters.Refresh, or after .Parameters("i_caller").Value = "'STG_DATA_REQUEST'"?
    If it's the second one, you'll need the definition of the stored procedure so you can see what parameters it's expecting. That'd mean you're getting something wrong with the names.

  • Excel 2003 Export fails with Diadem 8.10

    We still use Diadem 8.10 on some test stands.  These stands were just loaded
    with the Office 2003 suite.
    Since then, Diadem 8.10 cannot export our data to Excel.  Everything seems
    fine in Diadem.  The export assistance appears to work as always.
    When we try to open the exported file in Excel, we get this error:
    >  "The document is corrupt and cannot be opened.  To try and repair it, use the Open and
    >  Repair command in the Open dialog (File menu) and select Extract Data when prompted.
    Then Excel shows "Extracting Data from Export_Data.xls" in the status bar, with a progress control.
    Eventually, Excel shows this error:
    >  Errors where detected in 'Export_Data.xls,' but Microsoft Office Excel was
    >  able to open the file by making the repairs listed below.  Save the file
    >  to these repairs permanent.
    > 
    >  Damage to the file was so extensive that repairs were not possible. Excel
    >  attempted to recover your formulas and values, but some data may have
    >  been lost or corrupted.
    The result is an Excel file with the correct name, but all cells are empty.
    I have tried reinstalling Diadem 8.10, but the results are the same.  I can install
    Diadem 9.10, and Excel exports are perfect. 
    Unfortunately, the scripts for our application do not work in 9.10, so we must use
    8.10 for a while yet.
    Any ideas to fix the Excel export function for 8.10?

    Hi jbrandim,
    What happens if you take that Excel file created by DIAdem 8.1 and try to open it in an older version of Excel?  Presumably this used to work fine for you prior to Excel 2003.  Does it still?  If it does still work, what happens if you then resave this imported Excel file with the older version of Excel.  Can this new (resaved) Excel file be opened in Excel 2003?
    The new Excel export code that is working correctly for you in DIAdem 9.1 will likely have trouble running in DIAdem 8.1.  You could try replacing the "...DIAdem\AddInfo\gfsexcel.dll" in the DIAdem 8.1 directory with the new file from the DIAdem 9.1 directory, but there are no guarantees.  You should save a backup version of the dll in case it doesn't work.
    Brad Turpin
    DIAdem Product Support Engineer
    National Instruments

  • Error on export to Excel 2003

    Hello, I have Crystal Reports 8 installed on a Windows 2003 Citrix server along with Office 2003 SP3.  Whenever I try to export any report to Excel, I get the following error:
    File error: Data may have been lost
    I found elsewhere that this may be fixed if I install new database and export drivers, however when I looked for them on this site, I could only find them in French and German.  Is there either an English version of that hotfix, or another way to fix this problem?
    Thanks

    Hi,
    If you are using Crystal 8.5 then click [here|http://resources.businessobjects.com/support/additional_downloads/service_packs/crystal_reports_en.asp#CR85] to download service packs.
    Hope this will help!!
    Amit

  • BrioQry dll error in Excel 2003 VBA6.5

    Hi,
    I use Hyperion - Explorer 8.3.2.152 Windows XP, Update Version SP3.
    Under VBA 6.3 the following code runs well in Excel 2003:
    Sub testBrio()
    Dim bqy As BrioQry.Application
    Set bqy = New BrioQry.Application
    MsgBox "works!"
    Set bqy = Nothing
    End Sub
    After updating to VBA 6.5 an error is triggered when creating the application object - error 430: Class does not support automation.
    Does anyone have any idea how to solve this issue?
    Thanks!

    Hello Nicolas,
    Please post this query to the [Legacy Products|SAP BusinessObjects BI Legacy Products;  forum.
    That forum is dedicated to topics related to legacy products such as Business Objects Enterprise 5.x and 6.x.
    The forum is monitored by qualified technicians and you will get a faster response there.
    Also, all Legacy Product queries remain in one place and thus can be easily searched in one place.
    Thanks a lot,
    Falk

  • Printing Excel Instance from InfoView using Excel 2003

    Hi
    I have problem with printing Excel instance within InfoView. We are using Active X as viewer - but when user schedules report in Excel and when it opens that instance - it opens in Web Excel viewer within InfoView. At that point there is no standard menu if user uses Office 2003 or actually Excel 2003 on its own machine so user cannot print instance. Can anybody help with this. If you try to open instance on machine that has Office 2007 there are no problems since instance gets open in full Excel.
    Thanks

    What version of Crystal Reports are you using?  Any service packs or hot fixes installed?
    Can you open other xls files with 2007?  
    Have you ever exported to excel before?
    I export to -excel (97-2003) data only- and open the files with Excel 2007 with no problems. Excel 2007 complains about the old format (xls) and wants to convert it to the new excel format. I alsways ignor it.
    Maybe the 'garbage' you are seeing is because the layout of your crystal report is not working for the export. Is all the data there but you have extra cells and/or lines, or the data is pushed to the left? I find that I must have the fields packed tightly with no space between them and no space above or below the fields, or I get extra cells between and lines above or below them.
    Most of my exports are detail lines with a single line header and columns are set to match the detail line. When exporting multiple lines where the fields do not line up exactly with the ones above them, I may use one or more empty text fields that matches the size of the fields above them to fill the empty space. Sort of like:
    line 1:{field1.}{field2...}{field 3}
    line 2:(text...}{text.....}{field 4)
    And you may need to turn off 'can grow' on all fields as they may cause miss-alignment. All the data will be there when you export it, even what you can not see in Crystal. You will just need to format the cells in Excel to see it.
    Debi  (hi Don)

  • Report Generation Toolkit with Excel 2003 and Excel 2000

    Hello,
    I'm using the Report Generation Toolkit to generate an Excel report from an Excel template.
    The "NI_Excel.lvclass" is included in the "source" section of the application builder options.
    I create an exe file on  a PC where Excel 2003 is installed. On a Notebook, where only Excel 2000 is installed, the application crashes at the generation of the report:
    I guess the problem is the different version of Excel but I don't know. On the developer PC with Excel 2003 it works fine.
    In this document it's only talked about different Word versions.
    How can I use the Report Generation Toolkit here?
    I'm using it that way:
    Regards

    Oh, it seems that the Report Generation Toolkit "only" supports Excel XP/2003/2007.
    I think, that's the problem.

  • I can't transfer data properly to Excel 2003 with the report generation toolkit.

    I have a table with number to transfer into Excel. I use EasyGraph.vi and it works correctly with Excel 2000. But when I try the same program to transfer my data into Excel 2003, the data are not transfered correctly. When I have for example 0,56, it is read as text in Excel and when I have something like 53,300 Excel 2003 read this 53 300 as if there was no coma.
    Do you know what's happening with Excel 2003 ?

    Separators have always been a pain in Excel !
    A work around is to avoid using any separator at all, and to format numbers as power of 10.
    For instance :
    0.12345 -> 12345E-5
    12.345 -> 12345E-3
    The attached vi does the trick.
    Chilly Charly    (aka CC)
             E-List Master - Kudos glutton - Press the yellow button on the left...        
    Attachments:
    NoSeparatorEnumbers.vi ‏20 KB

Maybe you are looking for