I have a clustered server environment with win2k3 64 and sqlserver 2008 r2 sp1. there are 4 instances in the cluster. I choose to upgrade only one instance to sp2 and during the upgrade, all the instances are restarted, which is not desirable. how to prevent this from happening

I have encountered an extremely strange problem. I try to install a named instance of SQL Server 2005 on single node of a Windows Server 2008 R2 cluster two node cluster. I have selected collation as THAI_CI_AS during installation but after the installation is completed, the database has  was installed SQL_Latin1_General_CP1_CI_AS. The set up command is like this:

USERNAME=XXXX COMPANYNAME=XXXX PIDKEY=********** INSTALLSQLSHAREDDIR=C:\Program Files\Microsoft SQL Server\ INSTANCENAME=SQLSERVER2 INSTALLSQLDIR=C:\Program Files\Microsoft SQL Server\ VS=VS1 IP=133.5.5.44,Cluster Network 1 GROUP=SQL2 ADDNODE=CN1 INSTALLVS=SQL_Engine INSTALLSQLDATADIR=K:\Microsoft SQL Server\ SECURITYMODE=SQL SAPWD=********** SQLCOLLATION=Thai_CI_AS SQLACCOUNT=XXDC\XXXX-SQL SQLPASSWORD=********** SQLAUTOSTART=0 AGTACCOUNT=XXDC\XXXX-SQL AGTPASSWORD=********** AGTAUTOSTART=0 ENABLERANU=1 SQLCLUSTERGROUP=XXDC\SQL Server 2005 Cluster Service-S-G AGTCLUSTERGROUP=XXDC\SQL Server 2005 Cluster Service-S-G FTSCLUSTERGROUP=XXDC\SQL Server 2005 Cluster Service-S-G STPSETUPTHREADID=3268 STPSETUPPROCESSID=4064 EXTERNALCONTROL=1 CLUSTER=1 CLUSTERSEC=0 ADDLOCAL=SQL_Engine,SQL_Data_Files,SQL_Replication,SQL_FullText,SQL_SharedTools,SQL_BC_DEP TRANSFORMS=:SqlRun02.mst;:InstID02.mst;:InstName02.mst

Hi all,

I'm evaluating the correct edition of SQL Server to buy, I'm not sure between "Standard" and "Business Intelligence".

Can I start with the "standard" edition and then upgrade to "business intelligence"? I think yes, my question is:

is there any disruption of service when I perform the edition upgrade?

Hey everyone, alright so I have been beating my head on this one for a few days and I'm at a loss. I've been working on installing SQL Server 2012 SP1 on Windows Server 2012 using "best practices" as much as I can. I've been able to get it to install with all default settings, but when I start modifying the installation configuration I begin to run into problems.

Upfront here is a link to my Install Detail Log: Detail Install Log

A description of the "environment" I am attempting to install it to.

• It's a VMware virtual server.
• Running Windows Server 2012 Datacenter 64bit
• I have it currently configured with 16GB of ram and 8 cores (is intended to end up being a SQL server for a Sharepoint 2013 installation).
• SQL Server 2012 Developer Edition 64bit with SP1
• I'm installing only the Database Engine Services with SQL Server Replication and Full-Text and Semantic Search options + the Management tools
• Running on a Windows Domain that is set at 2008R2 for Forest and Domain
• Using an Enterprise and Domain Admin account for the installation also launching the setup with "Run as Administrator" the Domains "Domain Admin" group is added to the Local Administrator group on the local machine

That's the base, as I said if I install everything default, it works. Once I start making changes things start going south. Here is what I am attempting to do with varying degrees of success.

• Database Engine and Agent are using Managed Service Accounts, both accounts have been created, associated with the computer object in AD, and "installed" on the local machine I have also manually granted the readServicePrincipalName and writeServicePrincipalName permissions in AD (don't really know if this is necessary anymore, but I'm trying to be thorough to figure out what is missing)
• I've created the following drive structure on the server: Local Disk (C:), Programs (P:), SQL (S:), Data (F:), Logs (L:), TempDB (T:), Backup (B:) the intention is to install the binaries to P:, the instance files and data root directory to S:, user data files to F:, user logs to L:, TempDB and Logs to T: and backup to B: (open to changing it upon recommendation, this is based on my best effort to figure out a clear installation base). These are all separate VMware virtual hard disks added to the machine.
• Regarding folder/drive permissions I have largely tracked with: http://sqlblog.com/blogs/jonathan_kehayias/archive/2010/03/22/sql-server-installation-checklist.aspx regarding individual drive permissions to be more exact, my MSA has Full Control of: B:\, P:\ and S:\; List Folder Contents of: L:\, F:\ and T:\ and Full Control of folders at the root of L:\, F:\ and T:\
• I'm utilizing only Windows Authentication for the installation adding my domains SQLDBAs group (of which the account I'm using to install is a member)

When doing this everything seems to work up until the installation gets to: SqlEngineDBStartConfigAction_install_configrc_Cpu64 then it hangs for a minute before giving me an "Attempted to perform an unauthorized operation"

Here is the relevant section from the detail log:

(01) 2012-12-04 14:07:03 SQLEngine: --SqlServerStartup: SQLEngine: Slipstream case: Enable traceflag -T902
(01) 2012-12-04 14:07:03 SQLEngine: : Checking Engine checkpoint 'StartEngineService'
(01) 2012-12-04 14:07:03 SQLEngine: --SqlServerServiceSCM: Starting SQL via SCM (-mSqlSetup -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T4010 -T3659 -T3610 -T8015 -T902)... 
(01) 2012-12-04 14:07:03 Slp: Sco: Attempting to start service MSSQL$MOSS2013SQL
(01) 2012-12-04 14:07:03 Slp: Sco: Attempting to open SC Manager
(01) 2012-12-04 14:07:03 Slp: Sco: Attempting to open service handle for service MSSQL$MOSS2013SQL
(01) 2012-12-04 14:07:04 Slp: Prompting user if they want to retry this action due to the following failure:
(01) 2012-12-04 14:07:04 Slp: ----------------------------------------
(01) 2012-12-04 14:07:04 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2012-12-04 14:07:04 Slp: Inner exceptions are being indented
(01) 2012-12-04 14:07:04 Slp: 
(01) 2012-12-04 14:07:04 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2012-12-04 14:07:04 Slp:     Message: 
(01) 2012-12-04 14:07:04 Slp:         Attempted to perform an unauthorized operation.
(01) 2012-12-04 14:07:04 Slp:     HResult : 0x84bb0001
(01) 2012-12-04 14:07:04 Slp:         FacilityCode : 1211 (4bb)
(01) 2012-12-04 14:07:04 Slp:         ErrorCode : 1 (0001)
(01) 2012-12-04 14:07:04 Slp:     Data: 
(01) 2012-12-04 14:07:04 Slp:       WatsonData = MSSQL$MOSS2013SQL
(01) 2012-12-04 14:07:04 Slp:       DisableRetry = true
(01) 2012-12-04 14:07:04 Slp:     Inner exception type: System.UnauthorizedAccessException
(01) 2012-12-04 14:07:04 Slp:         Message: 
(01) 2012-12-04 14:07:04 Slp:                 Attempted to perform an unauthorized operation.
(01) 2012-12-04 14:07:04 Slp:         Stack: 
(01) 2012-12-04 14:07:04 Slp:                 at Microsoft.SqlServer.Configuration.Sco.Service.StartService(String[] startParams)
(01) 2012-12-04 14:07:04 Slp: ----------------------------------------
(01) 2012-12-05 06:58:23 Slp: User has chosen to retry this action
(01) 2012-12-05 06:58:23 Slp: Sco: Attempting to close service handle for service MSSQL$MOSS2013SQL
(01) 2012-12-05 06:58:23 Slp: Sco: Attempting to close SC Manager
(01) 2012-12-05 06:58:23 Slp: Sco: Attempting to open SC Manager
(01) 2012-12-05 06:58:23 Slp: Sco: Attempting to open service handle for service MSSQL$MOSS2013SQL
(01) 2012-12-05 06:58:23 Slp: Prompting user if they want to retry this action due to the following failure:
(01) 2012-12-05 06:58:23 Slp: ----------------------------------------
(01) 2012-12-05 06:58:23 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2012-12-05 06:58:23 Slp: Inner exceptions are being indented
(01) 2012-12-05 06:58:23 Slp: 
(01) 2012-12-05 06:58:23 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2012-12-05 06:58:23 Slp:     Message: 
(01) 2012-12-05 06:58:23 Slp:         Attempted to perform an unauthorized operation.
(01) 2012-12-05 06:58:23 Slp:     HResult : 0x84bb0001
(01) 2012-12-05 06:58:23 Slp:         FacilityCode : 1211 (4bb)
(01) 2012-12-05 06:58:23 Slp:         ErrorCode : 1 (0001)
(01) 2012-12-05 06:58:23 Slp:     Data: 
(01) 2012-12-05 06:58:23 Slp:       WatsonData = MSSQL$MOSS2013SQL
(01) 2012-12-05 06:58:23 Slp:       DisableRetry = true
(01) 2012-12-05 06:58:23 Slp:     Inner exception type: System.UnauthorizedAccessException
(01) 2012-12-05 06:58:23 Slp:         Message: 
(01) 2012-12-05 06:58:23 Slp:                 Attempted to perform an unauthorized operation.
(01) 2012-12-05 06:58:23 Slp:         Stack: 
(01) 2012-12-05 06:58:23 Slp:                 at Microsoft.SqlServer.Configuration.Sco.Service.StartService(String[] startParams)
(01) 2012-12-05 06:58:23 Slp: ----------------------------------------

I've ran procmon during a retry to see if I could figure out the permissions issue, I'm at a loss.

I have tried various things to resolve this with varying degrees of success. I've also gotten different errors (including "Could not find the Database Engine startup handle."). I have added my MSA to Local Administrators, didn't fix the problem. If I don't move some files around and leave it on C: I can sometimes get it to install or at least kick a different error.

Any thoughts, suggestions or ideas are welcome, if I missed some pertinent info let me know.

Thanks!

ADD: I selected cancel this time from the "Attempted to perform an unauthorized operation." error upon completion the final error for all Database Engine parts was: "Could not find the Database Engine startup handle." as I mentioned earlier. Here are links to an updated Detail Log: Detail and a Summary Log: Summary

Here is the relevant Summary info:

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0018
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024

  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0018
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0018
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024

I am trying to install SQL Server 2008 R2 on Windows Server 2008, i choosed SQL Server default feature installation. i am getting error at last stage of wizard...following is the description.. 

Description:
  Stopped working

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: setup100.exe
  Application Version: 10.50.1600.1
  Application Timestamp: 4bb6742c
  Fault Module Name: mscorwks.dll
  Fault Module Version: 2.0.50727.4200
  Fault Module Timestamp: 4a9ee32d
  Exception Code: c0000005
  Exception Offset: 00000000001870b3
  OS Version: 6.0.6002.2.2.0.274.10
  Locale ID: 16393

Please help me out i have tried the installation for several times..

hi there ,

when i try to install sql 2008 express on to my windows 7 home edition pc . i keep getting the following message

"Managed SQL ServerInstaller has stopped working..."

i read elsewhere that it might be a .net 4 issue but i have dont net 3.51 sp1 that comes with windows 7 ( turned off and on features )

can anyone advise ?

This appears to be more in SQL Server than in SharePoint Server(this is what I believe):

This is the message from failed SharePoint Server installation.

There is a dbwraplog file which reads as shown:(only part of it copied)

INF:0:Starting process C:\Program Files\Common Files\Microsoft Shared\SERVER14\Server Setup Controller\sqlexpr.exe with args  /q /HideConsole  /ACTION=install /pid=11111-00000-00000-00000-00000 /FEATURES=SQL,Tools /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /SQLSVCACCOUNT="NT AUTHORITY\Network Service" /INSTANCENAME=SharePoint /INSTALLSQLDATADIR="C:\Program Files\Microsoft Office Servers\14.0\Data" and waiting 00:49:10 for it to stop
ERR:-2068578304:Leaving function RunCommand

I do find the SQLexpr.exe in

C:\Program Files\Common Files\Microsoft Shared\SERVER14\Server Setup Controllerit not

Why does it not start?

I do see the MSSQL10.SharePoint in the directory
C:\Program Files\Microsoft Office Servers\14.0\Data

There are no other SQL Servers on the machine at present.

I do not have SSMS.

Any help will be appreciated.

mysorian

Hi all.

I'm having a problem running an in place upgrade of SQL Server 2005 x64 Enterprise to 2008 R2 Enterprise.

When I run setup.exe and choose "upgrade", I am able to upgrade all components apart from the database engine. I am not given the option to select an instance prior to this. I have ensured that "x64" is selected from the bottom "options" tab on the initial setup screen. My current installed version of SQL is definitely 2005 x64 Enterprise, I have checked this with @@version and in the general properties of the Management Studio.

The strange thing is that if I select "x86" from the bottoms tab in SQL setup I AM able to select the 2005 instance, which lists the database engine as something it will upgrade in the next screen. Obviously I have not proceeded with the upgrade as I feel something is wrong somewhere.

Does anyone have any ideas as to how I can get the x64 install to detect the 2005 instance and upgrade the database engine?

Thanks

hey all

i installed sql server 2008 when i installed the following error occur

also when i go in configuration manager there is empty in this

plz anyone can tell me about this problem?????

Hi,

I'm trying to add reporting services to an existing 2008 R2 instance as a pre-requisite for a fresh CRM 2011 installation. I figured out that the "Installation Type" page that allows adding features to an existing instance does not show up. This is an SQL Server 2008 R2 Enterprise installation and the Data-base Engine is up and running and being used by SharePoint. The OS is Windows Server 2008 R2 with all updates installed.

Tried to run setup "as administrator", but didn't help. Tried Add/Remove from control panel, but no difference. Seems that the setup routine does not recognize the instance initially. Is there any command line switch that forces the Installation Type page to appear?

I'd be thankful for any hints.

in install SQL SERVER 2008 R2

when i cereate a databse diagram

following error is coming

serach on google then i fcound go to database properties but i Cant find database properties in this

I keep getting this error when I try to install, repair or uninstall SQL 2012 which won't run because of another error? Here is the error.. 

sql server has encontoiured the following error: 

Could not load file or assembly \\\ C:/program files/microsoft/sql server/ 110 blah blah blah huge path / Microsoft.SQLserver.Configuration.Setup.Extension.DLL  Error Code 0x84b10001

I'm also not able to open SQL server management studio 2012. I have Management Studio 2008, but I need 2012 for my remote host which is using 2012. So, when I try with 2008 to open my db at the host, I get an error that I need 2012. This is driving me nuts.. 

I'm running Windows 7 Ultimate with 8gig of ram, solid state drive, on a lap top, latest updates, etc,. I also have VIsual Studio 2012 Pro, Webmatrix, and everything else works fine. Just this one damn SQL server Management studio that I need for it's visual tools to do relationships with, etc, and it doesn't work. Any help would be most appreciated.. I'm going to try to update SQL server again and the computer in general to see if that helps.. 

A search gives me a lot of stuff about 2008 sql, but nothing with the same error, so I'm afraid to try those solutions since they don't seem to be the same problem as I'm having!

Tim

Tim

Hello,

I'm shortly to be upgrading a SQL Server 2005 instance to SQL Server 2008 R2 on a Windows 2003 R2 box. Whilst following suggested practice I ran the Upgrade Advisor and got the following issue reported "

". This was for many commands such as DROPSYSOBJ, OUTPUTINTOFULLTEXT, OLDSYSTEMTABLES, DUMPLOAD, MERGE, ...

The status of these issues is critical and it is suggested that they be resolved prior to the upgrade, but I don't know what the issue means let alone how to resolve it. Can anyone shed any light on this for me please?

Mike

I am on SQL Server 2008 R2 on Windows 7. I want  to rebuild my master database (this is for learning) using

setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=PREMTESTCOMPUTE\pmehrotr /SAPWD=xxxxxxx

When I run this command, I get error:

 Final result:                  Failed: see details below
  Exit code (Decimal):           -2068643838
  Exit facility code:            1203
  Exit error code:               2
  Exit message:                  The state of your SQL Server installation was not changed after the setup execution. Please review the summary.txt logs for further details.

  Requested action:              RebuildDatabase

I have looked in various summary log files in   Setup Bootstrap \Log drcetory and I cannot find the roort cause as something missing, do not have premssions etc. In different files it shows the same exit message; so it is frustrating how to troubleshoot this problem. I have also looked in event viewer and no information related to this error.

My database instance MSSQLSERVER has several accounts with sysadmin role. I just sepcified one:

setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=PREMTESTCOMPUTE\pmehrotr /SAPWD=xxxxxxx

Hello all,

I am planning to try to move some SQL2005 and SQL2008 from a 2nodes (VMs) to another 2nodes (physical).

A. What I plan to do is :

1. add physical machines as 3rd and 4th node of Windows cluster and form a 4node Windows cluster

2. stop all scheduled user created jobs (backups etc.)

3. for each instance existing, run on 1st physical machine (3rd node) the "add node" for all existing SQL2005 and SQL2008 failover clustered instances (FCIs) and Service Packs

4. for each instance existing, run on 2nd physical machine (4th node) the "add node" for all existing SQL2005 and SQL2008 failover clustered instances (FCIs) and Service Packs

5. one-by-one, faiolover the instances from VMs to physical nodes and do all the ckecks for the health of the system. If ok run backups and continue failover the next one. If there is anything wrong failback check and retry.

6. Run backups, enable jobs

the tricky part is that the systems is a live system.

we plan to do the installations during non-maintenance window an do the failover inside maintenance window.

Is there anything causing the SQL Server to actually failover DURING sql setup of "add node"? (e.g.: cluster validation before addign to cluster)?

B. We have all kind if services to be installed, includingn SSAS, SSIS, SSRS and thye already exist in VMs in one resource group per instance. I guess that during each "add node" run per instance they are all going to be installed at once for this instance, right?

C. anything special we should be aware of?

thank you very much!

kind regards, Thomas G. Apostolou

We have an InstallShield installation package that spawns an installation of MS SQL Server 2008 R2, depending on what components the user selects to install. This has worked fine, but now we need to support Windows Server 2012 and Windows 8, so we want to distribute SP2 of SQL Server 2008 R2 Express Edition instead of the original SP1. The only difference made to the installation package is to replace the redistributable of SQL Server R2 Express Edition SP1 with SP2. If the SP1 version is used Windows 2012 and Windows 8 will popup a message saying that there is compatibility issues with that version of SQL Server. 

When the installation package use SQL SP2 the SQL Server installation starts, extracts files etc and and begins the installation, but then freezes at the step ExecuteStandardTimingsWorkflow displayed in the installer UI.
There is no significant CPU usage and no increase in memory by any process like msiexec or similar and there is no error message displayed.
It is not possible to cancel the installation either (cancel button disabled). Reviewing the SQL Server log files shows the following lines in the Detail_ComponentUpdate log

2012-08-23 08:33:06 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\9.0
2012-08-23 08:33:06 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
2012-08-23 08:33:06 Slp: Sco: Returning service status Running
2012-08-23 08:33:11 Slp: Sco: Returning service status Running
2012-08-23 08:33:16 Slp: Sco: Returning service status Running <- repeated indefintely until the installer is killed in task manager

When using SP1 the same log files says the following

2012-08-23 11:00:57 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\VisualStudio\9.0
2012-08-23 11:00:57 Slp: Sco: Waiting for service 'msiserver' to accept the stop request.
2012-08-23 11:00:57 Slp: Sco: Returning service status Stopped

The problems appears to be that the installer cannot shutdown the msiserver service and just loops indefinitely. 
The following conditions apply to all tested machines which is Windows 8, Windows Server 2012 RC, Windows Server 2008 R2 

Machine is clean, no existing versions of SQL Server exists prior to installation. All security updates etc. applied.

Logged in user is local administrator.

Installation is successful if the SP1 version of SQL Server 2012 is used instead of the SP2 version

The SP2 version can be installed successfully from the command prompt (run as administrator). In this case I use the following command 

line (replaced password with ****):
SQLEXPR_x86_ENU.exe /ACTION=install /INSTANCENAME=PRODACAPO /IACCEPTSQLSERVERLICENSETERMS /HIDECONSOLE /QUIETSIMPLE /SECURITYMODE=SQL /SAPWD=**** /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"

Display language is US English and SQL Server package is US English. Input/keyboard language is Swedish.

Windows Installer service cannot be shutdown from services as Stop and Restart options are disabled.

No summary.txt file is created when the installation freezes

Are there any changes in the behavior of the installation package from SP1 to SP2? Since SP1 works it seems that InstallShield cannot be blamed for this problem? However, installing from the command prompt works which means that the problem seem to lie in with how the SQL installation is spawned from InstallShield. Currently this problem is preventing us from supporting Windows Server 2012 and Windows 8 properly.
If you need any log files or other info I can provide that promptly.


Related problems for other users:
http://stackoverflow.com/questions/11741803/fail-to-install-sql-server-2008-r2-as-a-feature-pre-requisite-in-a-wix-project

http://social.msdn.microsoft.com/Forums/en-NZ/sqlsetupandupgrade/thread/ce69b4e1-939f-4a64-9b44-e6ffdad3b9c8
The SP2 redistributable I use can be downloaded from here (SQLEXPR_x86_ENU.exe):

http://www.microsoft.com/en-za/download/details.aspx?id=30438

Thanks

Fredrik

Frede

Hi Team,

Am unable to view  Databases for SQL Server 2000 in Enterprise Manager.

REquesting you all to help/advice me on the same, I am attaching my screenshot of the error message.