error '80004005' on .asp

I have the following error on executing a. asp file which uploads a file
into a 2005 SQL DB.
Take note that the SQL server and IIS resides in the same server.
Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not find se
rver
'servername' in sysservers. Execute sp_addlinkedserver to add the server to
sysservers.Hi Monica
You can use SQL Profiler to see the statements you are sending to the server
.
If the server has been renamed check out
http://support.microsoft.com/kb/303774.
John
"Monica" wrote:

> I have the following error on executing a. asp file which uploads a file
> into a 2005 SQL DB.
> Take note that the SQL server and IIS resides in the same server.
> --
> Mcrosoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not find
server
> 'servername' in sysservers. Execute sp_addlinkedserver to add the server t
o
> sysservers.
> --
>
>|||hi John,
Is this also an issue even if the server was renamed even before I created
the DB? BTW, the Db came from a SQL 2000 version that was working fine, but
had this problem when I restored in the 2005 version.
Thanks,
Monica
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...[vbcol=seagreen]
> Hi Monica
> You can use SQL Profiler to see the statements you are sending to the
> server.
> If the server has been renamed check out
> http://support.microsoft.com/kb/303774.
> John
> "Monica" wrote:
>|||Hi Monica
This is a problem with the server and not the database. If you have not
renamed the SQL 2005 Server then you should not have this problem. Checking
@.@.SERVERNAME will show if you have this problem also check out "Hot to:
Rename a Stand-alone Instance of SQL Server 2005" in books online for more
information.
If @.@.SERVERNAME is correct you may have some SQL that is not compatible with
SQL 2005, this can be checked by running SQL Profiler.
John
"Monica" wrote:

> hi John,
> Is this also an issue even if the server was renamed even before I created
> the DB? BTW, the Db came from a SQL 2000 version that was working fine, b
ut
> had this problem when I restored in the 2005 version.
> Thanks,
> Monica
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:FEB13C42-80EC-4218-B5F0-E6B2C0E841BD@.microsoft.com...
>
>|||Hi John,
Now I have this error message,
Microsoft OLE DB Provider for ODBC Drivers error '80040e23'
[Microsoft][ODBC SQL Server Driver][SQL Server]The cursor does n
ot include
the table being modified or the table is not updatable through the cursor.
What does this mean?
Monica
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3C74BC77-EF9F-4063-A26E-2110688DB2A5@.microsoft.com...[vbcol=seagreen]
> Hi Monica
> This is a problem with the server and not the database. If you have not
> renamed the SQL 2005 Server then you should not have this problem.
> Checking
> @.@.SERVERNAME will show if you have this problem also check out "Hot to:
> Rename a Stand-alone Instance of SQL Server 2005" in books online for more
> information.
> If @.@.SERVERNAME is correct you may have some SQL that is not compatible
> with
> SQL 2005, this can be checked by running SQL Profiler.
> John
>
> "Monica" wrote:
>|||Hi Monica
This sounds a bit like http://support.microsoft.com//kb/290413 although it
will not apply to your version, it could be something to do with how you are
forming your SQL statements, can you pinpoint the statement with SQL profile
r?
John
"Monica" wrote:

> Hi John,
> Now I have this error message,
> Microsoft OLE DB Provider for ODBC Drivers error '80040e23'
> [Microsoft][ODBC SQL Server Driver][SQL Server]The cursor does
not include
> the table being modified or the table is not updatable through the cursor.
> What does this mean?
>
> Monica
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3C74BC77-EF9F-4063-A26E-2110688DB2A5@.microsoft.com...
>
>