RE: trouble creating list via spread*** import

{\rtf1\ansi\ansicpg936\deff0\deflang1033\deflangfe2052{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}{\f1\fmodern\fprq6\fcharset134 \'cb\'ce\'cc\'e5;}}
\viewkind4\uc1\pard\lang2052\f0\fs20 Hi Jason,
\par
\par Have you got any progress on this issue or does the issue information in my last reply help some? If you still suffer the problem and need some urgent help, I suggest you consider contacting CSS for further troubleshooting.
\par
\par Best regards,
\par
\par Steven Cheng
\par Microsoft MSDN Online Support Lead
\par
\par Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par
\par \pard\li720 --------------------
\par From: stcheng@xxxxxxxxxxxxxxxxxxxx ("Steven Cheng")
\par Organization: Microsoft
\par Date: Wed, 05 Mar 2008 05:04:51 GMT
\par Subject: RE: trouble creating list via spread*** import
\par
\par
\par Hi Jason,
\par
\par Based on the problem symptom, I've looked up some former issues. It seems there are two possible problems you may have run into:
\par
\par ISSUE 1
\par =============
\par Cause:
\par
\par When selecting the fields to import from the excel spread***, if the user only selects the rows a range is specified like $1:$1. This range means that all
\par columns in row one are selected. SPS 2007 has a limit of 1000 columns of a single data type. The range $1:$1 uses the maximum number of columns allowed in excel which is well over the SPS 2007 limit.
\par
\par Resolution:
\par
\par The customer should select the entire range of data to be imported including the rows and columns. This should look like $A$1:$D$3.
\par
\par Additional Information:
\par
\par The maximum number of columns of a single type allowed in SPS 2007 is 1000. This is equivalent to the Excel column lettered ALL. The "An unexpected error has occurred. Your table cannot be published." message can also be logged for several
\par other reasons.
\par
\par For the "Method \lang1033 POST \lang2052 of object \f1\'91\'49\f0 OWSPostData?failed." error message the wrong post method is being used. This has been seen when using basic authentication on the site. If this is the case the following can be done:
\par
\par 1. On the client where the import is being done from modify the exptoows.xla file
\par to set lver = 3. This is a client side workaround.
\par
\par =======================
\par
\par \lang1033 Another issue is somewhat related to the sharepoint site's servername(in url):\lang2052
\par
\par
\par CAUSE:
\par ====
\par Due to the FQDN internet explorer does not trust this URL to accomplish this functionality and we need to add the FQDN to the intranet sites zone for it to work.
\par
\par RESOLUTION/WORKAROUND:
\par ===
\par We\lang1033 'v\lang2052 e seen this problem when the address is an FQDN even though it\f1\'92\'73\f0 internal and adding the site to the Intranet sites in the IE options fixes this problem.
\par
\par We also needed to reboot the client machine after making this change which suggests some sort of caching that was going on in the environment.
\par
\par \lang1033 ===============================\lang2052
\par
\par You can verify the issue based on the above issue description and try to see whether that's the cause of the problem you encountered.
\par
\par Sincerely,
\par
\par Steven Cheng
\par
\par Microsoft MSDN Online Support Lead
\par
\par
\par
\par ==================================================
\par
\par Get notification to my posts through email? Please refer to
\par http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
\par ications.
\par
\par
\par
\par Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
\par where an initial response from the community or a Microsoft Support
\par Engineer within 1 business day is acceptable. Please note that each follow
\par up response may take approximately 2 business days as the support
\par professional working with you may need further investigation to reach the
\par most efficient resolution. The offering is not appropriate for situations
\par that require urgent, real-time or phone-based interactions or complex
\par project analysis and dump analysis issues. Issues of this nature are best
\par handled working with a dedicated Microsoft Support Engineer by contacting
\par Microsoft Customer Support Services (CSS) at
\par http://msdn.microsoft.com/subscriptions/support/default.aspx.
\par
\par ==================================================
\par \tab
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par \pard\li1440 --------------------
\par From: =?Utf-8?B?SmFzb24=?= <Jason@xxxxxxxxxxxxxxxxxxxxxxxxx>
\par References: <9825E030-BF94-459E-9F03-734AB219FD0A@xxxxxxxxxxxxx> <953CFCF1-13B7-40A8-BF54-89769EDED773@xxxxxxxxxxxxx>
\par Subject: RE: trouble creating list via spread*** import
\par Date: Tue, 4 Mar 2008 12:16:06 -0800
\par
\par
\par i have tried different spreadsheets, and as little as 1 colum with 1 row of
\par data.
\par
\par "Ace" wrote:
\par
\par > How much data do you have in your spread***? I suggest that you try a test
\par > import with several rows first.
\par >
\par > "Jason" wrote:
\par >
\par > > When trying to create a new list using Import from Spread*** it is failing
\par > > with
\par > >
\par > > object doesn't support this property or method
\par > >
\par > > and then:
\par > >
\par > > method 'post' of object 'IOWPostData' failed
\par > >
\par > > Using excel 2003, same result on both WSS2.0 and 3
\par > >
\par > > Any suggestions?
\par \pard\li720
\par
\par \pard
\par
\par }