June 27, 2011 at 9:58 am
Hello All, I am using SQL 7 (Server 2000) and have a stored procedure that creates a linked server to an .mdb that is located on another server (Server 2000). We recently upgraded some of our hardware and the server that the .mdb resided on is now on a new server (Server 2008). Since then, I am unable to link in servers from this new server. I thought at first it had to do with it being a 2008 server, however I just tried to put the .mdb on another 2000 server and it still won't link. I am figuring that there must be something on the server itself i should change to make this linking work. Does anybody know what? Thanks.
June 27, 2011 at 10:05 am
Once had a very similar issue. Tho is was for a dbase 4 file. The issue was that after the upgrade with had to add admin as the user with a blank password.
I would however start with plan A : IE make sure you can see the file from the new server (ntfs permission).
June 27, 2011 at 10:09 am
I can see and open the file that resides on my 2008 server from my sql 7 server. I have made sure the permissions on the folder is full control for everyone. I even followed this article http://support.microsoft.com/kb/814398 and added the temp/tmp environmental variables and made sure the everyone had full control of those as well.
June 27, 2011 at 10:11 am
So the old linked server to the old location still works?
Just copy the settings to the new server. If that doesn't work try the admin trick I just told you about.
June 27, 2011 at 10:20 am
I think i might be confused by your questions, so please bear with me.. If I move the .mdb from the new location to another server (2000) that i know works, then the .mdb works just fine, so it's not the .mdb itself. No .mdb that is on the new server will link in from the new server but they will link in from another server. What settings do I need to set up/change on the windows 2008 server to get the .mdbs to work? My short term solution was to move all of them to another server that works, but this is not where I would like these to reside and at the end of July we are finally upgrading that server as well so then I might be where no server works, that's why I want to get this new one working before this happens. Thanks.
June 27, 2011 at 10:26 am
My point was find a location where it works then change only 1 variable at a time untill it breaks.
You have a server / mdb that works. Awesome.
Only change the server and recreate the linked server exactly as it was on the old one. Make sure the new server can read from that share (you can do a simple test with xp_cmdshell 'dir \\shared\folder\*.mdb'
Change all the variables 1 at a time and tell use where and how it breaks then we can help fixing it.
June 27, 2011 at 10:31 am
Ok, Yes, i have created a test link manually and only changed one thing at a time. I copied the exact .mdb from the new not working location to a server that I know works and then the link works, so the only variable change is the server. I have run xp_cmdshell on my new not working server path and i can see the directory just fine and again I can navigate to and open the .mdb with no issues. It just won't link.
June 27, 2011 at 10:40 am
In the linked server info, add the login admin with a blank password and see if that fixes it (took 3 hours and 4 of us on a pss call to figure this one out...).
June 27, 2011 at 12:06 pm
To make sure we are on the same page, I have manually created a linked server named TEST. On the Security tab of the properties, I changed the option button to "Be made using this security context:" and used admin and <blank> as the login and password. Let me know if this was incorrect. This change did not work for me, still can't link the .mdb.
June 27, 2011 at 2:49 pm
Sounds about right. Just to be safe try all 3-4 options for the login type. That's how we actually found the "fix".
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply