Monday, March 19, 2012
Could not Re-index !
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?
Sometimes autogrow doesn't grow fast enough. The only way I know to handle this is to pre-allocate storage.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message news:c97flr$rtl1@.imsp212.netvigator.com...
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following error
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because I
> could execute the same command successfully on another machine that has even
> less free hard disk space.
> Can anybodies help me ?
>
>
>
Could not Re-index !
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?
Have you checked the settings of you data / log files to see if they have
reached there max size ?
J
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c9c7sj$j5r1618@.imsp212.netvigator.com...
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following
error
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because
I
> could execute the same command successfully on another machine that has
even
> less free hard disk space.
> Can anybodies help me ?
>
Could not Re-index !
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?Sometimes autogrow doesn't grow fast enough. The only way I know to handle t
his is to pre-allocate storage.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"cpchan" <cpchaney@.netvigator.com> wrote in message news:c97flr$rtl1@.imsp212.netvigator.com.
.
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following err
or
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because
I
> could execute the same command successfully on another machine that has ev
en
> less free hard disk space.
> Can anybodies help me ?
>
>
>
Could not Re-index !
Service Pack 3.
But I could not do DBCC DBREINDEX on one of them and got the following error
:
DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
The error was :
Server: Msg 1105, Level 17, State 2, Line 1
Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
because the
'PRIMARY' filegroup is full.
Index (ID = 1) is being rebuilt.
Index (ID = 3) is being rebuilt.
Index (ID = 4) is being rebuilt.
But I don't think the error came from insufficient hard disk space because I
could execute the same command successfully on another machine that has even
less free hard disk space.
Can anybodies help me ?Have you checked the settings of you data / log files to see if they have
reached there max size ?
J
"cpchan" <cpchaney@.netvigator.com> wrote in message
news:c9c7sj$j5r1618@.imsp212.netvigator.com...
> My company has 5 SQL Servers, their configurations are : SQL Server 7.0 +
> Service Pack 3.
> But I could not do DBCC DBREINDEX on one of them and got the following
error
> :
> DBCC DBREINDEX('dbo.SA_TRN_DTL', ' ', 0)
> The error was :
> Server: Msg 1105, Level 17, State 2, Line 1
> Could not allocate space for object 'SA_TRN_DTL' in database 'rmsdb_prd'
> because the
> 'PRIMARY' filegroup is full.
> Index (ID = 1) is being rebuilt.
> Index (ID = 3) is being rebuilt.
> Index (ID = 4) is being rebuilt.
> But I don't think the error came from insufficient hard disk space because
I
> could execute the same command successfully on another machine that has
even
> less free hard disk space.
> Can anybodies help me ?
>
Thursday, March 8, 2012
Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'
I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :
Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.
Thank you.
please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.
Thanks,
Peter
|||I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.
Hope this helps,
Ries Vriend
http://www.amsterdamsoftware.com
|||I am not backing up any of the system databases and still getting this error.|||
I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.
The backup is running and I'm seeing the backup files, but the errors are troubling.
I'm running 32 bit SP1. SQL Server 9.0.2047
|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...
select value, value_in_use from sys.configurations where name = 'Agent XPs'
|||yeah it is enabled. Still then Im getting the error.|||I am also having a problem with this:
2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.
The againt will not even start.
Anyone have any luck with this please let me know.
Thanks
Stacey
|||We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208
This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
So, when will SP2 or a hotfix be released? It would be nice to have database mail working.
Thanks.
|||SQL 2005 Service Pack 2 CTP fixed this on my server.
http://www.microsoft.com/sql/ctp.mspx#E2
|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"
the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.
Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'
I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :
Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.
Thank you.
please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.
Thanks,
Peter
|||I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.
Hope this helps,
Ries Vriend
http://www.amsterdamsoftware.com
|||I am not backing up any of the system databases and still getting this error.|||
I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.
The backup is running and I'm seeing the backup files, but the errors are troubling.
I'm running 32 bit SP1. SQL Server 9.0.2047
|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...
select value, value_in_use from sys.configurations where name = 'Agent XPs'
|||yeah it is enabled. Still then Im getting the error.|||I am also having a problem with this:
2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.
The againt will not even start.
Anyone have any luck with this please let me know.
Thanks
Stacey
|||We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208
This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
So, when will SP2 or a hotfix be released? It would be nice to have database mail working.
Thanks.
|||SQL 2005 Service Pack 2 CTP fixed this on my server.
http://www.microsoft.com/sql/ctp.mspx#E2
|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"
the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.
Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'
I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :
Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.
Thank you.
please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.
Thanks,
Peter
|||I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.
Hope this helps,
Ries Vriend
http://www.amsterdamsoftware.com
|||I am not backing up any of the system databases and still getting this error.|||
I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.
The backup is running and I'm seeing the backup files, but the errors are troubling.
I'm running 32 bit SP1. SQL Server 9.0.2047
|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...
select value, value_in_use from sys.configurations where name = 'Agent XPs'
|||yeah it is enabled. Still then Im getting the error.|||I am also having a problem with this:
2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.
The againt will not even start.
Anyone have any luck with this please let me know.
Thanks
Stacey
|||We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208
This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
So, when will SP2 or a hotfix be released? It would be nice to have database mail working.
Thanks.
|||SQL 2005 Service Pack 2 CTP fixed this on my server.
http://www.microsoft.com/sql/ctp.mspx#E2
|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"
the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.
Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'
I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :
Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.
Thank you.
please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.
Thanks,
Peter
|||I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.
Hope this helps,
Ries Vriend
http://www.amsterdamsoftware.com
|||I am not backing up any of the system databases and still getting this error.|||
I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.
The backup is running and I'm seeing the backup files, but the errors are troubling.
I'm running 32 bit SP1. SQL Server 9.0.2047
|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...
select value, value_in_use from sys.configurations where name = 'Agent XPs'
|||yeah it is enabled. Still then Im getting the error.|||I am also having a problem with this:
2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.
The againt will not even start.
Anyone have any luck with this please let me know.
Thanks
Stacey
|||We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208
This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
So, when will SP2 or a hotfix be released? It would be nice to have database mail working.
Thanks.
|||SQL 2005 Service Pack 2 CTP fixed this on my server.
http://www.microsoft.com/sql/ctp.mspx#E2
|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"
the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.
Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'
I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :
Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.
Thank you.
please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.
Thanks,
Peter
|||I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.
Hope this helps,
Ries Vriend
http://www.amsterdamsoftware.com
|||I am not backing up any of the system databases and still getting this error.|||
I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.
The backup is running and I'm seeing the backup files, but the errors are troubling.
I'm running 32 bit SP1. SQL Server 9.0.2047
|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...
select value, value_in_use from sys.configurations where name = 'Agent XPs'
|||yeah it is enabled. Still then Im getting the error.|||I am also having a problem with this:
2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.
The againt will not even start.
Anyone have any luck with this please let me know.
Thanks
Stacey
|||We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208
This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
So, when will SP2 or a hotfix be released? It would be nice to have database mail working.
Thanks.
|||SQL 2005 Service Pack 2 CTP fixed this on my server.
http://www.microsoft.com/sql/ctp.mspx#E2
|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"
the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.
Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'
I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :
Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.
Thank you.
please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.
Thanks,
Peter
|||I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.
Hope this helps,
Ries Vriend
http://www.amsterdamsoftware.com
|||I am not backing up any of the system databases and still getting this error.|||
I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.
The backup is running and I'm seeing the backup files, but the errors are troubling.
I'm running 32 bit SP1. SQL Server 9.0.2047
|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...
select value, value_in_use from sys.configurations where name = 'Agent XPs'
|||yeah it is enabled. Still then Im getting the error.|||I am also having a problem with this:
2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.
The againt will not even start.
Anyone have any luck with this please let me know.
Thanks
Stacey
|||We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208
This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
So, when will SP2 or a hotfix be released? It would be nice to have database mail working.
Thanks.
|||SQL 2005 Service Pack 2 CTP fixed this on my server.
http://www.microsoft.com/sql/ctp.mspx#E2
|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"
the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.
Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'
I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :
Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.
Thank you.
please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.
Thanks,
Peter
|||I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.
Hope this helps,
Ries Vriend
http://www.amsterdamsoftware.com
|||I am not backing up any of the system databases and still getting this error.|||
I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.
The backup is running and I'm seeing the backup files, but the errors are troubling.
I'm running 32 bit SP1. SQL Server 9.0.2047
|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...
select value, value_in_use from sys.configurations where name = 'Agent XPs'
|||yeah it is enabled. Still then Im getting the error.|||I am also having a problem with this:
2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.
The againt will not even start.
Anyone have any luck with this please let me know.
Thanks
Stacey
|||We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208
This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
So, when will SP2 or a hotfix be released? It would be nice to have database mail working.
Thanks.
|||SQL 2005 Service Pack 2 CTP fixed this on my server.
http://www.microsoft.com/sql/ctp.mspx#E2
|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"
the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.
Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'
I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :
Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.
Thank you.
please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.
Thanks,
Peter
|||I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.
Hope this helps,
Ries Vriend
http://www.amsterdamsoftware.com
|||I am not backing up any of the system databases and still getting this error.|||
I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.
The backup is running and I'm seeing the backup files, but the errors are troubling.
I'm running 32 bit SP1. SQL Server 9.0.2047
|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...
select value, value_in_use from sys.configurations where name = 'Agent XPs'
|||yeah it is enabled. Still then Im getting the error.|||I am also having a problem with this:
2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.
The againt will not even start.
Anyone have any luck with this please let me know.
Thanks
Stacey
|||We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208
This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
So, when will SP2 or a hotfix be released? It would be nice to have database mail working.
Thanks.
|||SQL 2005 Service Pack 2 CTP fixed this on my server.
http://www.microsoft.com/sql/ctp.mspx#E2
|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"
the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.
Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'
I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :
Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.
Thank you.
please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.
Thanks,
Peter
|||I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.
Hope this helps,
Ries Vriend
http://www.amsterdamsoftware.com
|||I am not backing up any of the system databases and still getting this error.|||
I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.
The backup is running and I'm seeing the backup files, but the errors are troubling.
I'm running 32 bit SP1. SQL Server 9.0.2047
|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...
select value, value_in_use from sys.configurations where name = 'Agent XPs'
|||yeah it is enabled. Still then Im getting the error.|||I am also having a problem with this:
2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.
The againt will not even start.
Anyone have any luck with this please let me know.
Thanks
Stacey
|||We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208
This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/
So, when will SP2 or a hotfix be released? It would be nice to have database mail working.
Thanks.
|||SQL 2005 Service Pack 2 CTP fixed this on my server.
http://www.microsoft.com/sql/ctp.mspx#E2
|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"
the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.
Wednesday, March 7, 2012
Could not fetch a row 'VFPOLEDB'
I set up a linked server connecting to a FoxPro database using the vfpoledb
provider.
On my development machine I can get this linked server to work, but on my
test machine, without a full SQL version, I get the error "Could not fetch a
row...". Does anyone have any ideas on how to fix this? I have tried
reinstalling the vfpoledb.exe but that didn't help it.
--
Evan HennisHi
I am not a VFP expert, but you may want to check that the locations for the
VFP database are correct and that MDAC versions are up-to-date and
consistent, and VFP is patched to the same level.
You may also want to see if your permissions on these machines varies.
If this is working on one machine and not the other implies the mechanism is
correct, although if the data is different it could be a factor.
The are plenty of posts concerning this error and VFP
http://tinyurl.com/94xhx and replies suggest that you check primary keys,
read http://support.microsoft.com/default.aspx?scid=kb;en-us;207595 ...
John
"EvanHennis" wrote:
> I am running an MSDE of SQL Server 2000 with the latest server pack.
> I set up a linked server connecting to a FoxPro database using the vfpoledb
> provider.
> On my development machine I can get this linked server to work, but on my
> test machine, without a full SQL version, I get the error "Could not fetch a
> row...". Does anyone have any ideas on how to fix this? I have tried
> reinstalling the vfpoledb.exe but that didn't help it.
> --
> Evan Hennis|||The actual error is:
"Could not fetch a row from OLE DB provider 'VFPOLEDB'
I am trying to connect to a local FoxPro database. Is there some security on
the local computer I need to set?
--
Evan Hennis|||Hi
Being able to connecting to the database probably rules out permissions at a
OS level. It is not clear if this is a networked database or separate ones,
if the latter check for differences in the databases. If not it is most
likely environmental e.g. MDAC.
John
"EvanHennis" wrote:
> The actual error is:
> "Could not fetch a row from OLE DB provider 'VFPOLEDB'
> I am trying to connect to a local FoxPro database. Is there some security on
> the local computer I need to set?
> --
> Evan Hennis
>|||On the test machine I am running Win2000 and I installed the MDAC 2.8. On the
development maching I am in XP Pro. Which I beleive has MDAC 2.8 built in. Is
there a way that I can compare the permissions and such on the MDAC?
--
Evan Hennis
"John Bell" wrote:
> Hi
> Being able to connecting to the database probably rules out permissions at a
> OS level. It is not clear if this is a networked database or separate ones,
> if the latter check for differences in the databases. If not it is most
> likely environmental e.g. MDAC.
> John
>
> "EvanHennis" wrote:
> > The actual error is:
> > "Could not fetch a row from OLE DB provider 'VFPOLEDB'
> >
> > I am trying to connect to a local FoxPro database. Is there some security on
> > the local computer I need to set?
> > --
> > Evan Hennis
> >
> >|||Hi
Download the the MDAC component checker
http://msdn.microsoft.com/data/mdac/downloads/default.aspx.
You have not said if this is the same database!!!
John
"EvanHennis" wrote:
> On the test machine I am running Win2000 and I installed the MDAC 2.8. On the
> development maching I am in XP Pro. Which I beleive has MDAC 2.8 built in. Is
> there a way that I can compare the permissions and such on the MDAC?
> --
> Evan Hennis
>
> "John Bell" wrote:
> > Hi
> >
> > Being able to connecting to the database probably rules out permissions at a
> > OS level. It is not clear if this is a networked database or separate ones,
> > if the latter check for differences in the databases. If not it is most
> > likely environmental e.g. MDAC.
> >
> > John
> >
> >
> > "EvanHennis" wrote:
> >
> > > The actual error is:
> > > "Could not fetch a row from OLE DB provider 'VFPOLEDB'
> > >
> > > I am trying to connect to a local FoxPro database. Is there some security on
> > > the local computer I need to set?
> > > --
> > > Evan Hennis
> > >
> > >|||Same Database? Well, each computer has its own MSDE instance on it. They are
both connecting to a FoxPro database on the development machine. BUT, I have
tried connecting to a local FoxPro database on the test machine and it
doesn't work. But if I try to connect to a local database on the development
machine it works fine.
--
Evan Hennis
"John Bell" wrote:
> Hi
> Download the the MDAC component checker
> http://msdn.microsoft.com/data/mdac/downloads/default.aspx.
> You have not said if this is the same database!!!
> John
> "EvanHennis" wrote:
> > On the test machine I am running Win2000 and I installed the MDAC 2.8. On the
> > development maching I am in XP Pro. Which I beleive has MDAC 2.8 built in. Is
> > there a way that I can compare the permissions and such on the MDAC?
> > --
> > Evan Hennis
> >
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > Being able to connecting to the database probably rules out permissions at a
> > > OS level. It is not clear if this is a networked database or separate ones,
> > > if the latter check for differences in the databases. If not it is most
> > > likely environmental e.g. MDAC.
> > >
> > > John
> > >
> > >
> > > "EvanHennis" wrote:
> > >
> > > > The actual error is:
> > > > "Could not fetch a row from OLE DB provider 'VFPOLEDB'
> > > >
> > > > I am trying to connect to a local FoxPro database. Is there some security on
> > > > the local computer I need to set?
> > > > --
> > > > Evan Hennis
> > > >
> > > >|||Hi Evan,
It may not solve your problem, but be sure you've got the latest VFP OLE DB
provider (VFP9), downloadable from
http://msdn.microsoft.com/vfoxpro/downloads/updates . It is not included
with an MDAC installation.
Are you trying to read data or update data? Updating VFP data via a linked
server was not supported in earlier versions of the OLE DB data provider.
--
Cindy Winegarden MCSD, Microsoft Most Valuable Professional
cindy_winegarden@.msn.com www.cindywinegarden.com
Blog: http://spaces.msn.com/members/cindywinegarden
"EvanHennis" <EvanHennis@.discussions.microsoft.com> wrote in message
news:1628DF07-BF7C-4265-8B19-00733D8CA75F@.microsoft.com...
>I am running an MSDE of SQL Server 2000 with the latest server pack.
> I set up a linked server connecting to a FoxPro database using the
> vfpoledb
> provider.
> On my development machine I can get this linked server to work, but on my
> test machine, without a full SQL version, I get the error "Could not fetch
> a
> row...". Does anyone have any ideas on how to fix this? I have tried
> reinstalling the vfpoledb.exe but that didn't help it.
> --
> Evan Hennis|||Thanks for responding but I can't use the latest VFP OLE DB because we have a
pretty large application and I can't make a change like that. I am trying to
do a normal read, Updates are not supported.
I had this working at one point so I am stumped.
--
Evan Hennis
"Cindy Winegarden" wrote:
> Hi Evan,
> It may not solve your problem, but be sure you've got the latest VFP OLE DB
> provider (VFP9), downloadable from
> http://msdn.microsoft.com/vfoxpro/downloads/updates . It is not included
> with an MDAC installation.
> Are you trying to read data or update data? Updating VFP data via a linked
> server was not supported in earlier versions of the OLE DB data provider.
> --
> Cindy Winegarden MCSD, Microsoft Most Valuable Professional
> cindy_winegarden@.msn.com www.cindywinegarden.com
> Blog: http://spaces.msn.com/members/cindywinegarden
>
> "EvanHennis" <EvanHennis@.discussions.microsoft.com> wrote in message
> news:1628DF07-BF7C-4265-8B19-00733D8CA75F@.microsoft.com...
> >I am running an MSDE of SQL Server 2000 with the latest server pack.
> > I set up a linked server connecting to a FoxPro database using the
> > vfpoledb
> > provider.
> > On my development machine I can get this linked server to work, but on my
> > test machine, without a full SQL version, I get the error "Could not fetch
> > a
> > row...". Does anyone have any ideas on how to fix this? I have tried
> > reinstalling the vfpoledb.exe but that didn't help it.
> > --
> > Evan Hennis
>
>|||I downloaded the Component Checker and I don't see the VFPOLEDB.dll in the
list of files. Could this be the issue?
--
Evan Hennis|||Hi
I think Cindy has answered this! You can check the file version numbers by
looking at the file properties. If they are different you may have to either
change the way you are doing this or regression test the parts that use the
OLEDB provider.
John
"EvanHennis" wrote:
> I downloaded the Component Checker and I don't see the VFPOLEDB.dll in the
> list of files. Could this be the issue?
> --
> Evan Hennis
>|||I don't know what you mean by saying "Cindy has answered this"? I have
installed the VFP 8 Runtime and it doesn't seem to work. So I don't think it
has anything to do with my install. Is there some place that I can check to
see if I have the VFP OLE DB installed?
--
Evan Hennis
"John Bell" wrote:
> Hi
> I think Cindy has answered this! You can check the file version numbers by
> looking at the file properties. If they are different you may have to either
> change the way you are doing this or regression test the parts that use the
> OLEDB provider.
> John
> "EvanHennis" wrote:
> > I downloaded the Component Checker and I don't see the VFPOLEDB.dll in the
> > list of files. Could this be the issue?
> > --
> > Evan Hennis
> >|||I found the issue. For some reason my installer, which is an ENTIRE different
can of worms, wasn't installing the VFP stuff correctly. I reverted back to
an older version and that fixed my issue. I am still confused that when I
tried to install the run time from a downloaded exe that it didn't work.
Anyway, thanks for all the help.
--
Evan Hennis
"EvanHennis" wrote:
> I don't know what you mean by saying "Cindy has answered this"? I have
> installed the VFP 8 Runtime and it doesn't seem to work. So I don't think it
> has anything to do with my install. Is there some place that I can check to
> see if I have the VFP OLE DB installed?
> --
> Evan Hennis
>
> "John Bell" wrote:
> > Hi
> >
> > I think Cindy has answered this! You can check the file version numbers by
> > looking at the file properties. If they are different you may have to either
> > change the way you are doing this or regression test the parts that use the
> > OLEDB provider.
> >
> > John
> >
> > "EvanHennis" wrote:
> >
> > > I downloaded the Component Checker and I don't see the VFPOLEDB.dll in the
> > > list of files. Could this be the issue?
> > > --
> > > Evan Hennis
> > >|||Hi Evan,
The VFP runtime is different from the OLE DB data provider. The runtime
supports Visual FoxPro applications (EXEs and DLLs), and also access to Fox
data from within those applications. The OLE DB data provider supports
access to Fox data from "outside." I don't know how you installed the
runtime but it doesn't necessarily install the OLE DB data provider, unless
by the "runtime" you mean a full install of the Visual FoxPro IDE, which
will, of course, install the OLE DB data provider.
--
Cindy Winegarden MCSD, Microsoft Most Valuable Professional
cindy_winegarden@.msn.com www.cindywinegarden.com
Blog: http://spaces.msn.com/members/cindywinegarden
"EvanHennis" <EvanHennis@.discussions.microsoft.com> wrote in message
news:BFFC8772-7669-4429-8DA3-892BA5441C02@.microsoft.com...
>I found the issue. For some reason my installer, which is an ENTIRE
>different
> can of worms, wasn't installing the VFP stuff correctly. I reverted back
> to
> an older version and that fixed my issue. I am still confused that when I
> tried to install the run time from a downloaded exe that it didn't work.|||I am not sure why I was worried about the "runtime". It was a long worthless
day so who knows. Any way, the issue was with the VFP OLE DB provider not
getting installed. I redid my installer and it works now.
Thanks,
-- Evan Hennis
Could not fetch a row 'VFPOLEDB'
I set up a linked server connecting to a FoxPro database using the vfpoledb
provider.
On my development machine I can get this linked server to work, but on my
test machine, without a full SQL version, I get the error "Could not fetch a
row...". Does anyone have any ideas on how to fix this? I have tried
reinstalling the vfpoledb.exe but that didn't help it.
--
Evan HennisHi
I am not a VFP expert, but you may want to check that the locations for the
VFP database are correct and that MDAC versions are up-to-date and
consistent, and VFP is patched to the same level.
You may also want to see if your permissions on these machines varies.
If this is working on one machine and not the other implies the mechanism is
correct, although if the data is different it could be a factor.
The are plenty of posts concerning this error and VFP
http://tinyurl.com/94xhx and replies suggest that you check primary keys,
read http://support.microsoft.com/defaul...kb;en-us;207595 ...
John
"EvanHennis" wrote:
> I am running an MSDE of SQL Server 2000 with the latest server pack.
> I set up a linked server connecting to a FoxPro database using the vfpoled
b
> provider.
> On my development machine I can get this linked server to work, but on my
> test machine, without a full SQL version, I get the error "Could not fetch
a
> row...". Does anyone have any ideas on how to fix this? I have tried
> reinstalling the vfpoledb.exe but that didn't help it.
> --
> Evan Hennis|||The actual error is:
"Could not fetch a row from OLE DB provider 'VFPOLEDB'
I am trying to connect to a local FoxPro database. Is there some security on
the local computer I need to set?
--
Evan Hennis|||Hi
Being able to connecting to the database probably rules out permissions at a
OS level. It is not clear if this is a networked database or separate ones,
if the latter check for differences in the databases. If not it is most
likely environmental e.g. MDAC.
John
"EvanHennis" wrote:
> The actual error is:
> "Could not fetch a row from OLE DB provider 'VFPOLEDB'
> I am trying to connect to a local FoxPro database. Is there some security
on
> the local computer I need to set?
> --
> Evan Hennis
>|||On the test machine I am running Win2000 and I installed the MDAC 2.8. On th
e
development maching I am in XP Pro. Which I beleive has MDAC 2.8 built in. I
s
there a way that I can compare the permissions and such on the MDAC?
--
Evan Hennis
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Being able to connecting to the database probably rules out permissions at
a
> OS level. It is not clear if this is a networked database or separate ones
,
> if the latter check for differences in the databases. If not it is most
> likely environmental e.g. MDAC.
> John
>
> "EvanHennis" wrote:
>|||Hi
Download the the MDAC component checker
http://msdn.microsoft.com/data/mdac...s/default.aspx.
You have not said if this is the same database!!!
John
"EvanHennis" wrote:
[vbcol=seagreen]
> On the test machine I am running Win2000 and I installed the MDAC 2.8. On
the
> development maching I am in XP Pro. Which I beleive has MDAC 2.8 built in.
Is
> there a way that I can compare the permissions and such on the MDAC?
> --
> Evan Hennis
>
> "John Bell" wrote:
>|||Same Database? Well, each computer has its own MSDE instance on it. They are
both connecting to a FoxPro database on the development machine. BUT, I have
tried connecting to a local FoxPro database on the test machine and it
doesn't work. But if I try to connect to a local database on the development
machine it works fine.
--
Evan Hennis
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Download the the MDAC component checker
> http://msdn.microsoft.com/data/mdac...s/default.aspx.
> You have not said if this is the same database!!!
> John
> "EvanHennis" wrote:
>|||Hi Evan,
It may not solve your problem, but be sure you've got the latest VFP OLE DB
provider (VFP9), downloadable from
http://msdn.microsoft.com/vfoxpro/downloads/updates . It is not included
with an MDAC installation.
Are you trying to read data or update data? Updating VFP data via a linked
server was not supported in earlier versions of the OLE DB data provider.
Cindy Winegarden MCSD, Microsoft Most Valuable Professional
cindy_winegarden@.msn.com www.cindywinegarden.com
Blog: http://spaces.msn.com/members/cindywinegarden
"EvanHennis" <EvanHennis@.discussions.microsoft.com> wrote in message
news:1628DF07-BF7C-4265-8B19-00733D8CA75F@.microsoft.com...
>I am running an MSDE of SQL Server 2000 with the latest server pack.
> I set up a linked server connecting to a FoxPro database using the
> vfpoledb
> provider.
> On my development machine I can get this linked server to work, but on my
> test machine, without a full SQL version, I get the error "Could not fetch
> a
> row...". Does anyone have any ideas on how to fix this? I have tried
> reinstalling the vfpoledb.exe but that didn't help it.
> --
> Evan Hennis|||Thanks for responding but I can't use the latest VFP OLE DB because we have
a
pretty large application and I can't make a change like that. I am trying to
do a normal read, Updates are not supported.
I had this working at one point so I am stumped.
--
Evan Hennis
"Cindy Winegarden" wrote:
> Hi Evan,
> It may not solve your problem, but be sure you've got the latest VFP OLE D
B
> provider (VFP9), downloadable from
> http://msdn.microsoft.com/vfoxpro/downloads/updates . It is not included
> with an MDAC installation.
> Are you trying to read data or update data? Updating VFP data via a linked
> server was not supported in earlier versions of the OLE DB data provider.
> --
> Cindy Winegarden MCSD, Microsoft Most Valuable Professional
> cindy_winegarden@.msn.com www.cindywinegarden.com
> Blog: http://spaces.msn.com/members/cindywinegarden
>
> "EvanHennis" <EvanHennis@.discussions.microsoft.com> wrote in message
> news:1628DF07-BF7C-4265-8B19-00733D8CA75F@.microsoft.com...
>
>|||I downloaded the Component Checker and I don't see the VFPOLEDB.dll in the
list of files. Could this be the issue?
--
Evan Hennis
Could not fetch a row 'VFPOLEDB'
I set up a linked server connecting to a FoxPro database using the vfpoledb
provider.
On my development machine I can get this linked server to work, but on my
test machine, without a full SQL version, I get the error "Could not fetch a
row...". Does anyone have any ideas on how to fix this? I have tried
reinstalling the vfpoledb.exe but that didn't help it.
Evan Hennis
Hi
I am not a VFP expert, but you may want to check that the locations for the
VFP database are correct and that MDAC versions are up-to-date and
consistent, and VFP is patched to the same level.
You may also want to see if your permissions on these machines varies.
If this is working on one machine and not the other implies the mechanism is
correct, although if the data is different it could be a factor.
The are plenty of posts concerning this error and VFP
http://tinyurl.com/94xhx and replies suggest that you check primary keys,
read http://support.microsoft.com/default...b;en-us;207595 ...
John
"EvanHennis" wrote:
> I am running an MSDE of SQL Server 2000 with the latest server pack.
> I set up a linked server connecting to a FoxPro database using the vfpoledb
> provider.
> On my development machine I can get this linked server to work, but on my
> test machine, without a full SQL version, I get the error "Could not fetch a
> row...". Does anyone have any ideas on how to fix this? I have tried
> reinstalling the vfpoledb.exe but that didn't help it.
> --
> Evan Hennis
|||The actual error is:
"Could not fetch a row from OLE DB provider 'VFPOLEDB'
I am trying to connect to a local FoxPro database. Is there some security on
the local computer I need to set?
Evan Hennis
|||Hi
Being able to connecting to the database probably rules out permissions at a
OS level. It is not clear if this is a networked database or separate ones,
if the latter check for differences in the databases. If not it is most
likely environmental e.g. MDAC.
John
"EvanHennis" wrote:
> The actual error is:
> "Could not fetch a row from OLE DB provider 'VFPOLEDB'
> I am trying to connect to a local FoxPro database. Is there some security on
> the local computer I need to set?
> --
> Evan Hennis
>
|||On the test machine I am running Win2000 and I installed the MDAC 2.8. On the
development maching I am in XP Pro. Which I beleive has MDAC 2.8 built in. Is
there a way that I can compare the permissions and such on the MDAC?
Evan Hennis
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Being able to connecting to the database probably rules out permissions at a
> OS level. It is not clear if this is a networked database or separate ones,
> if the latter check for differences in the databases. If not it is most
> likely environmental e.g. MDAC.
> John
>
> "EvanHennis" wrote:
|||Hi
Download the the MDAC component checker
http://msdn.microsoft.com/data/mdac/.../default.aspx.
You have not said if this is the same database!!!
John
"EvanHennis" wrote:
[vbcol=seagreen]
> On the test machine I am running Win2000 and I installed the MDAC 2.8. On the
> development maching I am in XP Pro. Which I beleive has MDAC 2.8 built in. Is
> there a way that I can compare the permissions and such on the MDAC?
> --
> Evan Hennis
>
> "John Bell" wrote:
|||Same Database? Well, each computer has its own MSDE instance on it. They are
both connecting to a FoxPro database on the development machine. BUT, I have
tried connecting to a local FoxPro database on the test machine and it
doesn't work. But if I try to connect to a local database on the development
machine it works fine.
Evan Hennis
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Download the the MDAC component checker
> http://msdn.microsoft.com/data/mdac/.../default.aspx.
> You have not said if this is the same database!!!
> John
> "EvanHennis" wrote:
|||Hi Evan,
It may not solve your problem, but be sure you've got the latest VFP OLE DB
provider (VFP9), downloadable from
http://msdn.microsoft.com/vfoxpro/downloads/updates . It is not included
with an MDAC installation.
Are you trying to read data or update data? Updating VFP data via a linked
server was not supported in earlier versions of the OLE DB data provider.
Cindy Winegarden MCSD, Microsoft Most Valuable Professional
cindy_winegarden@.msn.com www.cindywinegarden.com
Blog: http://spaces.msn.com/members/cindywinegarden
"EvanHennis" <EvanHennis@.discussions.microsoft.com> wrote in message
news:1628DF07-BF7C-4265-8B19-00733D8CA75F@.microsoft.com...
>I am running an MSDE of SQL Server 2000 with the latest server pack.
> I set up a linked server connecting to a FoxPro database using the
> vfpoledb
> provider.
> On my development machine I can get this linked server to work, but on my
> test machine, without a full SQL version, I get the error "Could not fetch
> a
> row...". Does anyone have any ideas on how to fix this? I have tried
> reinstalling the vfpoledb.exe but that didn't help it.
> --
> Evan Hennis
|||Thanks for responding but I can't use the latest VFP OLE DB because we have a
pretty large application and I can't make a change like that. I am trying to
do a normal read, Updates are not supported.
I had this working at one point so I am stumped.
Evan Hennis
"Cindy Winegarden" wrote:
> Hi Evan,
> It may not solve your problem, but be sure you've got the latest VFP OLE DB
> provider (VFP9), downloadable from
> http://msdn.microsoft.com/vfoxpro/downloads/updates . It is not included
> with an MDAC installation.
> Are you trying to read data or update data? Updating VFP data via a linked
> server was not supported in earlier versions of the OLE DB data provider.
> --
> Cindy Winegarden MCSD, Microsoft Most Valuable Professional
> cindy_winegarden@.msn.com www.cindywinegarden.com
> Blog: http://spaces.msn.com/members/cindywinegarden
>
> "EvanHennis" <EvanHennis@.discussions.microsoft.com> wrote in message
> news:1628DF07-BF7C-4265-8B19-00733D8CA75F@.microsoft.com...
>
>
|||I downloaded the Component Checker and I don't see the VFPOLEDB.dll in the
list of files. Could this be the issue?
Evan Hennis