Problem with ASP - ODBC - SQL Server after moving to Windows 2003 Server

Hello,
We are setting up a backup server for one of our Web sites, and the current
machine is running Win 2K Server, the new one Win 2003 Server. Otherwise
everything else is the same.
Most everthing works fine, except for one ASP template, which is opening a
recordset with this line:
set RS = Server.CreateObject("ADODB.Recordset") rs.Open "DealerInfo",
Conn,adOpenKeyset,adLockOptimistic,adcmdtable
On the 2003 server it gives an error:
Microsoft OLE DB Provider for ODBC Drivers error '800401f3'
[Microsoft][ODBC SQL Server Driver]Cursor type changed
I have searched for information about thids error, but not found any so far.
Any help would be appreciated.
Ragnar
I have determined that this is not really an error message, but an
informational message. It seems pretty clear that the real error lies
somewhere else, so I will have to come up with a way to add some debug
statements without stopping the code.
Ragnar
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23THcMdmpEHA.2032@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We are setting up a backup server for one of our Web sites, and the
> current machine is running Win 2K Server, the new one Win 2003 Server.
> Otherwise everything else is the same.
> Most everthing works fine, except for one ASP template, which is opening a
> recordset with this line:
> set RS = Server.CreateObject("ADODB.Recordset") rs.Open "DealerInfo",
> Conn,adOpenKeyset,adLockOptimistic,adcmdtable
> On the 2003 server it gives an error:
> Microsoft OLE DB Provider for ODBC Drivers error '800401f3'
> [Microsoft][ODBC SQL Server Driver]Cursor type changed
> I have searched for information about thids error, but not found any so
> far.
> Any help would be appreciated.
> Ragnar
>

Problem when moving index with included columns to another filegroup

Hi,

This may be a GUI bug. When I manually create and then execute a script to move an index with included columns to another filegroup, it works.

When I try to edit the storage property of the index through the GUI, index properties, then when I ask to generate the script for the change to the clipboard, I get an error

Could not add [FirstIncludedColumn] to the collection because it already exist. Microsoft.sqlserver.Smo

it works if the index does not includes addtl columns.

Is that a bug? It really looks it works when done manually.

Thanks, Philippe

Moving this thread to the Tools forum since this is not a TSQL/DDL issue.|||

This sounds like a bug to me. Please file a defect report here: http://lab.msdn.microsoft.com/productfeedback/Default.aspx

If possible, please include the T-SQL to create the index that causes problems. It also helps if you can include really detailed instructions for what you clicked/typed in the index dialog to make the storage change.

Thanks,
Steve