Failed to create microsoft office spreadsheet component

This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? In this article. Archived Forums. Use this forum to discuss topics about deployment for versions of SharePoint prior to Sign in to vote. Is there a prerequisite to import a speadsheet to create a list in SharePoint? Wednesday, December 10, PM. It is now working. They were both visible in the installed options, but I re-installed them anyway.

After restarting my pc, the import functionality started working. Friday, January 16, PM. Hi, Please cite the exact error message to us. Regarding the question about the prerequisites, here is the description from on-line document: To create a list based on a spreadsheet, you must be using a spreadsheet program that is compatible with Microsoft Windows SharePoint Services, Microsoft Internet Explorer, and Microsoft Windows.

Nice weekend! Best Regards, Lionel. Friday, December 12, AM. Here is the Forbidden error. The website declined to show this webpage HTTP Wednesday, December 17, PM. Hi, I noticed you described the exact same problem that I just discovered. This may also make the code easier to read. Use the CreateObject function instead of the New operator when you create an instance of an Office application. You can use the CreateObject function with early-bound objects and with late-bound objects. For example, use the "Excel.

Application" string instead of using the "Excel. The system that fails may have an older version of Microsoft Office or a newer version of Microsoft Office than the version that you specified in the "ProgID" string. Use the Erl command to report the line number of the line of code that does not succeed. This may help you debug applications that cannot run in the IDE. The following code tells you which Automation object cannot be created Microsoft Word or Microsoft Office Excel :.

Early-bound objects require their custom interfaces to be marshaled across process boundaries. If the custom interface cannot be marshaled during CreateObject or during New , you receive the "" error message. A late-bound object uses the IDispatch system-defined interface that does not require a custom proxy to be marshaled.

Use a late-bound object to verify that this procedure works correctly. If the problem occurs only when the object is early-bound, the problem is in the server application.

Typically, you can reinstall the application as described in the "Examine the Automation Server" section of this article to correct the problem. The most common reason for an error to occur when you use CreateObject or New is a problem that affects the server application. Typically, the configuration of the application or the setup of the application causes the problem. To troubleshoot, use following methods:. Verify that the Office application that you want to automate is installed on the local computer.

Make sure that you can run the application. To do this, click Start , click Run , and then try to run the application. If you cannot run the application manually, the application will not work through automation. Click OK. The application runs silently. The application is re-registered as a COM server. If the problem occurs because a registry key is missing, these steps typically correct the problem.

Make sure that the LocalServer32 key points to the correct location for the application. Make sure that the path name is in a short path DOS 8. You do not have to register a server by using a short path name. However, long path names that include embedded spaces may cause problems on some systems.

To examine the path key that is stored for the server, start the Windows Registry Editor, as follows:. Use the following values of the CLSID key to find the key that represents the Office application that you want to automate. Note Short path names may seem correct when they are not correct. This name may not initially appear to be a short path name. To determine whether the path is correct, follow these steps:.

Copy the value from the registry, and then paste the value in the Run dialog box. Verify that the application runs correctly. If the application runs after you click OK , the server is registered correctly. If the application does not run after you click OK , replace the value of the LocalServer32 key with the correct path. Use a short path name if you can.