I am running Excel 2007

I am running Excel 2007 and have been working on files and ONLY saving them to my USB memory stick.
On connecting the device to my PC (using an extension USB cord) I noticed a very brief minute blue like spark, and didn'y release until I tried to access my files that the entire content was wiped.
Excel cannot open the file 'LostFile_XLSX_608879.xlsx' because the file format or file extension is not valid. Verify that the file has not been corrupted and that the file extension matches the format of the file.
Well I think it looks fine to me, and I endeavoureed to use the Open & Repair when openng the file too, with no luck.

Well, this problem occurs when excel file gets corrupted or damage. In such case, When you try to open the .xls or .xlsx file, your whole document will not open properly and only characters displayed on the screen. For this, you should take the help of
professional excel recovery tool. The tool is capable to repair corrupt excel file and recover the file in their original format.
Excel Restore Toolbox can help you.
http://www.excel.restoretools.com/

Similar Messages

  • Can I run Excel 2007 in Boot Camp and run XLSM files?

    Since I have found no way to run Excel 2007 files with macros (xlsm format) on a Mac using Excel 2004, 2008 or NeoOffice, does Boot Camp offer support for running Excel 2007 with V.B. Macros? How about in Fusion or Parallels? Anyone know? Any PC switchers out there who have done this?

    I read somewhere that there was a problem with certain incompatibilities in the hardware. I guess the only thing to do is just install everything and test the macros. It'll work or it won't. I'll post the results when I have them. Thanks.

  • Can I run Excel 2007 on a Mac?

    Can anyone tell me if it's possible to run Excel 2007 on a Mac? I have Excel 2008 but I'm preparing for an exam which requires me to use Excel 2007.

    No.
    There is a 2004 and 2008 version for OS X but no 2007 version for Mac.

  • Error running XL Reporter: 'a required COM add-in program..' for Excel 2007

    I have 2 users running Excel 2007 that can't run XL reporter.  They get the message 'a required COM add-in program for XL Reporter has not been loaded'.  I have instructions for Excel 2003, but not for 2007.  Does anyone know how to resolve this for Excel 2007?

    Gordon,
    I have instructions to get the IXXLReporter.dll file in the installation area, but 2007 has completely different layout. I can't find where to go???  Can you please give me the procedure?
    Edited by: Pat Frohlich on Apr 1, 2009 10:12 AM

  • Excel 2007 Formatting Issues When Making PDF

    Running Excel 2007 on XP Pro. When I make a pdf file from an existing Excel file in Excel 2007 (originally created in Excel 2000), a lot of the formatting changes. Cells that were aligned to the center are now aligned to the top or bottom with no rhyme or reason.
    I would hate to have to go through and fix all the alignment problems in Excel 2007.
    Any suggestions or has anybody else had this problem?

    Not so much Excel (or, at least not so much that I remember) but I've read a
    LOT of messages about problems with Word'07
    You might want to check and make sure you have all MS Office updates installed, to fix any known bugs... plus make sure your version of Acrobat is fully up to date
    Acrobat Updates Here - Updates are NOT cumulative, so install in number order
    http://www.adobe.com/support/downloads/product.jsp?product=1&platform=Windows

  • EVDRE - Excel 2003 vs Excel 2007 performance

    We run BPC 7.0 sp6 with a user population that has a mix of Office 2003 & Office 2007 on their client machines.  We have several standard and non-standard evdre reports.  Reports that are run in 2003 take 30 - 60 seconds to expand or refresh, the same reports run in 2007 take 3 - 10 minutes to expand or refresh.
    Also, reports that are run consecutively only with different criteria in 2003 run fine, in 2007 each consecutive run adds 2 - 5 minutes per.
    Does anyone know why? 
    Does anyone know how to fix office 2007 performance issues?
    Any help would be appreciated

    Hi Steven,
    Have you installed System Driver Data Connectivity components on your application server (which is a prerequisite for running Excel 2007)? If not, then get it installed. This you can get from the Microsoft web site. You need to install all of the latest Microsoft Windows hotfixes prior to installing the Administration client. For information about which hotfixes to install, see http://www.microsoft.com/downloads/details.aspx?FamilyID=7554F536-8C28-4598-9B72-EF94E038C891&DisplayLang=en.
    Hope this helps.
    Regards,
    Poonam

  • Excel 2007 and Smartview 11.1 file open slow

    We are in the process of upgrading to HFM system 11.1 and smartview 11.1.1.3 and as part of this process we are starting to use Excel 2007. I am encountering an interesting problem when opening files in Excel 2007 using smartview 11.1 and I am wondering if any one else has seen this problem and found a solution.
    First I converted an excel 2003 file to excel 2007 and saved the file as an xlsx file type. Then I am able to open the file and it would take about 30 seconds to open the file. The file has about 15,000 formulas on for spreadsheets. If I click on each spreadsheet individually and use the "Refersh" button I can save the file in about 10 seconds and then close the file. When I open the file again it will open in 30 seconds. Now using the same file I click "Refresh All" and the file processes fine. I am able to save and close the file in about 10 seconds. However, when I try to open the file again it takes about 20 minutes to open, and then 20 minutes to close.
    This only happens with two or three files. I have another file that is 40 spreadsheets and about 3,000 formulas that is not affected when I click Refresh or Refresh All.
    Any help would be apperciated.
    Rich

    Hi
    On metalink i found some notes about this issure
    "Background
    SmartView communicates over HTTP using .NET. This just means that requests and responses are sent in a standard XML format that is tucked in the HTTP headers. The mechanism is the same as when your internet browser requests a file or submits a form (simplification). A standard Microsoft component that is part of Internet Explorer is used for this.
    There are three components (four if you include the network) in a SmartView refresh:
    -the client
    -the web server
    -the HFM application server
    It is easiest to troubleshoot when they are on separate machines. (Running SmartView on the server to see whether it works better is a useful test to see what effect the network is having, but doesn't show any other bottlenecks.) If you run Task Manager on these 3 machines showing the Performance tab, you will see initial activity on the client as Excel clears the cells and the request is converted into XML. Then you see the web server get busy as it receives and parses the request. Then the application server is busy as it send the data, then the web server is busy as it compiles the results into XML again, and finally the client parses the XML, pushes the data into cells and runs an Excel calculation. This last stage is the longest of all. Overall, it is typical to see the client doing 90-95% of the work, so client performance is a very important factor. Look out for Excel's memory usage increasing and RAM becoming in short supply. Often, user dissatisfaction with refresh times can be alleviated by giving them more RAM or a faster PC.
    The situation we are dealing with here, however, is when the chain of events described above is interrupted. In this case, you will see the client or the web server wait in vain for a response from the next machine in the chain. The case of invalid XML is similar, but the response is truncated so that the XML is not well-formed when it arrives. XML consists of matching pairs of tags and is not well-formed when a closing tag is missing. This can be caused by certain network settings such as packet size (see later). The end result in either case is the same: as Excel cleared the cells before sending the request, cells are left blank or with zeroes.
    Your job now is to work out why the particular component is failing.
    Client
    Check the HTTP time out in the registry:
    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]\
    "ReceiveTimeout"=dword:00dbba00
    "KeepAliveTimeout"=dword:002BF20
    "ServerInfoTimeout"=dword:002BF20
    The time-out limit is five minutes for versions 4.0 and 4.01 and is 60 minutes for versions 5.x and 6. Also, the time-out limit is 30 seconds for Windows Internet Explorer 7. To change the settings, add the above keys. The above values are hexadecimal, not decimal and correspond to 18000 milliseconds (3 minutes) and 240 minutes for the receive time-out. See
    - http://support.microsoft.com/kb/813827
    - http://support.microsoft.com/kb/181050
    Once you make those changes, my recommendation is that you reboot the client machine.
    Web server
    Look for errors in logs showing that the web app didn't respond/disconnected or timed out waiting for another application (i.e. the HFM application server). Eliminate load balancers etc. during testing in order to isolate the problem and to ensure that the user always goes to the same web server otherwise, logs can be hard to interpret. See also the IIS Tuning Guide for IIS settings. We cannot recommend particular settings, as each client must establish the optimal settings for their own environment after performance testing. If necessary, engage the services of a suitably qualified consultant.
    Application Server
    HFM application server performance is very dependent on whether the data is already in RAM or not. One symptom, where the first refresh fails but the second one succeeds, is probably a sign that the cache needed to be populated and once that had been done (by the first refresh) it went faster. HFM loads whole subcubes (Scenario, Year, Value and Entity) into cache, so asking for lots of accounts in the same subcube is fast, but asking for lots of entities will inevitably slow things down as it runs out of RAM and starts unloading subcubes to make room for more. The HFM event log (HsvEventLog.log) shows this happening, but don't forget that the messages you see are a normal consequence of the way HFM works and are not a problem unless you see a hugely elevated number of them during the period the refresh occurs. Another sign would be page file thrashing.
    If there are several servers in a cluster, use sticky sessions in HFM to make sure tests always go the same server, or hit one server directly rather than using the cluster.
    Solutions here involve giving more RAM to the server (probably not possible because of the 2 GB limit) and changing the worksheet design to restrict the number of subcubes accessed. A separate consolidation server, so that reads are not competing with intensive consolidations and calculations, would be a good thing.
    Network
    To find out if packets get fragmented, use
    ping -l size -f
    to send a big packet with the 'don't fragment' flag. E.g.
    Ping -l 1024 -f oracle.com
    If you see a reply like Reply from 141.146.8.66: bytes=1024 time=200ms TTL=245 then the size you specified is below the packet limit of the network. But if you use, for example, 2000 in place of 1024, you get Packet needs to be fragmented but DF set, then you know you have exceeded the limit. Combine this investigation with a Fiddler trace (https://www.fiddler2.com/fiddler2/) to see what size data messages are being sent and received.
    Troubleshooting Guidance
    If you seriously want to go into this in more detail, then it will take a considerable effort on your and your IT Department's part. My general advice would be:
    1. During this process, fix your environment so that it is predictable. Register a single HFM application server and connect to that. Use a single web server and don't go through Apache or any other redirector. Make sure we know which machine to go to for logs. This would be a temporary measure and it doesn't stop the other users using the full, load balanced system so long as it doesn't involve your server.
    2. As far as possible keep other users from using it during testing, unless you are specifically testing for performance under load. We want to see what activity is due to SmartView and not random other jobs.
    3. Use PerfMon on all three machines: client, web server and application server.
    4. Clear Logs before testing and note the times of each test so the logs can be correlated.
    5. Log CPU activity, memory usage, network throughput, page faults, thread count etc. I'm no expert on this so get advice from someone who is.
    6. In addition to the performance logs, from the IIS Server get:
    * HTTP.SYS Error Log - %windir%\System32\LogFiles\HTTPERR (Default location; configurable)
    * IIS Website Log - %windir%\System32\LogFiles\W3SVC# (Default location; configurable)
    * Event Log (both System and Application) in EVT and TXT (tab separated) formats
    7. From HFM Application server get:
    * HsvEventLog.log (in <HFM install>\Server working Folder)
    * Event Log (both System and Application) in EVT and TXT (tab separated) formats
    8. Be aware of all timeout settings in your environment (i.e. IIS & the network) and time your tests. This can show whether it is an ASP timeout, script timeout, client side timeout or whatever. Note that the Web Session Timeout setting for SmartView in HFM's Server and Web Configuration is a separate issue from IIS timeouts. Web Session Timeout controls the length of idle time before SmartView makes the user log in again. Default 20 mins.
    9. Run Fiddler traces to directly observe the XML and check for HTTP failures.
    Further resources
    - Tuning IIS 6.0 for HFM
    - SmartView Performance FAQ
    Both are available from Support.
    Author: Andrew Rowland
    Version: 11.x (Fri, 30 October 2009)"
    regards
    Alexander

  • 32-bit...64-bit...Excel 2007...Excel 2010...nonetheless a .xlsx File

    My head is spinning...soooooo here's the deal...
    The client provides us a .xlsx File. Now I have no idea how this is created and saved...via Excel 2007...Excel 2010
    When I attempt sourcing the .xlsx File in my SSIS Package I get the error "External Table is not in the expected format"
    Sooooo, I figure I'd write a C# Edit Script to read .xlsx File and Save it as a .xls file using the following syntax...
    string StrFileName = (Dts.Variables["User::FileName"].Value.ToString());
    StrFileName = Path.GetFileNameWithoutExtension(StrFileName);
    string StringSourceFile = (Dts.Variables["User::FilePath"].Value.ToString()) + StrFileName + ".xlsx";
    string StringDestinationFile = (Dts.Variables["User::FilePath"].Value.ToString()) + StrFileName + ".xls";
    // This initiates the Excel Application
    Microsoft.Office.Interop.Excel.Application excelApplication = new Microsoft.Office.Interop.Excel.Application();
    // This Opens the Source .xlsx File from Emdeon ePaySmart
    Workbook workbook = excelApplication.Workbooks.Open(StringSourceFile, XlUpdateLinks.xlUpdateLinksNever, true, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing);
    // This will Save the Source .xlsx Emdeon ePaySmart File as a .xls File...note xlFileFormat.xlExcel5
    workbook.SaveAs(StringDestinationFile, XlFileFormat.xlExcel8, Type.Missing, Type.Missing, Type.Missing, Type.Missing, XlSaveAsAccessMode.xlExclusive, Type.Missing, Type.Missing, Type.Missing, Type.Missing, Type.Missing);
    // This will Close the Source
    workbook.Close(false, Type.Missing, Type.Missing);
    // This shuts down the Excel Application
    excelApplication.Quit();
    Note xlFileFormat.xlExcel8
    Now this worked PERFECTLY client side. Then when I created a SQL Server Agent Job it blew up and from what I read the SQL Server Agent Job does not like running dynamic Excel commands.
    Soooooooo now I'm back at the drawing board and figured I'd use OLE DB to source the file.
    I am using this Connection String for the .xlsx File
    string StringConnection = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" + sourceFile + ";Extended Properties=\"Excel 8.0;HDR=Yes;IMEX=1\"";
    Now I understand that the OLEDB.4.0 Connection string is incorrect for a .xlsx File. (Which is why I probably tried to do this with dynamic Excel commands to begin with)
    Now comes the chicken and the egg problem...
    If instead I try using the OLEDB.12.0 Connection String it tells me it isn't installed
    My network, copied Microsoft Office 2010 installed is 32-bit
    So if I try to install the 64-bit Microsoft Access Database Engine 2010 it tells me I have to Uninstall Microsoft Office 2010. Well that is not possible
    So my question is this...How in God's name can I try and process this .xlsx File??? I am at a complete loss here.
    I did come upon this Posting previously...in italics below but it fell short in terms of providing a solution.
    Can anyone please help me out here?
    Thanks in advance for your review and am hopeful for a reply.
    ITBobbyP85
    When I create my connection manager to connect to a .xlsx file, I get the error message that says:
    "Test connection failed because of an error in initializing provider. External table is not in the expected format."
    The provider selected was the ole db "Microsoft office 12.0 Access Database Engine...", and in the All tab I entered "Excel
    12.0" at the top where it says Extended properties.
    Here is the stumper:
    My import package(s) has (have) been running manually for the last 2-3 weeks, but now i've finished an automated system that downloads
    the files from the ftp site, unzips them, validates all the expected files are there, renames and relocates the files to the names/locations expected by my ETL, and then runs the ETL.
    I found out today that the people who manually did this process were each time opening the file and then saving it to the correct location
    in Excel 2007. 
    When I try to run my ETL on the files in the automated process, it fails with the above error. If, however, I just open the file and
    save it (also in 2007), it runs fine. I have been trying to figure out what saving the file is doing to change it to be in the expected format.
    I have tried to use an excel 2003 connection to connect to a copy of the file with a modified extension of .xls and that didn't work.
    (in case it was in another version of excel and someone just changed the ext)
    I then tried to access the file with the OLE DB provider, as above, but instead of entering 12.0 on the Extended properties line, entering
    9.0 or 14.0 in turn (creating new sources/connections each time), and when I do that, both times I get an error that says: 
    “Test connection failed because of an error in initializing provider. Could not find installable ISAM.”
    Am I missing something? Is there something else that simply opening and saving the file might be doing to make it paletable to ssis?
    If we install excel on the db server I realize i could probably open it up and save it as excel 2007 and that would do the trick, but
    the dba is resistant to this idea, so I thought I'd see if anyone has any other ideas?
    If we do have to install excel on that server, does the version have to be excel 2007 in order to programmatically save it as type 2007?
    thanks in advance for your thoughts on the issue...

    You just need to install the latest ACE OLEDB (JET) provider, then when you set the package to run use a proxy with proper rights to access the Excel file on the file system.
    http://www.microsoft.com/en-ca/download/details.aspx?id=13255
    Arthur
    MyBlog
    Twitter

  • Error in Excel 2007.

    We have a user who gets an error when he will start the BPC for Excel in Excel 2007. And he can not open the BPC for Excel. The following error message appears: "In order to open the file Ev4Excel.xla the file had to be repaired or it was forced to remove unredable materials. The workbook has lost its VBA projects, ActiveX controls and all other programming functions." And it can not open the BPC for Excel
    The user also has Excel 2003 installed on his computer and if he uses Excel 2003, it works.
    Is it possible to have both Excel 2003 and Excel 2007 installed on the same computer and run SAP BPC against both
    Are there some Excel add-ins that you have to install when you install the Excel 2007?

    Hi,
    In SAP BPC installation guide you will find below recommendation
    Note: In order for the software to function correctly in Excel 2007, you must
    install the Microsoft.ACE.OLEDB.12.0 provider, which you can get from the
    Microsoft website. The provider must be installed on the Application server.
    This provided in 25mb in size. We installed it on our application server. but still some errors with excel 2007 is not resolved. Finally we tried with office 2003, but still error continued. When we moved back to office 2007, some excel-addins which were available earlier went missing.
    regards,
    Lokesh Nandula

  • Error message when opening a shared workbook with Excel 2007

    Hello,
    We would like to share a workbook outside BW (by saving into a serveur).Since we use Excel 2007, we can't anymore open this workbook.
    We have a message error (see bellow).
    For your information, it was ok with Excel 2003.
    When whe save the workbook in local disk and then copy from local disk
    to a serveur, it's ok.
    We use SAPGUI 7.10 support package 8, patch 1 Revision 1443 & BI 7.0.
    Best regards
    Nicolas Triqnuand

    hey Nicolas,
    first of all, your error message is in French... not too many people out there will be able to understand. Eventhough I do understand French, it doesn't make much sense to me... BUT... in Excel2007 all macro's are by default disabled. When you enable them (you should get a "Security Warning" right under "the Ribbon"), your BI stuff should work again.
    Just gave it a try, and it runs smoothly over here.
    Cheers,
    RafB

  • Error - using MS Excel 2007

    Hi All,
    Very recently I have upgraded my system to MS Excel 2007 from MS Excel 2003. Now when I try to refresh a workbook the system throws an error message saying " Run time error '13' - Type mismatch ". And then gets disconnected from the BW system.
    Please help.
    Thanks & Regards,
    Surjit P

    Hi Surjit,
    Hi,
    See SAP Note 1040856 - Business Explorer 3.X on Windows Vista / Excel
    2007 below:
    The *Business Explorer (SAP BW 3.x)3 programs are not yet released for
    Windows Vista, that means, BEx Query Designer (SAP BW 3.x),*BEx Analyzer
    (SAP BW 3.x), 3BEx Web Application Designer (SAP BW 3.x), *BEx Download
    Scheduler (SAP BW 3.x)* and BEx Browser (SAP BW 3.x) are not released.
    *Likewise, the BEx Analyzer (SAP BW 3.x) for Excel 2007 is not released for
    other versions of Microsoft Windows.
    Other terms
    BEx Analyzer, BEx Query Designer, BEx Web Application Designer, WAD,
    Microsoft Windows Vista, 3.x Frontend, Excel 2007, Office 2007
    Reason and Prerequisites
    We are currently evaluating the usage. Tests have shown that the productive
    use of Business Explorer cannot be supported fully at the moment.
    Due to changes in the Microsoft Windows and Office environment, problems may
    occur when displaying Business Explorer programs (SAP BW 3.x).
    Solution
    Microsoft Vista and Excel 2007 will be supported officially as of the next
    BW 3.5 Frontend patch. These patches should be available by the end of
    September 2007.
    - BW 3.5 for SAP GUI 6.40: Frontend Patch 13 (see Note 1073426)
    - BW 3.5 for SAP GUI 7.10: Frontend Patch 2 (see Note 1006943)
    Known problems:
    - Microsoft Vista and BEx Query Designer: See Notes 1050174, 1039191,
    1013139 and 1050174.
    - Microsoft Excel 2007, Vista and BEx Analyzer: see Notes 1045244,
    1052761 and 1054250.
    - Excel 2007 and BW precalculation servers: You cannot use Microsoft
    Excel 2007.
    Make sure all the criteria given above are accomplished..
    assign points if helpful.
    Thanks and Best Regards
    lasitha

  • Warning message when exporting a Financial Report to Excel 2007

    Excel 2007 users that attempt to export a fully formatted Financial Report into Excel 2007 get the following error message:
    "The file you are trying to open, 'FileName.xls', is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file now?"
    I am still researching the behavior that users get when they click through the message, but would ideally like for the message not to appear without updating the client machine registries. Has anybody else run across this?
    Excel 2007
    BI Plus version: 9.3.1.0.0.248

    It looks like this is a known issue addressed in Bug 7359171 - EXPORT TO EXCEL 2007 CAUSES FILE FORMAT WARNING:
    The current design does not allow you to open HTML content from a web site in Excel unless the extension of the URL is .HTM/.HTML/.MHT/.MHTML. So ASP pages that return HTML and set the MIME type to something like XLS to try to force the HTML to open in Excel instead of the web browser (as expected) will always get the security alert since the content does not match the MIME type. If you use an HTML MIME type, then the web browser will open the content instead of Excel. So there is no good workaround for this case because of the lack of a special MIME type for HTML/MHTML that is Excel specific. You can add your own MIME type if you control both the web server and the client desktops that need access to it but, otherwise the best option is to use a different file format or alert your users of the warning and tell them to select Yes to the dialog.
    Another Workaround :
    Client Configuration of Extension Hardening.
    Client desktops can change the default behavior of the security check using a registry key. The following registry key can be set to alter the behavior ofthe Excel 2007 client in the following ways:
    Key: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\SecurityValue: (DWORD)"ExtensionHardening" = [0 = Disable check; 1 = Enable check and prompt; 2 = Enable check, no prompt deny open]Default setting if value not present is 1 (enable and prompt).
    The client can configure the site to disable the check by setting ExtensionHardening = 0. This will stop the prompt from appearing, but it will also disable any future checks for the file content validity. This does not (in itself) lower your security. The check is part of a defense-in-depth strategy to prevent malicious users from crafting files of a different type than its extension (or MIME type), which could then be used to trick users into opening a file of a type they did not expect. This warning is designed to let the user know of this potential threat and given them an option of canceling the open if they wish.

  • Excel 2007 Window Minimizes while typing

    Hi,
    We have a user with a slightly different type of issue.  The user has 2 monitors, and when Excel is in the second screen, the active window will sometimes, suddenly, become minimized.  We have been able to reproduce this event, and confirmed that
    no keyboard shortcut is being pressed to cause this.  Also, not all windows on the 2nd display minimize - just the active Excel window. 
    Finally, when this happens, the window seems to just disappear, not a "fade to the taskbar" like a normal "minimize" function.  The document is closed, so there is no data loss, but the work-flow is interrupted and is very frustrating
    for this VIP user.
    We are running Office 2007 with Outlook 2010, and all the latest updates and service packs.
    Any help you can suggest would be appreciated.
    Thank you,
    Jeff

    Hi Raju,
    Visit these links:
    1. Microsoft Excel 2007 Query Error
    2. Re: SAP 7.10 to Excel 2007 export problem - blank sheet
    3. Re: ALV export to Excel 2007 w/ SAPGUI 7.1 patch 9 as integer not text
    These links are simillar to your problem. May it solve your problem.
    Regards.
    Deepak Sharma

  • Cannot Save New Document to SP2010 from Excel 2007

    I have two users who cannot save a new file from Excel 2007 to Sharepoint 2010 using the network share path. They receive the following error:
    You cannot save the file you selected. The folder you selected is not an actual file system location. 
    However, other users can save this way with not trouble at all. 
    When they have the Excel file open, they go to Save As... and the window opens. Then they type in the path to the Sharepoint library where they want to save the file: \\intranet\DavWWWRoot\site\library\
    At this point, they should be able to click the Save button and the window will refresh to the Sharepoint library. They would then be able to enter the name of the file and click the Save button again. However, when they click the Save button the first time
    to refresh the window, nothing updates and the path they just typed goes away.
    My first thought was an issue with permissions, but I've checked and double checked that they are in the correct group.
    Then I decided to go even more basic and have them use Windows Explorer to browse to the location. They were able to.
    I then had them right click within Windows Explorer, select New, and click Text Document. Not only were they able to create the new text file, but I confirmed it updated
    the Sharepoint library successfully. So, that obviously rules out any issues with permissions.
    Out of sheer frustration, I even tried mapping a network drive to the Sharepoint library and having them save to the mapped drive location, which of course yielded the exact same error.
    I have also double checked that the Webclient service is running on the machines. 
    One more piece to note is that these two users are still running XP. They'll be upgraded to Win7 later this year, but this needs to work before then.
    Any help or suggestions would be greatly appreciated.

    Hi,
    Did the issue only occur in Excel? What about the other Office suits?
    Please copy the site URL to the File name Text Box in the Save as window. Like:
    http://intranet\site\library
    Regards,
    George Zhao
    TechNet Community Support

  • ALV download to EXCEL -- probs with SAPGUI 6.40 and EXCEL 2007

    I have a method in an ALV grid which performs a dowload to excel
    Here's the method
    method download_to_excel.
    field-symbols:
           <fs0> type standard table,
           <fs1> type standard table.
        assign g_outtab1->* to <fs0>.
        assign g_fldcat1->* to <fs1>.
           call function  'LVC_TRANSFER_TO_KKBLO'
          exporting
            it_fieldcat_lvc   = <fs1>
        is_layout_lvc     = m_cl_variant->ms_layout
             is_tech_complete  = ' '
          importing
            es_layout_kkblo   = ls_layout
            et_fieldcat_kkblo = lt_fieldcat.
        loop at lt_fieldcat into lt_fieldcat_wa.
          clear lt_fieldcat_wa-tech_complete.
          if lt_fieldcat_wa-tabname is initial.
            lt_fieldcat_wa-tabname = '1'.
            modify lt_fieldcat from lt_fieldcat_wa.
          endif.
          l_tabname = lt_fieldcat_wa-tabname.
        endloop.
        call function 'ALV_XXL_CALL'
             exporting
                  i_tabname           = l_tabname
                  is_layout           = ls_layout
                  it_fieldcat         = lt_fieldcat
                  i_title             = sy-title
             tables
                  it_outtab           = <fs0>
             exceptions
                  fatal_error         = 1
                  no_display_possible = 2
                  others              = 3.
        if  sy-subrc <> 0.
          message id sy-msgid type 'S' number sy-msgno
                 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        endif.
    endmethod.
    Basically the method converts the GRID table I'm displaying into the format requred for FMOD ALV_XXL_CALL' -- the field catalog is slightly different but no big deal here.
    This works fine when downloading to  EXCEL 2003 but short dumps when trying to do the same thing for EXCEL 2007.
    Workstation is running Windows XP / SP2 build 2600 in both cases.
    Any fixes etc or should I stick with EXCEL 2003 until forced to upgrade.
    Cheers
    jimbo

    Hi all
    Seems the problem disappeared after applying the latest patch to SAP_GUI 6.40.
    I haven't tried SAP_GUI 7.0 yet.
    Thanks anyway
    Cheers
    jimbo

Maybe you are looking for