Accessing Registry errors with External Access

Question

We have a dll that we use to read HKEY_LOCAL_MACHINE\Software\GGPL\Myriad and this is working fine under SQL Server 2008 R2 on Windows 7, I also have SQL Server 2005 SP4 installed and the same dll does not work. When I do a Registry.LocalMachine.OpenSubKey("SOFTWARE\\GGPL\\Myriad", False) it returns nothing.

I can get to SOFTWARE ok but any deeper and I have a problem, both instances of SQL Server are running under the same user.

I have a similar problem at a client site that is running SQL Server 2005 on Windows Server 2008 R2 and I'm trying to fix the problem when I managed to replicate the problem on my own machine.

Thanks,

Andy

Answer 1

I do think  such registry errors relate more to App itself particularly more if SQL Server 2005 SP4 instances are up and running fine, thereby I do recommend to check on with its Vendor

---

Shehap (DB Consultant/DB Architect) Think More deeply of DB Stress Stabilities

Answer 2

Hi Shehap,

I think you may have mis understood my original post and I did not give a full history.

We have the App working on SQL Server 2005 at several clients including some running Server 2008 R2, but it does not work on my Windows 7 machine or a particular client running Windows Server 2008 R2. It is the same App that we are using, but this App works in SQL Server 2008 R2.

I need to work out what the difference is between SQL 2005 and 2008 R2 that is causing the problems.

Andy

Answer 3

Hi Andy,

Thanks for your post.

The information you provided is not enough for us to detect the problem. Please post the dll so that we can troubleshoot the problem directly.

---

Best Regards,
Iric
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 4

Hi Iric,

By dll do you mean the code for it or the actual dll itself.

Thanks,

Andy

Answer 5

That is why I am saying referencing the vendor itself is preferable choice here to seek computability sheet with SQL Server editions to narrow down error scope as Iric asked for also

---

Shehap (DB Consultant/DB Architect) Think More deeply of DB Stress Stabilities