User Warning in view.inc on line 1369 after upgrade

I have the same problem after upgrading to 6.x-2.10. Everything done the same as above. MySQL 5.0.81, Drupal 6.16

After enabling views:

* The configuration options have been saved.
* Skipping broken view

and

* warning: Invalid argument supplied for foreach() in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1747.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY vid, position' at line 1 query: SELECT * FROM views_display WHERE vid IN () ORDER BY vid, position in /homepages/17/d277729268/htdocs/drupal_615/sites/all/modules/views/includes/view.inc on line 1369.

Flushing caches doesn't remove this error, but all views (9 of them, coinciding with the # of warnings) appear to be working normally.

Looks like http://drupal.org/node/626834 again.

I think so, too. So i mark this as duplicate of the other issue.

Perhaps post your detailed initial node, to be able to reproduce the problem. I fear this keeps a drupal core bug.

I'm sorry, but what do you mean by "post your detailed initial node"?

I get this when I upgrade to 6.x-2.10:

warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
warning: Invalid argument supplied for foreach() in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1747.
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY vid, position' at line 1 query: SELECT * FROM views_display WHERE vid IN () ORDER BY vid, position in /Users/GraphicDesign/Sites/mysite/sites/all/modules/views/includes/view.inc on line 1369.

Although I GOT a failure message when updating but I didn't save that line ..

Same exact issue is occuring during upgrade from Acquia's version of 6.16 to 6.17. This would be Views 6.x-2.10-acquiadev-1.

Is is right that you disabled and enabled views?

I got this error message after updating Views to 6.x-2.11:

* warning: Invalid argument supplied for foreach() in /home/www/example.com/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /home/www/example.com/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /home/www/example.com/sites/all/modules/views/includes/view.inc on line 1747.
* warning: Invalid argument supplied for foreach() in /home/www/example.com/sites/all/modules/views/includes/view.inc on line 1747.
* user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ORDER BY vid, position' at line 1 query: SELECT * FROM views_display WHERE vid IN () ORDER BY vid, position in /home/www/example.com/sites/all/modules/views/includes/view.inc on line 1369.

UPDATE: The web site seems to work fine. It might not be related, but I also updated CCK and FileField, and I had to re-enable CCK ImageField.

@ressa

That's a known issue with schema api. If you don't disable/enable views during the update this does not happen. If you clear the cache again nothing happens.

I just updated to Views 6.x-2.11 and got these errors and I did not disable Views before the upgrade, but simply took the site off line.

So what is the solution to the problem? Can the errors safely be ignored? After the errors, I cleared all caches and ran update again and there was no error reported. Furthermore my Views appear to display properly.

If the error doesn't keep showing up then you don't need to be worried about it. I haven't found that we can do much about it. Schema API seems to just do things wrong sometimes, and I can't figure out why.

#626834: Disable then enable views displays errors