Import spreadsheet error
Locked
-
Friday, April 27, 2007 2:45 PM
Hi:
I'm trying to import a spreadsheet in the Create Option, but when I select the range of cells an then clic on Import I get this error 'Method Post of object IOWSPostData failed'. Does anyone knows how to fix it.
Regards.
- Moved by Mike Walsh FINMicrosoft Community Contributor Sunday, September 18, 2011 5:02 PM admin q (From:SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010))
Answers
-
Monday, July 16, 2007 10:47 PM
Do not copy the Office 2003 files into the Office12 folder.
They are not entirely compatible with the Office 2007 Windows SharePoint Services support files.
Instead, modify the EXPTOOWS.XLA. You could resort to the earlier hard-coding of the version but this would prevent interaction with STS v1 sites.
It appears that the version check was added in order to be more efficient and not try to post the data twice. Unfortunately the function to check the SharePoint version is new to Excel 2007 and fails if earlier versions are used.
Here is the workaround I used to modify the EXPTOOWS.XLA file found in the Office12\1033 folder (for English):
If you are only creating custom lists via spreadsheets on WSS v2 or higher you can search the project for Application.SharePointVersion and change:
lVer = Application.SharePointVersion(URL)
to:
lVer = 2
[this is in the 'Sub Initialize' routine of the publishForm module (Code section)]
==================
If you need a more robust solution you could use the following changes:
Changes to EXPTOOWS.XLA
-----------------------------------
In the publishForm module (Code section) in the section with the other variable declarations:
After
Dim lVer As Long
Insert the additional declaration of:
Dim fUseLegacyCheck As Boolean
Then in the routine 'Sub Initialize' change:
lVer = Application.SharePointVersion(URL)
to:
lVer = -1
If CInt(Application.Version) < 12 Then
fUseLegacyCheck = True 'Application.SharePointVersion not supported
Else
lVer = Application.SharePointVersion(URL)
End If
In the function btnPublish.Click, find and change:
If lVer < 2 Then
to:
If lVer = 1 Or fUseLegacyCheck Then 'STS v1 or .SharePointVersion not supported - 0 means Version check failed
and also change the next occurrence of:
Else
to:
End If
If lVer >= 2 Or fUseLegacyCheck Then 'Newer version found or .SharePointVersion not supported
===========================================================
- Proposed As Answer by Krishaynes Wednesday, May 27, 2009 10:10 AM
- Marked As Answer by Mike Walsh FINMicrosoft Community Contributor Wednesday, May 27, 2009 11:07 AM
All Replies
-
Monday, April 30, 2007 11:12 AM
-
Tuesday, May 15, 2007 7:53 PM
While this works, it causes you to save the VB file as an unsigned file. Does anyone know the real cause and solution? I do not see anything in MSDN where Microsoft has acknoledged or fixed this problem.
Thanks,
Frisky
-
Thursday, May 24, 2007 9:10 PM
I found something very interesting about this. I tried the fix mentioned above and it successfully solved the problem. By the way we are remaining on Office 2003 for now and have discovered this problem affects the publishing of an Excel list the same way if affects the import of a spreadsheet because they seem to depend on the same functions or services.
The odd thing about it is even after I reverted back to the original .xla file I was still able to publish and import. I even rebooted my PC just in case. This was true from other PCs where that fix had never been applied. I could then publish to any site within that web application from any PC. However, I would try to do it against other sites within other web applications (usually on other servers) that I had not yet tried publishing to when the .xla file fix was in place and it would not work.
That tells me something on the server was changed after I fixed that .xla file and published or imported a spreadsheet to a site that somehow fixed the problem for all clients. What that change was I have not been able to determine which is unnerving. I should also note that whatever was fixed appears to have been fixed permanently and not just in memory or something because the server has been rebooted since then and this is still true.
I am still testing this and trying to learn more about it and will post more information if possible.
I wish Microsoft would address this or at least shed some light on the subject. I would submit a support case but doing that lately has been very painful. Unfortunately it seems their ability to fully support the new SharePoint products leaves a lot to be desired at this time.
-
Sunday, June 10, 2007 12:04 PMI am receiving the same error message as stated above! Does anyone know the root of this problem? I receive the same error on both 2003 and 2007 sharepoint portals, using Excel 2003.
-
Tuesday, June 12, 2007 7:30 PM
After changing the VB file as show below, what are the ramifications of saving the EXPTOOWS.XLA as "unsigned"?
<before>
lVer = Application.SharePointVersion(URL)
</before><after change>
lVer = Application.SharePointVersion(URL)
lVer = 2 ' sets this macro to always use soap-method of saving data to sharepoint
</after change> -
Thursday, June 14, 2007 4:31 PM
A similar error (Run-time Error 438 - Object does not support method) is sometimes received when the user is trying to Import Spreadsheet as a Sharepoint list. One of the causes of this problem is when the user has MS Office 2003 installed and at least one component of MS Office 2007 (in my case Sharepoint Designer 2007). Then Sharepoint is trying to access the XLA and DLL files created by SharePoint designer instead of those created by your Excel 2003.
I copied and pasted the files from my Excel 2003 folder to my Office 2007 folder and the problem was resolved for me. This is not the nicest and cleanest fix but it works. Please make your own decision whether you like to use it or not. Here is exactly what I did.
I copied the EXPTOOWS.DLL and EXPTOOWS.XLA files from my C:\Program Files\Microsoft Office\OFFICE11\1033 folder (which belongs to MS Office 2003) and pasted them to my C:\Program Files\Microsoft Office\OFFICE12\1033 folder and overwritten the existing files.
Now I can import XLS spreadsheets without problems.
-
Thursday, June 28, 2007 1:28 PM
After making this change I no longer get the Method 'Post' of object 'IOWSPostData' failed error. Now I generate Cannot connect to the server at this time. Your list cannot be published. What do I need to do to accomplish the simple task of importing a spreadsheet in to a WSS 3.0 list?
XP Pro/WSS 3/Office 2007
-
Tuesday, July 03, 2007 2:34 PM
I got the same error after trying to change to the code then also after copying the files from Office 11...
Why MS has these kinds of problems is beyond me...
-
Monday, July 16, 2007 10:47 PM
Do not copy the Office 2003 files into the Office12 folder.
They are not entirely compatible with the Office 2007 Windows SharePoint Services support files.
Instead, modify the EXPTOOWS.XLA. You could resort to the earlier hard-coding of the version but this would prevent interaction with STS v1 sites.
It appears that the version check was added in order to be more efficient and not try to post the data twice. Unfortunately the function to check the SharePoint version is new to Excel 2007 and fails if earlier versions are used.
Here is the workaround I used to modify the EXPTOOWS.XLA file found in the Office12\1033 folder (for English):
If you are only creating custom lists via spreadsheets on WSS v2 or higher you can search the project for Application.SharePointVersion and change:
lVer = Application.SharePointVersion(URL)
to:
lVer = 2
[this is in the 'Sub Initialize' routine of the publishForm module (Code section)]
==================
If you need a more robust solution you could use the following changes:
Changes to EXPTOOWS.XLA
-----------------------------------
In the publishForm module (Code section) in the section with the other variable declarations:
After
Dim lVer As Long
Insert the additional declaration of:
Dim fUseLegacyCheck As Boolean
Then in the routine 'Sub Initialize' change:
lVer = Application.SharePointVersion(URL)
to:
lVer = -1
If CInt(Application.Version) < 12 Then
fUseLegacyCheck = True 'Application.SharePointVersion not supported
Else
lVer = Application.SharePointVersion(URL)
End If
In the function btnPublish.Click, find and change:
If lVer < 2 Then
to:
If lVer = 1 Or fUseLegacyCheck Then 'STS v1 or .SharePointVersion not supported - 0 means Version check failed
and also change the next occurrence of:
Else
to:
End If
If lVer >= 2 Or fUseLegacyCheck Then 'Newer version found or .SharePointVersion not supported
===========================================================
- Proposed As Answer by Krishaynes Wednesday, May 27, 2009 10:10 AM
- Marked As Answer by Mike Walsh FINMicrosoft Community Contributor Wednesday, May 27, 2009 11:07 AM
-
Tuesday, July 17, 2007 1:46 PM
I still have the same problem:
After making this change I no longer get the Method 'Post' of object 'IOWSPostData' failed error. Now I generate Cannot connect to the server at this time. Your list cannot be published. What do I need to do to accomplish the simple task of importing a spreadsheet in to a WSS 3.0 list?
XP Pro/WSS 3/Office 2007
Update: when importing a spreasheet from a local or network drive the Cannot connect to the server at this time. Your list cannot be published. error is generated. Importing a spreasheet from a sharepoint site works, however. So, I guess I have to upload the spreadsheet to the sharepoint site and then import it. Doesn't make any sense to me, but it works.
-
Tuesday, July 24, 2007 6:52 PMWhat an incredible waste of time for something that should be so simple
-
Wednesday, August 08, 2007 11:45 PMI agree. Typical I microsoft. For such a basic function and it doesn't work! For what its worth, I have this very problem using office 2003, there is no IVER variable in the XLA file mentioned above for office 2003.
-
Friday, August 10, 2007 5:45 AM
Yes thats right and that could be a pain
But at the same time you could be getting the error Cannot connecto to server
because of a security policy issue make sure you ahd your site to a trusted zone and it should be fine.
Hope that help
Patrick
-
Wednesday, December 05, 2007 3:32 PMI had the identical issue, though caused by installing OneNote 2007 onto an Office 2003 Pro configuration. My error was also resolved by copying the EXPTOOWS.DLL and EXPTOOWS.XLA files from OFFICE1/1033 into OFFICE12/1033.
-
Tuesday, February 19, 2008 9:01 PM
I can PUBLISH a list from Excel 2003 into Sharepoint 2007, even though IMPORTING the same list in Sharepoint fails with the 'Method 'Post' failed' error. Changing the Office12 xla file did not appear to work. I have Sharepoint Designer 2007 installed, so I wonder if Sharepoint is looking for Excel 2007, but forcing Excel 2003 to trigger the exchange seems to work.
-
Thursday, May 15, 2008 6:59 PM"Importing a spreasheet from a sharepoint site works, however. So, I guess I have to upload the spreadsheet to the sharepoint site and then import it. Doesn't make any sense to me, but it works."
Ok so I uploaded a document to the document library, but how can i use import spreadsheet to import it? It looks for a local path and doesnt give me the option of goign to the library.
sharepoints such a pain in the *** i sware to god... every function is hidden in a byzantine menu structure and many things are only accessable if you know the "magic" way to access them. Its almost as if m$ designed it to be hard to use
I hate sharepoint!!!!
edit: ok i figured that out, you can just put a url in, but i still get "the selected range cannot be converted to a list before publishing or the exsisting list is invalid"
I thought it might be something wrong with my spreadsheet so i just took 2 cells from it, but still no dice
EDIT 2: I got it! I had to create a table on sharepoint with all my excel collom headers and then edit it in access. From there I was able to import the spreadsheet data into access and then publish to sharepoint. hizah! although thats way to frackign complicated...- Proposed As Answer by Krishaynes Wednesday, May 27, 2009 10:10 AM
- Unproposed As Answer by Mike Walsh FINMicrosoft Community Contributor Wednesday, May 27, 2009 11:07 AM
-
Wednesday, June 18, 2008 9:24 PM
I added the user getting this message to the "Local Intranet", no other changes, and the error went away.
David
- Proposed As Answer by SurendraBabu Friday, November 14, 2008 5:44 AM
- Unproposed As Answer by Mike Walsh FINMicrosoft Community Contributor Friday, February 06, 2009 6:20 AM
-
Tuesday, July 29, 2008 10:35 AMSomething I wish to add...
Ours is a MOSS 2007 implementation with one SQL server and one SharePoint server that accesses the SQL server as its DB provider.
When I tried the fix "lVer =2" or "lVer =3", it gave a different error saying that it could not connect to the server.
I also noted that, before applying this fix, I could import Excel spreadsheets to other site-collections in other web-applications running on the same SharePoint server box.
So whatever is preveinting the import of Excel sheets to this one errant web-application from any PC, is inherent in that web-application itself and not in the SharePoint installation.
The only difference I could probably ascribe to this behaviour of the errant web-application, is that it contains sites that were migrated from WSS2, as opposed to the other web-applications which contain sites that were created newly.
P_S_H -
Monday, November 10, 2008 7:44 PMThis works:
http://rdacollab.blogspot.com/2008/05/importing-excel-spreadsheet-to.html
I tried altering the EXPTOOWS file, as this site and many others suggested...however, although the original IOWS PostData error disappeared, I still got the "Cannot connect to the server at this time..." error. I also installed the MS "hotfix".....which didn't work.
I was using http://servername:port/sites/mysite, so I created a site collection at http://servername:port/ (based on the advice in the link) and it works perfectly now. -
Tuesday, December 02, 2008 5:04 AMHi all,
I have tried all of the above fixes, in addition replacing the Office12 files with Office11 files. However, none of the fixes described have been able to rectify my problem with importing an excel spreadsheet as a new list currently.
This issue has been reported multiple times on one server running HTTPS/SSL, and have caused the following list of errors:
1 - 'Method Post of object IOWSPostData failed'
2 - 'Cannot connect to server at this time. Your table cannot be published'
3 - 'An Unexpected Error has occurred (-2147417851) - Looking up this error revealed that -2147417851 indicates 'The server threw an exception'
These errors are occurring on multiple computers. Error 2 also occurs on some computers straight away, but not error 1.
Our system is running WSS3/MOSS2007 Windows Server 2003 on XP with the latest SP (not sure of version) over HTTPS.
Additionally, creating a site collection at root as per the advice from the previous posts is not possible at this point in time due to restrictions placed on sites which can be created by our team. -
Friday, December 05, 2008 3:54 PMI have tried every solution proposed under the sun for this issue with no result.
I can import at the very top level of the site but if I go down into any sites under that the import fails with the error message.
I have tried all the fixes via the .xla file and still get the Method Post error.
Microsoft needs to fix this. I sent the empty root site fix to the administrator and that did not fix it either. Why do we have to go through all this for a function that we need and should be available?
If you are migrating data from and old SharePoint site or folders this would be a great feature too bad it does not work and is a cause of much frustration within my company.
-
Sunday, December 07, 2008 3:31 PM
Me too... I used the same blog entry as "swissclive" and was giving time to see whether the error will come up again... because this was an error that surfaced suddenly on some clients only... giving us a false idea that it is client dependent...
The cardinal rule as stated by "swissclive" appears to be...
"ALWAYS create a site at the root of a web-application."
...I cannot understand why this type of thing was never stated explicitly by Microsoft. if they had I certainly did not see it...!
What went wrong was that our web application was setup so that ALL our sites were within a location called "sites".
In otherwords, all our sites had URLs that were of the form "http://''SSSS:pppp/sites/...." and there was no site of the form "http://SSSS:ppp/" ("SSSS" is the server-name and "pppp" is the port that was created when the web application was created..)
You need to have the first site collection at the root so that the URL for that site is "http://SSSS:ppp/" and then have all your other sites any way you choose... This "root" site could be a directory site etc. to make more sense...
We did this and ever after that the method post error disappeared...!!! IT HAS BEEN 6 MONTHS NOW AND I GUESS THE ISSUE IS SOLVED ONCE AND FOR ALL, BECAUSE IT DID NOT RECUR IN ANY OF OUR 3000 ODD CLIENTS...!
Thanks for the response and we also thank the guys who put the blog post... http://rdacollab.blogspot.com/2008/05/importing-excel-spreadsheet-to.html
P_S_H -
Wednesday, April 08, 2009 11:29 AMHi!
Did anyone find a "real" solution to this or a statement from Microsoft? This problem occured in WSS 2.0 and was confirmed from MS to be a problem. http://support.microsoft.com/kb/838703
But this article says it's only applicable to version 2.0
Mattias
_______________________________
Mattias Karlsson
http://www.mysharepointofview.com -
Wednesday, May 27, 2009 10:48 AMHi!
We just recently applied SP2 and now I can't reproduce the error. I have not found this exact thing in the release notes of SP2 but it might be something else that solves this problem as well, (or, at least some of it, seems to be different solutions for it). We use Moss and Office 2003.
/Mattias
Mattias Karlsson
http://mysharepointofview.com -
Monday, June 29, 2009 6:45 AM
Hi,
Thought I send an update from our troubleshooting. Before I thought that the problem was solved in SP2, it turned out that after some time we started to get the problem again. We finally found that if you did got directly to one of the WFEs it worked and if you tried the other one it did not worked. This made us suspect the LB which is Cisco thing.
After reading this blog post: http://blogs.msdn.com/vsofficedeveloper/pages/SharePoint-Cisco-CSS-Switch-Issue.aspx we changed the settings on the LB to use Layer 4 instead of Layer 5 and now it works all the time. I have written a summary of our troubleshooting if it could be of interest: http://mysharepointofview.com/2009/06/a-word-about-troubleshooting-the-import-spreedsheet-problem/
/Mattias
Mattias Karlsson
http://mysharepointofview.com -
Monday, July 06, 2009 3:47 PMI am facing the same problem Method 'Post' of object 'IOWSPostdata' failed but there are no files as EXPTOOWS.DLL and EXPTOOWS.XLA under the Office12\1033 but i have them under Office11\1033. I tried copying these files to Office12\1033 but the error still persists. I also tried the patch mentioned above and it gave me that expected version of product is not on the System. I recently upgraded from Office 03 Pro to Office 2007 Ultimate. I also have Sharepoint Designer on the system.
has anyone found a proper solution to this.
thanks in advance- Proposed As Answer by Rahul Gupta - MCITP,MCPD Wednesday, July 29, 2009 8:52 PM
- Unproposed As Answer by Mike Walsh FINMicrosoft Community Contributor Sunday, September 18, 2011 4:00 PM
-
Wednesday, July 29, 2009 8:54 PMHey Guys
I found a very easy work around for this one on my end. When we create a new Sharepoint Site, we have to enable the Enterprise features of that site which enables the excel services on that site and then there are no errors while uploading it. Hope this helps- Proposed As Answer by Rahul Gupta - MCITP,MCPD Wednesday, July 29, 2009 8:54 PM
- Unproposed As Answer by Mike Walsh FINMicrosoft Community Contributor Sunday, September 18, 2011 4:00 PM
-
Friday, January 08, 2010 12:34 PMMy error was also resolved by copying the EXPTOOWS.DLL and EXPTOOWS.XLA files from OFFICE11/1033 into OFFICE12/1033.
Thanks, Abhijit -
Tuesday, May 18, 2010 11:11 AM
I don't have any of these files mentioned in my Office 12 folder (!).. I have only Office 12 installed, but this folder (C:\Program Files\Microsoft Office\Office12) or any of its sub-folders contains any file called EXPTOOWS.
Help anyone?
-
Sunday, September 18, 2011 3:32 PM
I don't know if this will work for others, but I resolved the problem by logging in with a local id.. the same ID that was used to create the site. When it failed, the ID I was using was for a different domain.
I have had no problems creating an SP list by importing a spreadsheet when using an ID that is part of the domain that the SP server belongs to.
-
Sunday, September 18, 2011 4:03 PM
Moderator Note:
This thread has reached 30 posts; it's originally a question from 2007 (!); at least one post is marked as an answer and the thread is now unmanageable.
I'm therefore locking it now.
Anyone with similar problems with the present versions of the software should post a new thread in an appropriate forum.
Moderator
SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
Both also have links to extensive book lists and to (free) on-line chapters
.png){kind=spacer}
