Upsizing Wizard

[GCeaser]

All,

I have created an ODBC entry that links to a new SQL Server
Express 2005 file database (mdf) file. I have tested the connection
via the ODBC tools in Windows XP and it says everything is fine. When
I attempt to utilize the Upsizing Wizard in MS Access V2003, I say use
an existing database and select the existing File Data Source DSN file
as the data source. When I do this, I receive the following error
message:

Reserver Error (-1038); there is no message for this error.

Does anyone have an idea why I might be getting this?

Thanks
George

 

[Michael Cheng [MSFT]]

Hi George,

Welcome to use MSDN Managed Newsgroup!

From your descriptions, I understood you would like to you encounter the
Reserver Error (-1038); when using Upsizing Wizard to SQL Server 2005
Express. If I have misunderstood your concern, please feel free to point it
out.

I followed your steps and it works fine on my side. Would you please check
the following questions?

- Whether you have upgraded your Windows XP to SP2?
- Please use Machine DataSources to see whether it will also report the
same error message?
- What's the exact error message? Is it possible for you to attach a print
screen here?
- Could you find more information on Event Log?
- Is it possible for you to create a linked table based on SQL Server 2005
Express from Access?

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!


Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[GCeaser]

Michael,

Your understanding of the problem is correct as long as you got the
part that the SQL Server 2005 Express database I am trying to upgrade
to is a file database stored in the App_Data folder in a VS 2005
project.

The OS is running XP SP2. I will try the above mentioned items
and post the results of those test items. Thanks for your help.

George

 

[GCeaser]

Michael,

Here are the results of my testing:
Below are the exact options I used in creating a Machine Datasource:

l. On the Driver Screen select:
SQL Native Client

2. On the Create a New Datasource for SQL Server Screen:
Name = ExpressJobTracking
Description = Job Tracking Express Database
Server = .\SQLExpress

3. On the How should SQL Server verify the authenticity of the login
ID screen select:

With Integrated Windows Authentication
and Check - Connect to SQL Server to obtain default settings for the
additional configuration options.

4. On the next screen:
Check the Change Default database to: Xjobtracking

5. On the final screen I only select the 'Perform translation for
character data' option.

I click finish and click the ODBC Microsoft SQL Server Setup window
shows with the following values:


Microsoft SQL Native Client Version 09.00.1399

Data Source Name: ExpressJobTracking
Data Source Description: Job Tracking Express Database
Server: .\SQLExpress
Use Integrated Security: Yes
Database: Xjobtracking
Language: (Default)
Data Encryption: No
Trust Server Certificate: No
Multiple Active Result Sets(MARS): No
Mirror Server:
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes
Attach Database Filename: C:\Visual Studio 2005
Projects\JobTracking\App_Data\Xjobtracking.mdf

I test the connection and it succeeds.

6. I start MS Access and open my MDB file
7. I select tools --> Database Utilities --> Upsizing wizard
8. I select use an existing database and click next
9. On the Select Data Source window, I select the Machine Data Source
named ExpressJobTracking entry and click OK.
l0. I receive the exact error message in a small pop up window:
Window Title: Upsizing Wizard
Message: Reserved error (-1038); there is no message for this error.

Any help would be greatly appreciated.
George

 

[GCeaser]

Oh - one more things.. I can use the linked table option and select the
machine DSN to link to a table in the database.

Thanks
George

 

[Michael Cheng [MSFT]]

Hi George,

Thanks for your detailed update.

However, it seems strange and the error message also indicated this is a
reserved error message. We will have to debug and check what was going on
internal, this work has to be done by contacting our Microsoft Customer
Service and Support and open a support incident and work with a dedicated
Support Professional.

Please be advised that contacting phone support will be a charged call.
However, if you are simply requesting a hotfix be sent to you and no other
support then charges are usually refunded or waived.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!


Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[GCeaser]

OK - So I finally got it to work. This is how I did it. I copied the
MDF file out of the App_Data directory from my VS 2005 project and
pasted it into a folder on my C drive. (The full path was now C:\SQL
Express Databases\Xjobtracking.mdf). Then deleted my old machine DSN
and created a new one pointing to the file in the C:\SQL Express
Databases directory. After that, Access was able to connect to the
file fine. I am not sure if this the real solution to the challenge (I
would certainly hope not) but that is all that I know I changed. OH -
The only other thing I did was try to install MDAC 2.8 SP1 on my
machine which promptly failed and gave me the error message that it was
not supported on my OS (XP SP2). I hope this helps someone else.

George

 

[GCeaser]

OH - One more thing - I already had SQL Server Management Studio
Express installed. Before moving the MDF file and re-creating the DSN,
I deleted a second SQL Express instance I had on the machine named
jtexpress using the SQL Server Management Studio. It asked me if i am
sure I want to remove the selected registered service and I say yes.
The instance goes away from the database engine tree view. However,
when I right mouse click on database engine and select Update Local
Server Registration, the instance I thought I deleted re-appears. Oh
well. I am just trying to help anyone else out there who is getting my
original error on the upsizing wizard.

 

[Michael Cheng [MSFT]]

Hi George,

Thanks for your email and it's great to know you have resolved it by
creating a new ODBC access.

The latest MDAC available is 2.80 from download.microsoft.com while MDAC in
XP SP2 is 2.81. Since you have installed XP SP2 (MDAC 2.81), you get the
error message that prevent you installing


Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[GCeaser]

Micheal,
Just to be clear, it was not the creation of a new ODBC access that
resolved this challenge, at least not by itself, as I have done that
many times and retried the upsize wizard and it still failed. It must
be some combination of what I tried. I just want to make it clear to
anyone reading this that creating a new ODBC entry did not soley
resolve my problem.

Thanks
George

 

[Michael Cheng [MSFT]]

Hi George,

Thanks for the update and I believe communities will benefit from this
valuable experience sharing.

I am still looking into the possible root cause for this issue. If I find
anything valueable, I will keep you updated.



Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.