none
MDS Error: 0 : Evaluation period has expired.

    Question

  • Hi,

    I had a SQL Server 2008 R2 Enterprise installed now I downloaded the SQL Server 2012 trial to try the new features.

    I uninstalled the 2008 R2 version and installed the 2012 trial edition.

    There was no problem, but the Master Data Services web application fails, it says that the Evoluation period has expired. 

    I tried to find some information about this issue, I found the following forum without solution:

    http://social.msdn.microsoft.com/Forums/en-IE/sqldenmds/thread/25bbd187-4d75-4735-baae-5b1607022608?prof=required

    I set the web.config to log to file, now I have the following log entries in the log file:

    MDS Error: 0 : Service started successfully,  Assembly version: 11.0.0.0, file version: 11.0.2100.60 ((SQL11_RTM).120210-1917 )
        DateTime=2012-06-03T20:45:26.0209765Z
    MDS Error: 0 : ApiContractVersion: 5102
        DateTime=2012-06-03T20:45:26.0366015Z
    MDS Start: 1 : Service.InitializeExpirationStatus
        DateTime=2012-06-03T20:45:26.0522265Z
    MDS Error: 0 : Error 193 (0x000000c1). Unable to load sqlboot.dll from path: C:\Program Files\Microsoft SQL Server\110\Shared\sqlboot.dll
        DateTime=2012-06-03T20:45:26.0678515Z
    MDS Stop: 2 : Service.InitializeExpirationStatus
        DateTime=2012-06-03T20:45:26.1303515Z

    ...

    MDS Stop: 2 : Service.InitializeExpirationStatus

    I checked the dll file in C:\Program Files\Microsoft SQL Server\110\Shared\sqlboot.dll still exists...

    Have you got any idea how to solve this problem?

    Thanks in advance!

    Gabor Varga

    Sunday, June 03, 2012 9:56 PM

Answers

  • Hi,

    It is strange... I made the following modificiation for testing:

    - I renamed the C:\Program Files\Microsoft SQL Server\110\Shared\sqlboot.dll to C:\Program Files\Microsoft SQL Server\110\Shared\sqlboot.dll.x64

    - I copied the C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlboot.dll to C:\Program Files\Microsoft SQL Server\110\Shared\sqlboot.dll

    - I tried to open http://localhost/MDS

    - now it works fine! :-$

    (the server is Windows 2008 R2 SP1 x64)

    Any idea?

    Best regards,

    Gabor

    • Marked as answer by Madve Sunday, June 03, 2012 10:20 PM
    Sunday, June 03, 2012 10:20 PM
  • The problem returned after installing CU2. Same workaround -- copy sqlboot.dll from x86 directory (and reboot).

    -Megan

    • Marked as answer by Madve Thursday, June 28, 2012 7:29 PM
    Friday, June 22, 2012 4:58 PM

All replies

  • Hi,

    It is strange... I made the following modificiation for testing:

    - I renamed the C:\Program Files\Microsoft SQL Server\110\Shared\sqlboot.dll to C:\Program Files\Microsoft SQL Server\110\Shared\sqlboot.dll.x64

    - I copied the C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlboot.dll to C:\Program Files\Microsoft SQL Server\110\Shared\sqlboot.dll

    - I tried to open http://localhost/MDS

    - now it works fine! :-$

    (the server is Windows 2008 R2 SP1 x64)

    Any idea?

    Best regards,

    Gabor

    • Marked as answer by Madve Sunday, June 03, 2012 10:20 PM
    Sunday, June 03, 2012 10:20 PM
  • MDS is only 64 bit as far as I know, so normal that it would point to the 64-bit C:\Program Files\Microsoft SQL Server\110\Shared\sqlboot.dll

    Your IIS is 64-bit right? If you look at W3Wp.exe in task manager, on the processes tab, it doesn't have *32 beside it does it?

    Wierd how putting a 32-bit copy of the dll into the 64-bit program files 110\Shared folder would work. That seems like it wouldn't work, so it seems counterintuitive.

    Maybe the file was corrupted for some reason. A bad /failed file copy, or bad sector on the disk.

    Or there could be a 2012 setup problem, could be that when you install 2012 with just MDS the sqlboot.dll is the wrong copy. Maybe if you install MDS + other features of SQL 2012 that problem doesn't happen. (most people have multiple features I suspect). If you find this is a bug by further testing, let me know so we can investigate.

    Thanks, Jason


    Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance

    Friday, June 08, 2012 5:08 AM
  • That may be what I have run into as well. I installed MDS 2012 on a web server, with no other 2012 components, and pointed it to a database server elsewhere. I will try the above workaround.

    Or there could be a 2012 setup problem, could be that when you install 2012 with just MDS the sqlboot.dll is the wrong copy. Maybe if you install MDS + other features of SQL 2012 that problem doesn't happen. (most people have multiple features I suspect). If you find this is a bug by further testing, let me know so we can investigate.


    -Megan

    Saturday, June 09, 2012 4:48 AM
  • That may be what I have run into as well. I installed MDS 2012 on a web server, with no other 2012 components, and pointed it to a database server elsewhere. I will try the above workaround.

    Or there could be a 2012 setup problem, could be that when you install 2012 with just MDS the sqlboot.dll is the wrong copy. Maybe if you install MDS + other features of SQL 2012 that problem doesn't happen. (most people have multiple features I suspect). If you find this is a bug by further testing, let me know so we can investigate.


    -Megan

    Sure enough, copying sqlboot.dll from the x86 Program Files directory fixed it for me too.

    As an aside, I have encountered a variety problems trying to bring up MDS 2012 (Developer Edition) for initial evaluation. In re-installing and trying again (and again) in various configurations, sometimes web.config was missing permissions. Once there were no IIS authentication settings for the IIS site. Sometimes the IIS site was created in a stopped state. It's been a struggle. I have recorded some of this on my blog.


    -Megan

    Saturday, June 09, 2012 5:16 AM
  • The problem returned after installing CU2. Same workaround -- copy sqlboot.dll from x86 directory (and reboot).

    -Megan

    • Marked as answer by Madve Thursday, June 28, 2012 7:29 PM
    Friday, June 22, 2012 4:58 PM
  • Can you please review the text .log files in your setup log folder and tell me which MSIs have mention of this sqlboot.dll.

    C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\<Date>\

    We tried to reproduce this problem in the lab, and it did not happen, so something is happening we haven't been able to pin down.

    If you want you can attach the logs, or find all the the spots where sqlboot is touched in the setup logs.

    Thanks, Jason


    Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance

    Saturday, June 23, 2012 2:44 AM
  • Using a file content search, I found sqlboot.dll referenced in one .log file: SqlSupport_Cpu64_1.log (in the _SHARED_ subdirectory). It appears a number of times in that file.

    I can provide you with the file(s) if that would help. The above file is about 12 Mb, and the entire log directory is about 45 Mb.


    -Megan

    Saturday, June 23, 2012 6:52 AM
  • Yes, please share. If you want to mask the account names and server names feel free.  Skydrive works, or drop box.


    Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance

    Friday, June 29, 2012 4:21 AM
  • The problem returned after installing CU3. Same workaround -- copy sqlboot.dll from x86 directory (and reboot).

    New problem after this workaround:

    I have Microsoft SQL Server Enterprise (64-bit) version 11.0.2332.0 on Microsoft Windows NT 6.1 (7601) and I tried to copy a database with Tasks / Copy database... and it was not succesful because the SSIS task was not able to run:

    Event Name: OnError

     Message: Integration Services evaluation period has expired.

    :-@

    Any idea?


    Tuesday, October 02, 2012 6:22 PM
  • I have this exact issue.  However, doing the DLL copy switcheroo does not solve the problem for me. 

    Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com

    Monday, February 11, 2013 7:45 PM
  • I have this exact issue.  However, doing the DLL copy switcheroo does not solve the problem for me. 

    Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com

    I seem to have avoided further problems when I installed my production instance by including the DB engine on the VM where I installed MDS, and installing MDS in the root/default website rather than as its own site. I also went from IIS 7.0 to IIS 7.5.

    I don't know what made the difference but things work much better now, and some of the asynchronous features of the MDS website began working for the first time. Some of my speculations about what happened can be found here.


    -Megan

    Monday, February 11, 2013 7:59 PM