MSOLEDB Provider for SQL Server: Cannot find data type <whatever>

Posted on 2008-10-30
Medium Priority
Last Modified: 2013-11-05
Recently had to perform an emergency transfer of a SQL Server Database from one server to another - managed to create a virtual drive for the Database files to "live" on, and mounted them to the new server.  Made the server "aware" of the new database, and everything seemed to be rolling fine.

Now, for some reason, it cannot find/access User-Defined Data Types, and there they are, plain as day, under the Database->Programmability->Types->User-defined Data Types.  Is there some sort of process I'v left out to tell the SQL Server that it needs these data types?

Oh yeah - I almost forgot: we're getting this error from an Access Application that directly "talks" to SQL Server.  (Don't laugh too loud - it's supposed to be our Accounting Software.)  If this makes any difference, which I don't believe that it does.

I'm not sure where to go from here...   ?
Question by:LongFist
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
LVL 43

Accepted Solution

Eugene Z earned 1500 total points
ID: 22849035
< transfer of a SQL Server Database from one server to another>
did you install at least sp1 on on new server (check MDAC version too)

Author Comment

ID: 22849568
Apparently not.  I ran the following SQL command on the server:

WITH Version(ver)
        CHARINDEX(' - ', @@VERSION)+3,
SELECT Build = LEFT(ver, CHARINDEX(' ', ver))
    FROM Version

Results: 1 row(s) affected

...meaning I'm running the RTM, no apparent patches or service packs installed.

So, now it's off to find the latest service pack for SQL Server 2005 Standard, right?  Right.

Microsoft Data Access Components (MDAC)  2000.086.3959.00 (srv03_sp2_rtm.070216-1710) --- but wouldn't that be more concerned with data connections than SQL Server's handling of UDTs?  (Just asking...)

Author Comment

ID: 22850560
Now patched to version 9.0.3042 - SP2 fully in effect.

No joy, error persists.  Same place: encounters user data type (that exists in the database definition), errors out.  Is there some "association" algorithm that should be run, or something?  Or is SQL Server just that full of "automagical" capacity?

Frustrated, very frustrated...    (...not your fault, mind you, but just noting the mindset to avoid possible misunderstandings...)
Get real performance insights from real users

Key features:
- Total Pages Views and Load times
- Top Pages Viewed and Load Times
- Real Time Site Page Build Performance
- Users’ Browser and Platform Performance
- Geographic User Breakdown
- And more

LVL 43

Assisted Solution

by:Eugene Z
Eugene Z earned 1500 total points
ID: 22854110
can you run the Access from the sql server?
what statement was used against sql server? Can you run it on sql server directly?
are you sure it is pointed (linked) to new sql server?

SELECT  SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),

Author Comment

ID: 22867894
Okay - this is extremely embarassing!  It turns out that the problem wasn't in SQL Server at all - no, it was in how the application was handling things.

It turns out that there was a third Database - SYS - that contained (among other things) references to where those UDT's were kept: more lousy development on their part, as this is something SQL Server will do auto-magically, if you let it.  But I guess it's to be expected: they used MSAccess 2K3 as their application "front end", and that's caused no end of troubles when setting it up on machines that have Office 2K7 or the like.  SYS needed backing up, deleting, re-building, and then restoring (overwrite?) from the backup to make it all work right.  And no, it's nothing that we would have thought of in a thousand years...

So, while were doing everything that we knew to do, nobody thought to see if the application platform was short-circuiting the existing system.

I'm truly sorry I bothered everybody, since it was third-party error in the first place.  How do we handle this sort of situation?
LVL 43

Assisted Solution

by:Eugene Z
Eugene Z earned 1500 total points
ID: 22870888
no problem - do not be sorry -
Most important it is resolved :)
good job!

Author Closing Comment

ID: 31511873
The problem actually resided in the third-party application, not SQL Server itself.  However, without the expert's guidance and creativity, the problem might not have been noticed.  Therefore...

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In SQL Server, when rows are selected from a table, does it retrieve data in the order in which it is inserted?  Many believe this is the case. Let us try to examine for ourselves with an example. To get started, use the following script, wh…
In this article I will describe the Copy Database Wizard method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
If you’ve ever visited a web page and noticed a cool font that you really liked the look of, but couldn’t figure out which font it was so that you could use it for your own work, then this video is for you! In this Micro Tutorial, you'll learn yo…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…

800 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question