Printable View
I have been trying to install a package which references MSADO21.TLB - which is the Microsoft ActiveX Data Objects Library.
However I am consistently getting this error:
I have also tried MSADO20.TLB (V 2.0) with the same result.Quote:
There was an error when trying to register C:\WINNT\SYSTEM32\MSADO21.TLB
This was working fine the other day, but now I am consistently getting this error...
:confused:
This is the transcript of the install session from the .log file:
Quote:
*** ERROR: No entrypoint for DllRegisterServer() was found in 'C:\WINNT\system32\MSADO21.TLB'
*** DURING THIS ACTION: DllSelfRegister: "C:\WINNT\system32\MSADO21.TLB"
*** ERROR: An error occurred while registering the file 'C:\WINNT\system32\MSADO21.TLB'
*** ERROR: (User Responded with 'Ignore')
*** DURING THIS ACTION: DllSelfRegister: "C:\WINNT\system32\MSADO21.TLB"
I've also searched this site, and it seems over at least a year, various others have had similar if not identical problems, but no-one seems to have a solution...:confused:
Can you manually register it useing regsvr32?
What OS are you running?
It's WINNT. And I've tried in a network environment and just as a workstation. And no, I can't register it myself. It gives me:
as an error when I try that... (part of the same error report in the .log file...)Quote:
*** ERROR: No entrypoint for DllRegisterServer() was found in 'C:\WINNT\system32\MSADO21.TLB'
Here is all I could find in MSDN on the subject. I hope it helps.
This link might help, but it didn't do anything for me.Quote:
Referencing the ADO Libraries
As with any library that provides a type library, you must set a reference to the ADO library you want to use in your Visual Basic project. The type library for the current version of ADO is contained within the ADO DLL, msado15.dll. (To meet the needs of certain applications written with older versions, older versions of the type library can be referenced as well through the provided msado20.tlb, msado21.tlb, and msado25.tlb files.)
To reference the ADO library in your Visual Basic project, open the Project menu and click References. Scroll down and select Microsoft ActiveX Data Objects 2.7 Library. If an application compiled on a system with ADO 2.7 must run on a computer with a previous version of ADO installed, it needs to use one of the backwards compatibility type libraries. Add a reference to the appropriate .tlb file instead of to msado15.dll.
http://msdn.microsoft.com/library/de...tml/mdac25.asp
Ok, another piece of info: I noticed that when using the P&D wizard today, to try and rebuild the install, it couldn't find the dependancy info for MSADO21.TLB. I said keep going...blah...blah.
I'm trying again, and this time it didn't tell me that it couldn't find the dep info, so I'll see what happens this time...
Hmmm.... no good on that front. I'll try your info now.
Hmmm sounds like you need to re-install mdac to me.
Else go to mdac 2.7.
I'm in the process of getting MDAC2.7 now - just gotta free up 20MB on this computer's C: drive...:p
Hmmm... still having troubles.... :(
Initially I got a problem due to a lack of MSDART.DLL, which I have now included in my setup, so it all installs correctly, but then when I run the thing I get
Thanks Microsoft.... reeeeaaallll helpful...:rolleyes:Quote:
Method ~~ of ~~ Failed
I narrowed the problem down to run-time error 3706.
The detail from MSDN is this:
What does this mean, and how do I solve it?Quote:
Provider cannot be found. It may not be properly installed.
Post the code that you are using for your connection string. There may be a clue there.
Mega.
That's pretty much it. I actually have it on one line, so I just split it up then.Code:Global Const strConnection = "Driver={Microsoft Access Driver " & _
"(*.mdb)};Provider=MSDASQL.1;Persist Security " & _
"Info=False;Extended Properties='DBQ=" & CurriculumDirectory & _
"courseDocs.mdb;DefaultDir=" & CurriculumDirectory & _
";DriverId=281;FIL=MS Access;MaxBufferSize=2048;" & _
"PageTimeout=5;UID=admin;PWD=safety;Initial Catalog=" & _
CurriculumDirectory & "courseDocs'"
As I may have mentioned, it was working, until the other day. I changed nothing at all in regards to the DB, and it wouldn't install properly after that. Now I've updated to MDAC2.7, and it installs OK, but then I get that nuisance error there, which I tracked down to
RunTime Error '3706' - Provider not installed correctly or something
See this thread also: http://www.vbforums.com/showthread.p...hlight=mdac2.7
Does it work on your machine okay and the problem lies with when you install it elewhere? or.. can you not get it to work now either?
Mega.
MY machine is fine, it has VB on it, and various other things.
The problem on other machines isn't apparent if I had previously installed it on them either.
The initial install error still came up, but it didn't affect the program, as I guess there was correct stuff already on that machine, but when installing on a 'new' machine, It installs ok, but then doesn't work (as per error described)...
It is absolutely essential that MDAC is installed on the host machines and it must be the same (or higher) version that you used to compile the program.
I assume you have done this?
Mega.
You'd think so wouldn't you... ;)
No, I'm pretty sure that at the original installation it installed the MDAC, but this would have been when I was using V2.0 or 2.1. Now I've upped to 2.7 - how do I install that on the other machine?
I thought it was automatic, as part of the P&D setup.exe, but I am probably wrong...
Ok, ta, I'll give that a burl.
:)
Yep, got that already. Now I'm in the process of downloading the Service Packs so I can install the latest IE, so I can install MDAC2.7...:rolleyes:
:p
LOL :)
I hope it works after all that.
Mmm... me too...:p
Cheers.
Far out... give me a break.... I've now installed all that stuff, and I'm getting an Error saying
"...[Microsoft ODBC Driver]...Could not open registry key (null)..."
or something.... ****ing hell - this thing just doesn't want to work does it...:rolleyes:
Bummer:(
Have you tried....and this is a long shot...reinstalling vb itself. Almost sounds, if it was working, that something has corrupted itself somewhere...as l say long shot, but what the hey:rolleyes:
Fixed a problem we were having with Excel by doing this, after of course spending a week scouring code, msdn, etc.....
Somethings just suck for no apparent reason, we feel your pain, and are only smiling slighty at it....in that phew it's not me dealing with it sort of way....
Hope it helps, or focuses or whatever...
The thing is, the exact same install package will work on other machines on the same network... I am soon to test it on a fesh machine, as all the ones where it works are ones I had previously installed to (including MDAC), so I need to know if it is a corruption problem of some sort...
Still waiting though - getting things done, including obtaining resources - in here is a ****ing big slow hassle...
What was your problem again rj?
hhhhhahahahahehe ;)
Ok you never said you were using sql!
Quote from MS: "Due to issues with clustering, this release is currently NOT supported on SQL 7.0 Clustered Servers or SQL 6.5 Clustered Servers"
Even if this isnt your case try what i mention below!
So 2 things you can do. Go back and try 2.5 or use the provider SQLOLEDB instead od MSDASQL!
Hope this is it!
If is working on other machines, then deffiantly corruption dude. Tried to answer in chit chat and went into some weird error...but...
Which version of NT service packs etc on this machine and one that it does work on. Am finding allsorts of problems with NT 4 SP 6, so that may be it. Currently moding a vb5 app, adding a few tables and sorting routines, the program works at work, but here l can't even get the original code to run:(
But it works on other virtually identical machines... :( Why would changing the provider make a difference?
But I shall keep it in mind...
As for 2.5, I don't know if I even have that anymore - when I installed MDAC2.7, I lost references to earlier versions... :eek:
And anyway, 2.5 was always giving me stupid problems when distributing...
It had SP5, but in a vain effort to improve it (by installing MDAC 2.7) I installed SP6, and then IE6... no change on that machine...Quote:
Originally posted by Jethro
If is working on other machines, then deffiantly corruption dude. Tried to answer in chit chat and went into some weird error...but...
Which version of NT service packs etc on this machine and one that it does work on. Am finding allsorts of problems with NT 4 SP 6, so that may be it. Currently moding a vb5 app, adding a few tables and sorting routines, the program works at work, but here l can't even get the original code to run:(
The machines it works on are either SP5 or SP6. My testing machine is SP6, everything works on it - my dev. machine is SP5 - everything works on that... :(
Anyway, still waiting on tester number 2...
Real bummer:( Sounding awfully like a rebuild to me. Was msdn any help at all? Could go and check the error number if you like, have membership (hopefully if SK has got off his ass and done it like he promised)...
The new error number is about 10 digits long... :rolleyes:
I'll have to get it...
Another suggestion, which might be lamer than the first, but then why not cut out all the simple answers. On the machine with the problems try network neighbourhood to ensure you have access to the database...who knows stranger things have happened:confused:
Geez, this is a pain...
I put in error handling stuff, and now the error number isn't displayed...
The worst bit is that the offending machine is 50m up the hall...:rolleyes:
Access is fine - it's in the general shared area. That machine doesn't have Access anyway, so I can't open it up.Quote:
Originally posted by Jethro
Another suggestion, which might be lamer than the first, but then why not cut out all the simple answers. On the machine with the problems try network neighbourhood to ensure you have access to the database...who knows stranger things have happened:confused:
*Jethro waiting for rj to get back.....oh and the error text as well would be helpful;)Quote:
Originally posted by rjlohan
Geez, this is a pain...
I put in error handling stuff, and now the error number isn't displayed...
The worst bit is that the offending machine is 50m up the hall...:rolleyes:
50m up the hall...not a novell network you got there is it :confused: Have had problems with that stuff, that could cause this....something about distance, and couldn't we move the machine according to the novell tech....like right, and that's why novell ain't selling partner:mad:
Quote:
Originally posted by Jethro
*Jethro waiting for rj to get back.....oh and the error text as well would be helpful;)
50m up the hall...not a novell network you got there is it :confused: Have had problems with that stuff, that could cause this....something about distance, and couldn't we move the machine according to the novell tech....like right, and that's why novell ain't selling partner:mad:
Well, now that you mention it.........
NEed more time - gotta recompile minus the error 'handling'...
Would be talking to novell then rj, their networks suck over any distance...and may be the cause of your problemQuote:
Originally posted by rjlohan
Well, now that you mention it.........
Ok, here it is.
It occurs identically twice, when I attempt to make a DB connection...
Quote:
Err: -2147467259
[Microsoft][ODBC Microsoft Access 97 Driver]General Error. Unable to open registry key '(null)'.
Yeah right - like I'm gonna get them to change their network...they won't even upgrade from Internet Explorer 2.3 without a fuss...:rolleyes:Quote:
Originally posted by Jethro
Would be talking to novell then rj, their networks suck over any distance...and may be the cause of your problem
Yeah, but if you can claim it's a network issue, then you can hand the problem over to the sysops....sit back....and drink coffee, safe in the knowledge that some one else's ass is in the sling;)
Ok off to msdn, will try to find something there for ya...
I don't really need to blame anyone today, but I'll keep that in mind... ;)
Cheers.
Ok this is the only reference l got on my search
http://support.microsoft.com/directo...h_SRCH&SPR=ADO
Log in and have a look, hopefully the answer is in there;)
Dickheads...:mad:Quote:
STATUS
Microsoft is researching this problem and will post new information in the Microsoft Knowledge Base as it becomes available.
This was in reference to a specific DB (advworks) or something, but I reckon it may be the same problem.... shall continue looking...
No you said that some machines have 2.7 some have 2.1 some have 2.5!Quote:
Originally posted by rjlohan
But it works on other virtually identical machines... :( Why would changing the provider make a difference?
But I shall keep it in mind...
As for 2.5, I don't know if I even have that anymore - when I installed MDAC2.7, I lost references to earlier versions... :eek:
And anyway, 2.5 was always giving me stupid problems when distributing...
Changing the provider to the one mentioned might help because that provider will work with all mdac's released!!
Is this an access or SQL database??
Access.
I thought that MDAC2.7 would be installed on those machines, since I have references to it in my project... am I mistaken?
Ok another thought, pop into the Access db and compact it maybe....could be corrupt if stand alone???? Though you would probably get an unidentified db sort of error l guess.
Gotta Log,
Cya Later....
Try connecting using ADO and Jet the usual way! You know Set cn as new.adodb connection blablah!!
Does that work?
If so you can round it down to a few things!
later
b :)
As opposed to what? I thought that's what I was doing...Quote:
Originally posted by Beacon
Try connecting using ADO and Jet the usual way! You know Set cn as new.adodb connection blablah!!
Does that work?
If so you can round it down to a few things!
later
b :)
:confused:
as opposed to this:
VB Code:
I never connect like that.
I use
strConnectionString = "..."
cnn.Open strConnectionString
etc. etc.
Same dog different tree!
Try it butmunch!;) :p
Try which?
I use this:
[code[]
Set cnnExamCentre = New ADODB.Connection
Set rstExamCentre = New ADODB.Recordset
'Open database connection
cnnExamCentre.Open strConnection
:
:
:
'Close database connection
cnnExamCentre.Close
[/code]
Try anyone that is different to the one you posted earlier in this thread!
...Which means you can't register them via RegSvr32.exe or anything else.
Usually what I do is just chuck them in the %WinSysDir% or in this case, the %Common Files%\System\ADO and they work ok.
Maybe try a simple DAO connection to narrow down the possibilities.....
Was trying this today...but my friggin data disk has disappeared into the ether....
Just to help out
Starting with 2.1, and then try 2.7, may or may not get the same problem, but if l do can hand it off to some of the resident MS specialists in the office...
I haven't solved it yet, mind you I have put it off temporarily for more URGENT work... :p
Found this on a software companies site for faq. Sounds similar so it's worth a shot.
E11. [S1000][Microsoft][ODBC Access 97 ODBC Driver]General error Unable to open registry key 'DriverId'.
This exception happens when the ODBC data source you setup for your Access database contains certain security protection such that an NT background service like IDS Server is not able to read. The solution is to run the IDS Server using your own user account (See FAQ-G14).
G14. How to run IDS Server using a specific user account on Windows NT?
By default, IDS Server on Windows NT is run as a NT service using the default 'system' account. This account has minimum security, network and other customization. Sometimes it is necessary to run the IDS Server service using a specific user account so that the server inherit configurations such as ODBC data sources and network drive mappings setup using that account. Here is how you can do it on NT 4.0:
1. Run Control Panel - Services, find and highlight the IDS Server service and click on the "Startup..." button.
2. Select the "This Account:" radio button, then type in the user account in the edit box to the right (for example administrator or informix). Then enter and confirm the Windows NT password of the selected user account in the two remaining edit boxes.
3. Click "OK". Stop