2147467259 was generated by Microsoft OLEDB Persistence Provider Unspecified Error
I have an Access front end working with data in a SQL Server 2005 back end. Everything works well, but for some users who have slower connections, through a VPN, they get errors like Error#-2147467259 was generated by Microsoft OLEDB Persistence Provider Unspecified Error. I cannot find any specific information on this one, but it seems to me it has to do with the volume of data and the slowness of the connection, like the SQL being executed has timed out. I can run an mdb on this users machine and trap the offending SQL statement, put it into my SQL Server Management Studio and with my very fast connection, it runs with no error.
Does this make sense? Can anyone shed any light on the situation? Is there a SQL Server 2005 setting I can change to allow for a longer timeout, if that is what it is?
Does this make sense? Can anyone shed any light on the situation? Is there a SQL Server 2005 setting I can change to allow for a longer timeout, if that is what it is?
-2147467259 is decimal number in hex it's: 80004005
and it means "Class not registered".
This error is standard COM error telling that app is trying to access/launch COM interface that is not registered (with regsvr32) or you dont have permissions (dcomcnfg) to access it.
The big question now is which COM component is not registered, if you knew exact dll/ocx that would be easier. In your situation i would try to reinstall MDAC (because error comes from Microsoft OLEDB) see here: http://msdn2.microsoft.com/en-us/library/ms810805.aspx for more details.
ziolko.
and it means "Class not registered".
This error is standard COM error telling that app is trying to access/launch COM interface that is not registered (with regsvr32) or you dont have permissions (dcomcnfg) to access it.
The big question now is which COM component is not registered, if you knew exact dll/ocx that would be easier. In your situation i would try to reinstall MDAC (because error comes from Microsoft OLEDB) see here: http://msdn2.microsoft.com/en-us/library/ms810805.aspx for more details.
ziolko.
ooops sorry my mistake 80004005 means unspecified error
ziolko.
ziolko.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check if your Access uses Native SQL client which is the best choice.