January 15, 2009 at 3:16 pm
So I have a cluster of 6 nodes... Node 1 runs instance 1, Node 2 Instance 2, etc..Nodes 5&6 run no instances and are there so we can fail over to them if necessary.
Not sure if it matters... this is about OPENDATASOURCE.
On Node 4, from instance 4 I tried to run the following command.
Select * from OPENDATASOURCE
('Microsoft.Jet.OLEDB.4.0',
'Provider=Microsoft.Jet.OLEDB.4.0;
Password=xxxx;User ID=AppAdmin;
Data Source=\\CLUSTER1-SQL4\u$\MDBToSQLMigrate\WORKING\SOURCE.MDB;
Persist Security Info=True;
Jet OLEDB:System database=\\CLUSTER1-SQL4\u$\MDBToSQLMigrate\WORKING\SYSTEM.MDW'
)...AccountDefaults
The result of this is:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" returned message "Unspecified error".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)".
I've checked the following.
The sql instance and the sql agent are both running under accounts with administrative priveleges to the Nodes of the cluster
They have full access to the c:\documents and settings\sqlservice\local settings\temp directories on all nodes of the cluster
The path and files exist and can be accessed from any of the instances.
They also have full access to the folders and files to be accessed.
I've checked the version on the Microsoft.Jet.OLEDB.4.0 and it's the latest version corresponding to Windows 2k3 SP2.
SQL is at SP2, and Remote Ad-hoc queries are enabled.
The next thing I'd look at is making sure the account has delegation properties set, but this happens even if I'm running the query directly on the SQL server, which seems to me to mean there's no delegation involved...
I'm out of ideas... any thoughts?
January 16, 2009 at 8:17 am
Hoping somebody has an idea... I've been watching process monitor and there's not even an attempt to access the UNC that I can see in it... so something is irking SQL prior to it attempting to open the mdb file.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply