- Remove From My Forums
-
Question
All replies
-
Log file: C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20150502_090151sql_engine_core_inst_Cpu64_1.log
First you should check that mentioned log file to get more informations about the issue.
Olaf Helper
[ Blog] [ Xing] [ MVP]
-
What type of upgrade you are trying to do inplace upgrade or side by side ? I guess you are trying to do inplace upgrade
Did you ran SQL Server 2014 upgrade advisor. I guess upgrade advisor is facing breaking changes that is why it is unable to proceed. Please run upgrade advisor and see if it points out to any breaking changes
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
-
Correct we are trying to do an in place upgrade. The only error the upgrade adviser returns has to deal with «User Defined CLR objects that may function differently when the database compatibility level is raised to 110»
-
I’m not finding a lot more information in the log file but will keep looking. I receive the following errors during the up grade process. Not sure if this will be helpful or not.
1. CalculateAgentStaticSettingsAcount: «Exception has been thrown by the target of an invocation.»
2. GetPrimaryNodeForUpgrade: The document specified by its root path ‘/Extension/Agent/AgentPreviousRegPath’ does not exist in data store
3. Insall_sql_engine_core_inst_Cpu64_Action: Sqlmsirc_notifyFeaturesStates_64. «there was an error attemption to remove the configuration of the product which prevents any other action from occurring. The current configurations of the product
is being cancelled as a result.» -
Did you run upgrade advisor(UG) ? what did it suggested. Dont proceed before running UG
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
-
I did install and run the upgrade advisor. The only error I received was the following: «User Defined CLR objects that may function differently when the database compatibility level is raised to 110»
-
I did install and run the upgrade advisor. The only error I received was the following: «User Defined CLR objects that may function differently when the database compatibility level is raised to 110»
This is the error which is breaking the upgrade you need to refer to below article
Breaking Changes to Database Engine Features in SQL Server 2014
Please search for CLR. It would also be better if you post this in forum related to SQLCLR. I am not experienced with it
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
-
I cleaned up the CLR errors, re-ran the upgrade advisor and it came back clean without any errors. Ran the upgrade and received the same errors as before? I will review the logs and see if I can decipher what the issues might be. any
suggestion will be most appreciated. -
Hello,
Please run the following statements on SQL Server Management Studio:sp_configure
‘allow updates’, 0GO
RECONFIGURE
GO
Hope this helps.Regards,
Alberto Morillo
SQLCoffee.com-
Edited by
Tuesday, May 5, 2015 3:26 AM
-
Edited by
-
Thanks Alberto,
When I ran the above statement I got the following: «Configurations Option ‘allow updates’ changed from 0 to 0. Run the reconfigure statement to install» Does this mean that the allow updates value was already set to 0 so
nothing was changed?Thanks Phil
-
Hello,
Yes, it was already set top zero.
Regards,
Alberto Morillo
SQLCoffee.com -
I am having same CLR errors..can you tell me how did you cleaned up those?
-
did you guys found the solution for those CLR errors?
I am experience same problem now trying to upgrade 2008 R2 to 2014..#
Thanks,
mel
The title is the message I keep getting when I try to install the update.
«TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
A failure was detected for a previous installation, patch, or repair for instance ‘SQLEXPRESS’ during configuration for features [RS_Server_Adv,]. In order to apply this patch package (KB968369), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.»
I have tried numerous things others on the net have said they have done to get this to work. Like go in to regedit and rename PendingFileOperation to deleting all logitech drivers. I tried running repair in Sql Server but it wants me to pick an instance to repair and I cant find one on my computer since I havent used it yet because I have been trying to get this update to take. I am at the end of my rope with this. According to Sql Server there arent any «issues with the previous operation that failed» I dont know what to do. Please help.
- Remove From My Forums
-
Question
All replies
-
Log file: C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20150502_090151sql_engine_core_inst_Cpu64_1.log
First you should check that mentioned log file to get more informations about the issue.
Olaf Helper
[ Blog] [ Xing] [ MVP]
-
What type of upgrade you are trying to do inplace upgrade or side by side ? I guess you are trying to do inplace upgrade
Did you ran SQL Server 2014 upgrade advisor. I guess upgrade advisor is facing breaking changes that is why it is unable to proceed. Please run upgrade advisor and see if it points out to any breaking changes
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
-
Correct we are trying to do an in place upgrade. The only error the upgrade adviser returns has to deal with «User Defined CLR objects that may function differently when the database compatibility level is raised to 110»
-
I’m not finding a lot more information in the log file but will keep looking. I receive the following errors during the up grade process. Not sure if this will be helpful or not.
1. CalculateAgentStaticSettingsAcount: «Exception has been thrown by the target of an invocation.»
2. GetPrimaryNodeForUpgrade: The document specified by its root path ‘/Extension/Agent/AgentPreviousRegPath’ does not exist in data store
3. Insall_sql_engine_core_inst_Cpu64_Action: Sqlmsirc_notifyFeaturesStates_64. «there was an error attemption to remove the configuration of the product which prevents any other action from occurring. The current configurations of the product
is being cancelled as a result.» -
Did you run upgrade advisor(UG) ? what did it suggested. Dont proceed before running UG
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
-
I did install and run the upgrade advisor. The only error I received was the following: «User Defined CLR objects that may function differently when the database compatibility level is raised to 110»
-
I did install and run the upgrade advisor. The only error I received was the following: «User Defined CLR objects that may function differently when the database compatibility level is raised to 110»
This is the error which is breaking the upgrade you need to refer to below article
Breaking Changes to Database Engine Features in SQL Server 2014
Please search for CLR. It would also be better if you post this in forum related to SQLCLR. I am not experienced with it
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
-
I cleaned up the CLR errors, re-ran the upgrade advisor and it came back clean without any errors. Ran the upgrade and received the same errors as before? I will review the logs and see if I can decipher what the issues might be. any
suggestion will be most appreciated. -
Hello,
Please run the following statements on SQL Server Management Studio:sp_configure
‘allow updates’, 0GO
RECONFIGURE
GO
Hope this helps.Regards,
Alberto Morillo
SQLCoffee.com-
Edited by
Tuesday, May 5, 2015 3:26 AM
-
Edited by
-
Thanks Alberto,
When I ran the above statement I got the following: «Configurations Option ‘allow updates’ changed from 0 to 0. Run the reconfigure statement to install» Does this mean that the allow updates value was already set to 0 so
nothing was changed?Thanks Phil
-
Hello,
Yes, it was already set top zero.
Regards,
Alberto Morillo
SQLCoffee.com -
I am having same CLR errors..can you tell me how did you cleaned up those?
-
did you guys found the solution for those CLR errors?
I am experience same problem now trying to upgrade 2008 R2 to 2014..#
Thanks,
mel
- Remove From My Forums
-
Question
All replies
-
Log file: C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20150502_090151sql_engine_core_inst_Cpu64_1.log
First you should check that mentioned log file to get more informations about the issue.
Olaf Helper
[ Blog] [ Xing] [ MVP]
-
What type of upgrade you are trying to do inplace upgrade or side by side ? I guess you are trying to do inplace upgrade
Did you ran SQL Server 2014 upgrade advisor. I guess upgrade advisor is facing breaking changes that is why it is unable to proceed. Please run upgrade advisor and see if it points out to any breaking changes
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
-
Correct we are trying to do an in place upgrade. The only error the upgrade adviser returns has to deal with «User Defined CLR objects that may function differently when the database compatibility level is raised to 110»
-
I’m not finding a lot more information in the log file but will keep looking. I receive the following errors during the up grade process. Not sure if this will be helpful or not.
1. CalculateAgentStaticSettingsAcount: «Exception has been thrown by the target of an invocation.»
2. GetPrimaryNodeForUpgrade: The document specified by its root path ‘/Extension/Agent/AgentPreviousRegPath’ does not exist in data store
3. Insall_sql_engine_core_inst_Cpu64_Action: Sqlmsirc_notifyFeaturesStates_64. «there was an error attemption to remove the configuration of the product which prevents any other action from occurring. The current configurations of the product
is being cancelled as a result.» -
Did you run upgrade advisor(UG) ? what did it suggested. Dont proceed before running UG
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
-
I did install and run the upgrade advisor. The only error I received was the following: «User Defined CLR objects that may function differently when the database compatibility level is raised to 110»
-
I did install and run the upgrade advisor. The only error I received was the following: «User Defined CLR objects that may function differently when the database compatibility level is raised to 110»
This is the error which is breaking the upgrade you need to refer to below article
Breaking Changes to Database Engine Features in SQL Server 2014
Please search for CLR. It would also be better if you post this in forum related to SQLCLR. I am not experienced with it
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP
-
I cleaned up the CLR errors, re-ran the upgrade advisor and it came back clean without any errors. Ran the upgrade and received the same errors as before? I will review the logs and see if I can decipher what the issues might be. any
suggestion will be most appreciated. -
Hello,
Please run the following statements on SQL Server Management Studio:sp_configure
‘allow updates’, 0GO
RECONFIGURE
GO
Hope this helps.Regards,
Alberto Morillo
SQLCoffee.com-
Edited by
Tuesday, May 5, 2015 3:26 AM
-
Edited by
-
Thanks Alberto,
When I ran the above statement I got the following: «Configurations Option ‘allow updates’ changed from 0 to 0. Run the reconfigure statement to install» Does this mean that the allow updates value was already set to 0 so
nothing was changed?Thanks Phil
-
Hello,
Yes, it was already set top zero.
Regards,
Alberto Morillo
SQLCoffee.com -
I am having same CLR errors..can you tell me how did you cleaned up those?
-
did you guys found the solution for those CLR errors?
I am experience same problem now trying to upgrade 2008 R2 to 2014..#
Thanks,
mel
January 30, 2017 at 9:33 am
#318248
We are using SQL Server 2014 and I am getting the error
«SQL Server Setup has encountered the following error:
The NT Service ‘MSSQL$instancname’ could not be started.
Error Code 0x84B20001″
This error occures after the installation of a Service Packs or Cumulative Update. Also I do not get the message «Installation Completed’ that I would normaly get from SQL once a task completes
the instance comes up fine and all testing is normal.
Any help is appreciated.
Jeff
John Mitchell-245523
SSC Guru
Points: 148790
jayoub — Monday, January 30, 2017 9:33 AM
We are using SQL Server 2014 and I am getting the error
«SQL Server Setup has encountered the following error:
The NT Service ‘MSSQL$instancname’ could not be started.
Error Code 0x84B20001″This error occures after the installation of a Service Packs or Cumulative Update. Also I do not get the message «Installation Completed’ that I would normaly get from SQL once a task completes
the instance comes up fine and all testing is normal.
Any help is appreciated.
Jeff
Check out the log files for more information. C:Program FilesMicrosoft SQL Server120Setup BootstrapLog
John
Eirikur Eiriksson
SSC Guru
Points: 182833
IIRC, there was a connect item for this error for 2008 SP1, had to do with a registry key «ConfigurationState»
😎
jayoub
SSCertifiable
Points: 6988
Thank you very much for the reply. I looked in the folder and looked at the Detail.txt file — hope that was the correct one — it did give me lots of detail. MSSQL$InstanceName is the virtual Service account and I found, in short, the following errors. Any feedback is appreciated.
Restoring the following NT service to a running state after patch action: MSSQL$InstanceName
Slp: Sco: Attempting to start service MSSQL$InstanceName
Slp: Sco: Attempting to start service MSSQL$InstanceName, start parameters
Slp: Sco: Attempting to start service MSSQL$InstanceName
Slp: Sco: Attempting to open SC Manager
Slp: Sco: Attempting to open service handle for service MSSQL$InstanceName
Slp: Sco: Service MSSQL$InstanceName already running or pending start
Slp: Sco: Attempting to close service handle for service MSSQL$InstanceName
Slp: Waiting for nt event GlobalsqlserverRecComplete$InstanceName to be created
Slp: Waiting for nt event GlobalsqlserverRecComplete$InstanceName or sql process handle to be signaled
Slp: Error: Failed to start the following NT service after patch action: MSSQL$InstanceName
Slp: Sleeping 10 seconds before retrying NT service start request
Sco: Attempting to open service handle for service MSSQL$InstanceName
Slp: Invoking QueryServiceStatusEx Win32 API
Slp: Sco: Attempting to close service handle for service MSSQL$InstanceName
Slp: Sco: Attempting to close SC Manager
Slp: Sco: Returning service process id 7204
Error: Action «Microsoft.SqlServer.Configuration.SetupExtension.RunPatchAllInstanceAction» threw an exception during execution.
Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: The NT service ‘MSSQL$InstanceName’ could
not be started. —> Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException: The NT service
‘MSSQL$InstanceName’ could not be started.
Slp: at Microsoft.SqlServer.Configuration.SetupExtension.RunPatchAllInstanceAction.RestoreServiceStates()
at Microsoft.SqlServer.Configuration.SetupExtension.RunPatchAllInstanceAction.ExecuteAction(String actionId)
Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker
workerDelegate)
Slp: — End of inner exception stack trace —
Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException
Slp: Message:
Slp: The NT service ‘MSSQL$InstanceName’ could not be started.
Slp: HResult : 0x84b20001
Slp: FacilityCode : 1202 (4b2)
Slp: ErrorCode : 1 (0001)
Slp: Stack:
Slp: at Microsoft.SqlServer.Configuration.SetupExtension.RunPatchAllInstanceAction.RestoreServiceStates()
Slp: at Microsoft.SqlServer.Configuration.SetupExtension.RunPatchAllInstanceAction.ExecuteAction(String
actionId)
Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
Slp: at
Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker
workerDelegate)
Slp: Watson Bucket 2
Original Parameter Values
Jeff
Sue_H
SSC Guru
Points: 90860
Eirikur Eiriksson — Monday, January 30, 2017 10:06 AM
IIRC, there was a connect item for this error for 2008 SP1, had to do with a registry key «ConfigurationState»
😎
Yup…seems to be the same issue. Here is the connect item:
SQL 2008 SP1 Fails with error code 0x84B20001
The workaround section has the registry settings for configuration values that others have changed to address the issue.
Sue
jayoub
SSCertifiable
Points: 6988
Thanks. I checked it out and its for 2008. Would the same apply for SQL 2014?
Jeff
Sue_H
SSC Guru
Points: 90860
jayoub — Monday, January 30, 2017 1:01 PM
Thanks. I checked it out and its for 2008. Would the same apply for SQL 2014?
Not sure — I noticed it wasn’t fixed though. I looked around and just saw it up to 2012.
Nonetheless it’s probably worth taking a look at the registry keys to see if they are set to 0.
Sue
Ask a Question
All Questions
All Unanswered
FAQ
Please Sign up or sign in
to vote.
0.00/5 (No votes)
See more:
SQL
i have windows server 2008 R2 Standard
with no service pack
what should i do in order to install sql server 2014 on this operating system
Posted 27-Dec-14 0:49am
oula alsheikh
Add a Solution
1 solution
Please Sign up or sign in
to vote.
Solution 1
As long as it’s the 64 bit version and you update it to SP1 then MS says it shouldn’t be a problem (assuming your hardware meets their minimum specifications): http://msdn.microsoft.com/en-us/library/ms143506.aspx[^]
Permalink
Share this answer
Posted 27-Dec-14 1:06am
OriginalGriff
Comments
oula alsheikh
29-Dec-14 5:36am
i installed sp1 on windows server 2008
and run sql server but i encountered the following error
Error Code 0x84B20001
The action type ‘ExecuteWorkflowAction’ is not valid for the
WorkflowIdentity elemnt .The only valid action type is ExecuteWorkflowAction
what to Do?
Add a Solution
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
| Top Experts | |||||||||||||||||||||
| Last 24hrs | This month | ||||||||||||||||||||
|
|
Related Questions
Sql Server 2014 installation error
Wanted to uninstall SQL server 2008r2 and install SQL server 2014 inplace
installing sql express 2014 on windows 8
Failed to install mysql server 8.0.18 on windows 7 (64bit)
Error in installing SQL server 2014 express local-db
Unable to install SQL server management studio express
Facing issue in Installing Sql Server 2014
Install SQL server 2019, express edition on windows 10 problem
Sql server 2014: 1 row update is very slow
Sql server 2014 eating the RAM
Advertise
Privacy
Cookies
Terms of Use
Last Updated 27 Dec 2014
Layout: fixed
|
fluid
Copyright © CodeProject, 1999-2023
All Rights Reserved.
Web03
2.8:2023-01-23:1
CodeProject,
20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8
+1 (416) 849-8900
Содержание
- 0x84b20001 sql server setup
- SQL Server Setup Error code 0x84B20001.
- 0x84b20001 sql server setup
- Answered by:
- Question
- 0x84b20001 sql server setup
- Answered by:
- Question
- 0x84b20001 sql server setup
- Answered by:
- Question
- Answers
- All replies
0x84b20001 sql server setup
SQL Server Setup Error code 0x84B20001.
Applies to: Microsoft SQL Server 2012 Enterprise Core SP1.
When trying to install SQL Server Enterprise Core 2012 SP1 on Windows Server 2012 (Standard) from a ISO image, the user received the following error message during installation of the setup files:
SQL Server Setup has encountered the following error:
The patch file cannot be opened. The file is: E:PCUSOURCEx64setupsql_engine_core_inst_msisql_engine_core_inst.msp.
Error code 0x84B20001
Try to copy the ISO file to the hard drive, uncompress the ISO image using WinRAR, and then run SQL Server setup from the disk drive. If with WinRAR did not work, try using 7zip and WinZip also.
If uncompressing the ISO image in your computer hard drive and running setup from there was not successful, then there’s a possibility the ISO file is corrupted. Please try to download the ISO image again and verify the size of the ISO is the size listed on Microsoft download Web site.
Источник
0x84b20001 sql server setup
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I recently tried installing SQL Server Express 2012 on my computer. Its a new computer running Windows 8 and Visual Studio 2008 and 2010 are also installed. The installer will get most of the way through the installation and then will stuck indefinitely. If I right click on the installer on the task and then select «Managed SQL Server Installer«, then this error message appears:
SQL Server Setup has encountered the following error:
SQL Server 2012 ScenarioEngine.exe and setuppatch.exe cannot be run in this mode. If you are running ScenarioEngine.exe, start setup.exe instead. If you are running setuppatch.exe, run it from the command prompt, as the user interface is not supported for this action. For more information about Setup, see SQL Server Books Online.
Error code 0x84B20001.
I tried canceling out of the install but it couldn’t do this either so I had to force it to shutdown.
I zipped and posted the install log directory to here
So my questions are:
1. The fact that the installer wasn’t able to back out of the installer properly makes me wonder if there is garbage half install that is now my computer. Is there any potential problems from the botched install and how is this determined, and how do I go about cleaning it up properly?
2. The error message tells you to run the installer from command prompt. Is this really the solution to this problem? Would running «SQLEXPRWT_x64_ENU» from command prompt be sufficient or is there more to it than this?
Источник
0x84b20001 sql server setup
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I recently tried installing SQL Server Express 2012 on my computer. Its a new computer running Windows 8 and Visual Studio 2008 and 2010 are also installed. The installer will get most of the way through the installation and then will stuck indefinitely. If I right click on the installer on the task and then select «Managed SQL Server Installer«, then this error message appears:
SQL Server Setup has encountered the following error:
SQL Server 2012 ScenarioEngine.exe and setuppatch.exe cannot be run in this mode. If you are running ScenarioEngine.exe, start setup.exe instead. If you are running setuppatch.exe, run it from the command prompt, as the user interface is not supported for this action. For more information about Setup, see SQL Server Books Online.
Error code 0x84B20001.
I tried canceling out of the install but it couldn’t do this either so I had to force it to shutdown.
I zipped and posted the install log directory to here
So my questions are:
1. The fact that the installer wasn’t able to back out of the installer properly makes me wonder if there is garbage half install that is now my computer. Is there any potential problems from the botched install and how is this determined, and how do I go about cleaning it up properly?
2. The error message tells you to run the installer from command prompt. Is this really the solution to this problem? Would running «SQLEXPRWT_x64_ENU» from command prompt be sufficient or is there more to it than this?
Источник
0x84b20001 sql server setup
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I am having problem to install security update for SQL Server 2012 (64-bit) on Windows 8 (64-bit) OS.
I got error code 84B20001 while installation. After further investigation, in event log I found message as below-
«FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified) occurred while creating or opening file ‘e:sql10_main_tsqlmkmastrdatabasesobjfrei386MSDBLog.ldf’ Diagnose and correct the operating system error, and retry the operation.»
- I have not installed SQL Server on this location, I gone through recommended steps for installation.
- I have tried all the possible solutions found on web (including RebuildDatabase also), but nothing seemed to work .
- I have checked all permissions to access the database and those are all enough.
- I have more than 100GB space on C:, D: and E: drive, hence less disk space issue shouldn’t come.
- Also, I failed to start SQL Express service from service manager (SQL Server Configuration).
- Under «%systemroot%SoftwareDistribution» directory in the log file, I found message as below-
«AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for SQL Server 2012 RTM (KB27164442).»
Appreciate the help.
Answers
Does that “e:” drive exist? Does “e:sql10_main_tsqlmkmastrdatabasesobjfrei386” exist?
Hope this helps.
The default path is usually the Program Files folder on the System drive, so it makes think the default path was changed during installation.
However, do not worry about this, please move the files to the path I posted above to be able to start SQL Server and apply the update. After that change their location using the following article:
Hope this helps.
Would you please share/upload SQL Server setup logs ?
to share/locate SQL Server setup logs, please check-out below «FAQ»
FAQ
—-
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided «AS IS» with no warranties, and confers no rights. Please remember to click «Mark as Answer» and «Vote as Helpful» on posts that help you.
This can be beneficial to other community members reading the thread.
There is a same issue on the following blog, please refer to the solution there:
Allen Li
TechNet Community Support
Here is the log-
Starting up database ‘model’.
2012-11-19 18:41:13.06 spid9s Error: 17204, Severity: 16, State: 1.
2012-11-19 18:41:13.06 spid9s FCB::Open failed: Could not open file e:sql10_main_tsqlmkmastrdatabasesobjfrei386model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2012-11-19 18:41:13.17 spid9s Error: 5120, Severity: 16, State: 101.
2012-11-19 18:41:13.17 spid9s Unable to open the physical file «e:sql10_main_tsqlmkmastrdatabasesobjfrei386model.mdf». Operating system error 3: «3(The system cannot find the path specified.)».
2012-11-19 18:41:13.20 spid7s Informational: No full-text supported languages found.
2012-11-19 18:41:13.49 spid7s Starting up database ‘msdb’.
2012-11-19 18:41:13.49 spid9s Error: 17207, Severity: 16, State: 1.
2012-11-19 18:41:13.49 spid9s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file ‘e:sql10_main_tsqlmkmastrdatabasesobjfrei386modellog.ldf’. Diagnose and correct the operating system error, and retry the operation.
2012-11-19 18:41:13.50 spid9s File activation failure. The physical file name «e:sql10_main_tsqlmkmastrdatabasesobjfrei386modellog.ldf» may be incorrect.
2012-11-19 18:41:13.60 spid9s Error: 945, Severity: 14, State: 2.
2012-11-19 18:41:13.60 spid9s Database ‘model’ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2012-11-19 18:41:13.73 spid9s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2012-11-19 18:41:13.76 spid7s Error: 17204, Severity: 16, State: 1.
2012-11-19 18:41:13.76 spid7s FCB::Open failed: Could not open file e:sql10_main_tsqlmkmastrdatabasesobjfrei386MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2012-11-19 18:41:13.88 spid9s SQL Trace was stopped due to server shutdown. Trace . This is an informational message only; no user action is required.
2012-11-19 18:41:13.88 spid7s Error: 5120, Severity: 16, State: 101.
2012-11-19 18:41:13.88 spid7s Unable to open the physical file «e:sql10_main_tsqlmkmastrdatabasesobjfrei386MSDBData.mdf». Operating system error 3: «3(The system cannot find the path specified.)».
2012-11-19 18:41:14.00 Server A self-generated certificate was successfully loaded for encryption.
2012-11-19 18:41:14.04 Server Server local connection provider is ready to accept connection on [ \.pipeSQLLocalSQLEXPRESS ].
2012-11-19 18:41:14.08 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
Cannot close event log because there are still event handle users active.
Please let me know if you need more information.
Sorry to say, but it doesn’t worked for me. Anyway thanks.
Источник