Hi, I got this error message when i want to export to excel from a List. I realise this only happen when we have a lookup column inside the list. This is the error message:- "Cannot get the list schema column property from the sharepoint list." Does anyone have this issue? Can't Excel take the lookup field and translate it to plain text so that we can still on pivoting.

I have having the same exact issue. I'm running WSS v3 + Office 2003 and I'm ready to pull my hair out!

I have found reports of users having the same problem. Our current enviroment:Medium Farm MOSS 2007 Office 2003 We noticed it was when we have a particular date field coloumn in our list. We get the same error message "Cannot get the list schema column property from the sharepoint list". But I myself is running Office 2007 and is not experiencing theany problems. Just find it odd this all started happening this week. Thanks, J

Guys, Imay have a solutionor a workaround. After doing a some DD it turns out that the end users renameda column on the list. I went into thelibrary and verified the view by Settings>>>Documentary Library Settings. Selected the column in question which is named "Impl Date" andnoticed the URL address at the end of theview list shows "http://servername/sitename/_layouts/FldEdit.aspx?List=%7B46D19451%2D1026%2D4672%2D8A56%2DC6BC1707BEA7%7D&Field=Implementation%5Fx0020%5FDate" It's apparent it doesn't match. So is it safe to assume changing the column namemay havecausethis problem?Not sure why would that matter, I'm still trying to investigate it further. But it looks like the column that was in question was one of the columns, they happened to changed. Our quick solution was to create a new column, include it in the view. Then open in datasheet mode and move the data by copy and paste. Once we did that, we were able to export to datasheet. Thanks, J

I was getting the same error as well. Some people in our office get the error while some others do not. We are running SharePoint portal 2007 and trying to export to excel 2003. From Joey's last post I took out all the dates in the view that I was trying to export and found that it would work. I have tried all the other fixes I couldfind: - Making sure sharePoint tools where installed. - I got an error when I tried to register the OWSSUPP.dll file. Has anyone been able to find a fix so that they can download all content types without getting the schema error?

So are people saying that Office 2007 is the fix? I have 6000 users I can't have upgrade. And, we have lots of lists that I'm sure have had columns changed on 2003, then migrated to WSS 2007. The "workaround" of creating a datasheet view, adding a date column and copying sounds just peachy but I don't want to screw up the "modified date" on thousands of rows because we need that. Any REAL solution out there? help!!

Has anyone been able to find a solution to this? We have added date fields from scratch to a new Customised List and not changed the names of existing ones and still get this error exporting toExcel 2003. Thanks

I got the same error after editing a date column's properties from Default value = Today's date to NONE. When I set it back to Today's date, I could again open in Excel. Hope this helps you. Amanda

Thanks. I haven't changed any default date values so can't change back to anything. The problem continued so to get around it I deleted the customised list web part and added a pre-made web part that had most of the columns I wanted and some extra functionality. I then added my extra columns and it all work well now. I think the problem relates to customising only some web parts for some reason.

There is no solution anywhere. Can someone from Microsoft please reply to this post and address this issue which is causing me lots of problems. Date fields in lists cannot be exported from MOSS 2007 to Excel 2003.... WHY? Is there a workaround and please don't tell me it's just another bug to try and get people upgrading to Office 07

Eggheadcafe has a solution here: http://www.eggheadcafe.com/software/aspnet/30031255/cannot-get-the-list-schem.aspx It basically says to change the data type in your date columns to single line of text, then to change it back to date. This will prompt that data loss could occur, just ignore this (save list as a template if you don't believe me). If you do this with all date columns that are in your view it should work. I had no columns where the names were changed (IE didn't match the URL) and I was still getting this error. It would occur on Excel 2003 but not 2007. I didn't need to create a separate date column and copy/paste values over. Now, my questions is has anyone figured out what causes this to happen? There seems to be data validation for when dates are being entered, so how does the error occur? And more importantly how can we prevent it?

Although the above worked for some users, I have some others who refuse to risk their data as their date fields are essential. I am wondering if MS has brought out a patch or alternative fix that doesn't mess with the data. Is anyone in the know of such a fix/alternative?

Hi: I think Joey Arreza is the winner. Bottom line is that changing the name of the date fields prevents you from exporting to Excel. Don't change the date field names after they're created. http://epes.wordpress.com/2008/02/09/sharepoint-cannot-get-the-list-schema-column-property-from-the-sharepoint-list/ Hope it works. Charlie

eggheadcafe's solutionworked for me. I have MOSS 2007 and Excel 2003. I havea custom list with assorted fields including a number of dates. I pinned down the export error to the date fields only. List was newly created with no edits to field names or other such accidental problem-generators. Pre-eggheadcafe - got the error every time for any view containing a date field. Changed all date fields to single line of text, then back to date, and refreshed the view. Bob's my uncle, job done, cha-ching, and various other expressions of delight. Loss of data wasn't an issue for me as I'm building the tools at the same time as trying to build a useful business function, so I actually didn't have any data to lose at the time. Just upset I tried "experimenting" for so long last night instead of looking for a problem resolution on here...

There seems to be a post-SP1 hotfix for this now: http://support.microsoft.com/kb/941422

I have installed, but still have the issue..

We've just installed SP1 too and we still have this list schema issue on many of our lists

I, too, have installed SP1 and I'm still having this issue. Yet another SharePoint hotfix that doesn't actually fix the problem...

The option to rename all date fields to single text fields and then back to date fields resolves the issue irrespective of the version of Excel.Try it, it works.- Johan- Johan

How can you change the list column type and back and forth across over a thousand workspaces? Is there a utility or programmatic way to do this? Alex Angas - http://www.alexangas.com/blog

Modifying the date fields to single text seems to fix the synchronization issue;However, now Excel will not allow me to modify the list. I receive the error message, "The column is a read only column that cannot be modified." Any suggestions?On a side note, this list was working 2 weeks ago (also working for 5 months prior)and all of the sudden stopped working. I verified my Window's updates and I am up-to-date. I tried unistalling the Excel updates that took place in the last 2 weeks and the problem still exists. I re-installed the updates and I am back at square one. =0\Please help!

Using the object model you could:1. Iterate through all lists, choosing which ones are affected2. Iterate through the affected lists, and their SPField's , holding onto appropriate info for those which were date types.3. Extract the current data from the SPField, so you can restore it later, mapping it locally somewhere4. Remove all of the SPFields from their parent list.5. Iterate through your stored set, and recreate an SPField of text type, and re-set its data from your local storage.If you need help writing this, send me an email... cosier aat gmailMMatthew Cosier

Thank you for your help MatthewI ended up restoring my computer to 2 weeks ago and everything is working again! : )

Looks like this thread may have died awhile ago, but I am struggling to fix this issue. I've got a date ONLY field that was renamed in the past. MOSS 2007 with SP1 and I've applied this post-SP1 hotfix:http://support.microsoft.com/kb/941422/en-usUsers on Office 2003 received the standard 'Cannot get the list schema column property from the Sharepoint list' error message on export to Excel. I have tried:1) Applying the update identified to fix this issue in KB 9414222) Creating a new/differentdate ONLY column and scrapping the original3) Changing the original date ONLY field to single, then back to date ONLYAnd while I am able to export just fine to Office 2007, I have 600 users. It isn't feasible for me to upgrade all of them to Office 2007. Any advise you might be able to provide would be greatly appreciated. Thanks!

Jason, I think the only solution is Matthew's suggestion earlier. Unfortunately this hasn't been high enough priority for my company to fix so I have no code for you, but Matthew might be able to help. Regards, Alex. Alex Angas - http://www.alexangas.com/blog

I had the same issue with WSS3.0 + excel2003. I have change the default value of datetime fileds to today's date instead of none . It works well after that.Li

We've been seeing this problem for months too. I haven't tried the MS hotfix that has come out.But I do have a work around that has worked for my users.The problem seems to be with regional settings. My servers are in the US and the default regional settings are English (United States). All the users that reported problems were UK based. So, using the My Settings/Regional Settings from the users homepage we tried changing the users settings to English (United Kingdom).Since then all users have been able to export the columns without problems. I guess the problem is Excel (when on a UK locale PC) doesn't accept the dates in US formar (mm/dd/yy) so cannot read the data from SharePoint.I hope this helps.Simon

It seems that OfficeSP2 introduce a similar Issue but with Lookup field (including Users lookup fields). After upgrading to Office SP2 Im not able to refresh previously created Excel file with SP Link (both XP / Vista) while still working fine with a office SP1?????If I remove the lookup Col from the view the Sunc is working???Does anyone else seens this?Herve

Exasperating, isn't it? I've been dealing with this problem for several days. Never found a repair. The work-around is to export to Access and then export the Access table to Excel.

Running Office 2007 with SP1 seem's to work fine, when we are using Office 2007 SP2 machines we are seeing this error. Have spent the last 2 months working on a solution but no joy (Problems with individual columns consisting of Lookups, Dates, Calculated Values), we have taken the decision not to role out SP2 for Office, and to role back any SP2 machine to SP1 using the following Microsoft Tool http://www.microsoft.com/downloads/details.aspx?FamilyId=b97e6ecf-8da5-455d-b3bb-8ff2223f97c4&displaylang=en

Running Office 2007 with SP1 seem's to work fine, when we are using Office 2007 SP2 machines we are seeing this error. Have spent the last 2 months working on a solution but no joy (Problems with individual columns consisting of Lookups, Dates, Calculated Values), we have taken the decision not to role out SP2 for Office, and to role back any SP2 machine to SP1 using the following Microsoft Tool http://www.microsoft.com/downloads/details.aspx?FamilyId=b97e6ecf-8da5-455d-b3bb-8ff2223f97c4&displaylang=en I've tried this out (along with all of the date default value changes suggested by others) and have had no success. I still get the error after removing SP2. I have narrowed the issue to a specific lookup column (other lookups work fine) but have not come to a conclusion of what specifically is causing the problem.

Super easy fix for this, just change the column type to plain text then back to date.

Hi,I have done some debugging of this issue by using a man in the middle proxy. It doesn´t seems to be a web services issue as all SOAP Query got valid answers. I have even compared the returned XML with anther list with lookup that is not having the issue and I don´t see any problem so far… All seems to be pointing at an Excel Bug on the way it is processing the XML. Sorry but I didn´t went so far as debugging Excel assemblies… So the question is: “Can we have someone at Microsoft to look into this? I will be happy to forward those XMLs to someone that can inject it to Excel and track down the bug?” Best Regards Herve

In my case, it is caused by a column that is renamed after the view is created. So to test which column causes the problem, just try to remove columns from the view one by one until the issue is gone. When you identify the problem column, add back all the columns including the problem one, the view should start to work.

Tried all the solutions above and still didn't work. I'll try the hotfix even though this should probably be included in sp2? The strangest thing is occuring - we discovered when we have more than 4 items to export, then the error occurs. With 4 or less items, the export to excel works ?!? Using MOSS 2007 / Office 2007Read more about SharePoint...

hwg_Maarten Please don't propose your own posts. Propose the good posts of other people as that is helpful for the Moderators but not your own posts. (Moderator)FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com Complete Book Lists (incl. foreign language) on each site.

The LookUp column can cause this problem too. After removing a lookup column from the view, the export starts to work.

Exactly - Lookup. If your lookup coulumn is reading from calculated column the issue occurs. If you change lookup column to read from a single-line-of-text field, the goes away (at least it did for me). Either changing DateTime to text and back or fix the lookup. You can strategically determine which is the problematic column by removing all but title from a view and then adding one-by one to the view and trying to export to spreadsheet. Once the erroro occurs, you'll know which is the troublesome column. From there you can see which type of column is it and research more. Read more about SharePoint...

Boris, there are no exceptions in this.Please do not propose your own posts as answers as it does not help the Moderators.Propose the good answers of other people and wait for someone else to propose your posts.(Moderator)FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com Complete Book Lists (incl. foreign language) on each site.

Mike, I apologize for proposing as answer. I didn't mean to propose as an answer but to edit the post as you can probably see the created and edit time as moderator. Since buttons are closely together, I misclicked and there is no "unpropose as answer". Edited again: If this is so strictly forbidden why does the system allow authors to propose their posts as answers?

Boris, there are no exceptions in this.Please do not propose your own posts as answers as it does not help the Moderators.Propose the good answers of other people and wait for someone else to propose your posts.(Moderator) FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com Complete Book Lists (incl. foreign language) on each site. hi , ahem , i dont want to hijack this thread into a new topic , but many mod's , especially those new indian ones flag whatever they post as the answer , some other mods do it also , thus settings a bad example for everyone , .... (!!) this case proves again there should be for the posters a ' unpropose ' if you have ' proposed ' something , .... have a nice dayScan with OneCare + 50 Windows 7even Tips + Plagued by the Privacy Center? REMOVE IT + Threat Research & Response Blog + Sysinternals Live tools + TRANSLATOR+ Photosynth + Microsoft Security + Microsoft SUPPORT + PIVOT from Live Labs + Microsoft Live Labs + Office 2010 beta + Get Windows LIVE!

Exactly - Lookup. If your lookup coulumn is reading from calculated column the issue occurs. If you change lookup column to read from a single-line-of-text field, the goes away (at least it did for me). Either changing DateTime to text and back or fix the lookup. You can strategically determine which is the problematic column by removing all but title from a view and then adding one-by one to the view and trying to export to spreadsheet. Once the erroro occurs, you'll know which is the troublesome column. From there you can see which type of column is it and research more. Read more about SharePoint ... We had the same issue! Changing the lookup-column to a non-calculating field fixed the problem!

That cannot be the answer. I have other libraries that have lookup lists that we export to excel regularly and they work fine!

Hi Herve, Yes this seems to be my Issue as well, after going on a bit of a wild goose chase with date fields it appears that the look up field was causing the issue. I created a new column, transferred the data, added it to all my views and deleted the old column and it works fine

Changing the default value for one (of 4) column with "Date and Time" to "today" worked fine for me. Still, this is a very irritating bug.

I'm locking the thread. It has now 44 replies and is unwieldy. It also contains several suggested answers. Anyone with a similar question that is not answered here should start a new thread. Moderator pre-2010 forumsSP 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