RTC Service already exists

We are currently trying to migrate from OCS 2007 R2 to Lync 2013.
Preparing the schema works fine and has been verified.
I'm erroring out on on Preparing the Forest.
I've found the same error in a few other places but haven't found a solution that works for me yet.
"Command execution failed: Active Directory operation failed on "DOMAINCONTROLLER". The object "CN=RTC Service,CN=Services,CN=Configuration,DC=DOMAIN,DC=com" already exists.

Hi Eason,
Thank you for replying, I had previously seen that case, my situation is different
I have the RTC Service items located in two locations currently.
1. Default Naming Context>CN=System>CN=Microsoft>CN=RTC Service
2. Configuration>CN=Services>CN=RTC Service
I also came across this post
https://social.technet.microsoft.com/Forums/lync/en-US/1ebc2962-bfeb-452b-ad07-09b015f6c82e/command-execution-failed-active-directory-operation-failed-on-dc2012abccom-the-object-cnrtc?forum=lyncdeploy
which was solved by
"Removed RTC Service from
1: CN=Configuration=CN=Services- RTC Service
2: default naming-Context-System-Micrososft-RTC Service"
My hesitancy here is that we are still using OCS 2007 R2 in production until after Lync 2013 is fully functional, I don't want to break OCS.

Similar Messages

How to deal with "Error 1001. The specified service already exists" when install a service using installer package?

Hi everybody,
I wrote a "Class Library" project which is a service using Visual Stodio 2008 recently, then tried to use a Visual Studio 2008
Setup Project to install it.
Here is what I did for the "Class Library":
1. Finish the program.cs, Service.cs
2. Add Installer
3. Change the serviceInstaller so that "StartType" to be Aotumatic
4. Change the ServiceProcessInstaller2 so that "Account" to be LocalSystem
5.
6. Click in F5 (Start Debugging)
Here is what I did for the Setup Project:
1. Add the exe file built from the "Class Library" project to the Application Folder
2. On the Custom Action Editor, add the exe file from 1 to Install and Commit
3. Change the property of the project so that "RemovePreviousVersion" to be true
4. Click on F6(Build Solution)
Then I tried to run the msi file from the built of the Setup Project. Because I modified the two projects serveral times, I uninstalled the Class Library using "Control Panel->Add or Remove Programs" before I reinstall. Two things I notived:
1. After unstall, the registry was not cleaned up about the installed program
2. After several rounds install/uninstall, I got "Error 1001. The specified service already exists"
My questions are:
1. How to cleanup the registry when uninstall a program?
2. How to deal with the "Error 1001. The specified service already exists"?
3. Did I do anytbing wrong with the "Class Library" or the "Setup Project"?
Thanks a lot!
Helen

Hi Simon, not a problem!
I spent some more time on this and here are few more notes:
it is called Major Upgrade, when you are installing new version of the product upon a previous one and
MSI supports 2 strategies:
Strategy 1. Install a new version and uninstall previous one. (Install a new version right upon previously installed version (file merging is performed based on dll version number) and the delete previously
installed files)
Strategy 2. Uninstall previous version and install a new one (Delete all previous files and install from scratch new files.)
From the first look it seems that 1st strategy is weird and buggy. But, remember, MSI is great because it's transactional!!! That means that if once some of the phases (Installation, Uninstallation, Rollback, Comit) fails, your machine
will be reverted to the previous state and it'll be still functional.
Let's consider both strategies:
Consider you have installed product_v1.msi and you want to install product_v2.msi.
Strategy 1
1. MSI engine copies files from Product_v1 directory to TEMP directory
2. MSI engine merges files based on the assembly version (between v1 and v2)
3. Once merging is completed successfully it removes files in TEMP (RemoveExistingProducts action triggers it) and you got product_v2 installed, otherwise if it fails MSI engine revert machine to V1 and copies previous files from TEMP.
Strategy 2
1. MSI engine tottaly removes all files from v1.
2. MSI engine installs v2 files and if something goes wrong you cannot revert back, because RemoveExistingProducts allready worked out and MSI doesn't have files to revert machine back
I recommend to everybody to use Strategy 1 and leverage MSI transaction functionality. And you can set this strategies by defining sequence of RemoveExistingProducts action. See more info
here. So, I think it's not even a bug in VS as I said in the upper post it is default recommened behaviour.
AND, you got "Error 1001. The specified service already exists"
because if we follow Strategy 1 MSI engine tries to install Windows Service on top of the existing service and OF COURSE it fails MSI engine (StopServices, DeleteServices actions are executed before actual
installation and they look at ServiceControl table). In order to stop service first and delete them you have to fill ServiceContol table of the MSI (and then StopServices, DeleteServices actions will recognize what to they have to stop
and delete), like this:
*clip*clip*clip*
' see http://msdn.microsoft.com/en-us/library/windows/desktop/aa371634(v=vs.85).aspx for more info
' Update the Service Entry to stop and delete service while uninstalling
query = "INSERT INTO ServiceControl (ServiceControl, Name, Event, Arguments, Wait, Component_) VALUES ('MAD_Service', 'Service name', '160', '', '1', '"
+ componentName + "')"
Set view = database.OpenView(query)
: CheckError
view.Execute : CheckError
' Update the Service Entry to stop and delete service while installing
query = "INSERT INTO ServiceControl (ServiceControl, Name, Event, Arguments, Wait, Component_) VALUES ('MAD2_Service', 'Service name', '10', '', '1', '"
+ componentName + "')"
Set view = database.OpenView(query)
: CheckError
view.Execute : CheckError
*clip*clip*clip*
We can uninstall service first by following Strategy 2, but then we lose transactional support.
So, Simon did I encourage you to change your code a bit?:)
And, btw, if you don't want to change the strategy, please don't rely on SequenceID in MSI table, it can be change, you have to get the at the runtime.
Hope it will help to everybody!
See also more advanced explanation of how MSI works
here.
Truly yours, Marat

You cannot add a job with a duplicate name, as a web service already exists with name ... please rename the job and try again

We are attempting to add a web service job and getting a duplicate name issue. I believe we have a caching issue where this job name may already exist but we are unable to see it on the web services status page.
Is there a data services repository database table where I can find these web services jobs listed and clean it up from the backend?

There is no option there that shows me if it is being used as a web service. Here is my issue with some screen shots.
I look at my current web service enabled jobs looking for B_JOB_CP_MDR_to_GW_EMP but it is not in the list.
I attempt to add it from repository DWXDS9
It throws an error and tells me there is already a web service with this name...
Now there has got to be an internal data services table somewhere that has this job listed as a web service. I am just trying to figure out what that table may be to determine if we can do some type of cleanup on it so we can add this job again as a web service (so it is visible to us).

Error: Web service object exists

Hi all!
I am very new with SAP Web Services so, to learn, I created a very simple function, enabled it for RFC, and activated and successfully tested it.
After that, I tried to create a Service, starting the Wizard (Utilities > More utilities > Create web service > From the Function Module).
I followed all steps, setting 'Endpoint type' to 'Function Module'; enabling 'Mapping names'. All remaining values are default values.
Service name was set to 'Z_ESTRAZ_MATERIALI_n' (in the first trial n=1).
After completion of the wizard, in the status bar appears a red-icon message that indicates that the service already exist (but I am sure that no service exists with that name).
- The problem is highly reproducible (with new names).
- In the transaction WSADMIN I cannot see any service listed.
- SAP version: SAP ECC 6.0.
What can I check to solve the problem?
Many thanks.

Hi all!
After some trial-and-error it seems to me that the problem is solved when logging in English instead of Italian language. Doing this way, everything is ok.
Bye.

Need help with Sharepoint foundation web application stuck on "STOPPING" error job-service-instance-GUID Number already exists

Hi All,
I cant get to stop SharePoint foundation web app service. Its stuck on status stopping
I have tried the following:
reset IIS
restarted the Timer Service
When I try to use powershell command to stop I get the following error:
Can anyone who went through this help PLEASE
Stop-SPServiceInstance : An object of the type
Microsoft.SharePoint.Administration.SPServiceInstanceJobDefinition named
"job-service-instance-1ff39eb2-12d2-457d-a749-265e350eb1b1" already exists
under the parent Microsoft.SharePoint.Administration.SPTimerService named
"SPTimerV4". Rename your object or delete the existing object.
At line:1 char:127
+ ... pplication"} | Stop-SPServiceInstance
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...ServiceInstance:
SPCmdletStopServiceInstance) [Stop-SPServiceInstance], SPDuplicateObjectEx
ception
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletStopServ
iceInstance

Hi,
It seems that the issue is in the timer job definition for executing this operation.
My suggestion is to start the service again and delete the job definition from the error and again try to stop it.
This might be helpful:
http://sharepoint.stackexchange.com/questions/22368/is-there-a-powershell-cmdlet-to-delete-a-timer-job
I had a lot of issues in the past when try to stop this instance after the Web apps are provisioned.
As general rule now If I have multi-server Farm topology that has servers that should not serve Web App requests I turn off the service prior to provisioning any Web Apps in the Farm.
BR,
Ivan

BAPI to Accept an already existing service entry sheet

Hi,
Please let me know a BAPI to accept an already existing entry sheet.
i.e set 'X' to the acceptance indicator for an existing entry sheet
Regards
Shiva

Hi,
Read the documentation in se37 and use apprapiate among all.
BAPI_ENTRYSHEET_CHECK Check Service Entry Sheet
BAPI_ENTRYSHEET_CREATE Create Entry Sheet
BAPI_ENTRYSHEET_DELETE Delete Entry Sheet
BAPI_ENTRYSHEET_GETDETAIL Display Detailed Data on Entry Sheet
BAPI_ENTRYSHEET_GETLIST List Entry Sheets
BAPI_ENTRYSHEET_GETRELINFO Detailed Release Information Relating to Entry Sheet
BAPI_ENTRYSHEET_RELEASE Release Entry Sheet
BAPI_ENTRYSHEET_RESET_RELEASE Cancel Release of Entry Sheets
<b>Reward points</b>
Regards

"This entry already exists in the following tables (service contracts)"

Hi,
When running MRP Wizard on Step 3 of 4 'Data Source' screen, I get the following error which we've never had before in running MRP for over two years:
"This entry already exists in the following tables (service contracts)"
We are a manufacturing company and do not use the service contracts functionality within SAP Business One.
Any idea how to resolve so we can continue running MRP?
Any help would be greatly appreciated!

Hi,
I suggest you to not create a message to SAP support before upgrade the B1 2007A version patch level from 42 to 2007A SP01 PL12. PL12 is the latest PL. I said that because I am afraid your message will be a billable message. In my country, the charge for such message is 80 EUR.
After upgrade to PL12, check if the error still exists. If yes, then you create a message to SAP support. This is the most better way.
Rgds,
JimM

The cluster service terminated, error 7024, cannot create a file when that file already exists

I have a test 2-node Failover cluster using Server 2012 R2
As of last night the cluster service on one of the 2 nodes is down with this error:
The Cluster Service service terminated with the following service-specific error:
Cannot create a file when that file already exists.
EventID 7024
The Cluster service waits 60 sec, tries to start, and the same error occurs again.
Any idea where to look to identify which file this error is referring to, or how to go about identifying root cause and getting a solution?
thank you.
samb

Hi Yeswanth
Then you can try with a "Add Counter". This will create new file each time with the same name but a counter will be added to the file name at the end specifying the number of times it is created.
You can also the specify the format to create the counter once select this option u can correspondingly fill the Format and step fields.
Will this be fine.
Regards
Ashmi

Fixing entry already exists . Error in creation of fixed pegging

Hi,
we are calling CTP from GATP after product availability check. Using fixed pegging relationship through standarad abap class
error message is coming as
Error occurred during creation of fixed pegging relationships
Fixing entry already exists
Message no. /SAPAPO/OM_ERROR2328
diagnosis
   An application program called an LCA routine. This led to an error.
Procedure for system administrator
Contact SAP Service. Specify the application
message occurred.
You must also enter:
o   The message number
o   Return code 17313 (om_pb_fixentry_exists)
o   Error code COM Core

Dear Santosh,
the common cause for the error LC Return code 17313:
The heuristic tries to determine locking arguments, but other processes are locking these.
Therefore the proposal,
1. Don't run the MRP in a parallel mode.
2. Check the note 513827 for more information.
Regards,
Tibor

Creation of Microsoft Azure Website failed. The application already exists

Trying to create a new website, I get this error:
Creating Microsoft Azure Website
Creation of Microsoft Azure Website failed. The application already exists. The remote server returned an unexpected response: (409) Conflict.
I succeeded to create this website earlier on and then I deleted it as I didn't need it anymore.
Now I want to create it again but I get this error even though I've deleted all websites, hosting plans, cloud service, etc from my Azure account.
Any idea on how to fix this?

At this point, I don't know how it happened, but we'll need to dig deeper. I believe there is a sequence that can cause problems if you create a site via Current portal and delete it via Preview, but I'm not sure.
BTW, it seems you have 2 other sites that may be in the same situation (deleted in a way that you couldn't recreated them). They're 'shortl...dev' and 't..d' (not giving full name to avoid squatters!). Do you think you'll want to recreate them later? If
so, we can do the same maneuver to get back to a good state.

When I try to install Lightroom 5.6 I get a "Object already exists" message. I can't install it at all

I updated Lightroom to 5.6 before going away for the weekend. When I came home I was unable to access lighroom all together. After searching I finally found how to chat with customer service (which I can't figure out again) and they told me to uninstall Lightroom, make a new Admin on my computer, and re-install it on the new Admin. When I did this I still get the same "Object already exists" message and it won't even install now.

Do a clean (re)install:
* Download a fresh Firefox copy from http://www.mozilla.com/firefox/all.html and save the file to the desktop.
* Uninstall your current Firefox version and remove the Firefox program folder before installing that copy of the Firefox installer.
* Don't remove personal data if you uninstall the current version.
* Delete the files and folders in the %temp% folder.
* It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
Your bookmarks and other profile data are stored elsewhere (not in the Firefox program folder) and won't be affected by a reinstall, but make sure that you do not select to remove personal data if you uninstall Firefox.

"Already exists on the server"

I'm an old holdout on iWeb, still using it in November 2013. Since the Mavericks upgrade (I'm pretty sure that's when my problem started), after I publish, save, and quit, when I open iWeb up again, all the pages are red (on the leftside menu of pages), as if they're all changed and unpublished, even though neither is true. That's fine, but then when I make changes in iWeb and go to "Publish Site Changes," iWeb connects with my web hosting service and then gives me this message: "A folder with the name "Site" [this is my website's name in iWeb] already exists on the server. Do you want to replace it? Replacing it will completely overwrite the current contents of the folder on the server." Then I have the options of "replace" and "cancel." When I click "replace," iWeb uploads my entire website to the server again, and not just the parts that are changed. It's like, somehow, my web hosting service is making no connection to me as it used to. That is, it's treating me and my new content like it's all brand new and foreign. This is problematic because I have lots of video and audio content on my site, so the publishing of the whole site takes hours and hours. Once it's published, all's well online with my site, but how do I get iWeb to not republish the whole site again? Anyone know what's going on? Thank you!

Yes, "should" is the right word! As you suggested, I published the entire site, but when I then quit iWeb and reopened it, same thing: all left-column pages were red and the website & iWeb gave the same message ("A folder with the name "Site" [this is my website's name in iWeb] already exists on the server. Do you want to replace it? Replacing it will completely overwrite the current contents of the folder on the server.").
I suspect Mavericks is interacting with iWeb in some unanticipated way. That's certainly a guess. Any other thoughts/suggestions? Thanks!

Domain Name already exists

When trying to add the domain name *mcpctv.com* so I can launch my website as CCF Consulting for the register, in Business Catalyst, this happens ***error: domain name already exists, please delete any records of previous domain.*** There are no other records...... So how can I put in the Domain name so I can luanch my website?

hi Guys,
need to create a mailbox for a tennant "service" but get this error
This display name already exists. Please use a different display name
any idea ?
We have come across the same issue with the Service@ email account under tennant mode.and we've tried it under multiple domain names that we host..with the same resulting "display name already exists" error.
The Suggestions above by Fiona do not work, and yield :
[PS] C:\Windows\system32>Get-user -id service |FL
The operation couldn't be performed because object 'service' couldn't be found on '<AD Domain Controller>'.
+ CategoryInfo : NotSpecified: (:) [Get-Mailbox], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : FC39465B,Microsoft.Exchange.Management.RecipientTasks.GetMailbox
Yet... if we create another user and add Service@ as an alias it works .. we just cant create it as a primary user name.
Steve

Service of newly created database won't start if XE service already started

Hi all,
I install OracleXE 10g on WinXP SP1 and the default database (XE) is running well. Then I created a new database through TOAD but its window service won't start if XE service already started. If I shutdown the XE service than I can start the service of newly created database. This happens vice versa. When I forced to start the service of the new database with XE service already running windows told me to refer to service-specific error code 183.
But even if I'm able to start the service of the new database when I try to login using SYSTEM sometime it throws 'Oracle not available' and sometime 'shared memory realm does not exist'.
Here's my listener.ora:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oraclexe\app\oracle\product\10.2.0\server)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = C:\oraclexe\app\oracle\product\10.2.0\server)
(PROGRAM = extproc)
(SID_DESC =
(ORACLE_HOME = C:\oraclexe\app\oracle\product\10.2.0\server)
(SID_NAME = CASHIN)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(ADDRESS = (PROTOCOL = TCP)(HOST = SOLTIUS-SETYA)(PORT = 1521))
DEFAULT_SERVICE_LISTENER = (XE)
And here's my tnsnames.ora:
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = SOLTIUS-SETYA)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
CASHIN =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = SOLTIUS-SETYA)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = CASHIN)
I also check the folder %ORACLE_BASE%\oradata\CASHIN folder but I found no single file there. While under oradata\XE I found 6 dbf's files.
The reason why I created a new database is because I want to put Oracle files at another location instead of where XE files reside now.
Any help would be greatly appreciated.
Thanks in advanced.
Regards,
Setya

Then I created a new database through TOADDid you read the part in the license agreement that says XE doesn't support multiple instances?
~Jer

SQL 2008 R2 Management Tools Install Fails - The specified account already exists

Hello,
The installation SQL 2008 R2 Management Tools on a Windows 7 workstation fails with the error, The specified account already exists.
Below is the Summary Log.
Thanks.
Paul
Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal):           -2068052700
Exit facility code:            1212
Exit error code:               1316
Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time:                    2014-10-20 09:02:16
End time:                      2014-10-20 09:05:57
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\sqlncli_Cpu64_1.log
Exception help link:
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name:                  WS287
Machine processor count:       4
OS version:                    Windows 7
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:
\\SRVDIA18\MSSQL2008R2Install\x64\setup\
Installation edition:          STANDARD
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 <empty>
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
CUSOURCE:
ENABLERANU:                    False
ENU:                           True
ERRORREPORTING:                False
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    <empty>
INSTANCENAME:                  <empty>
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
ROLE:                          <empty>
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 <empty>
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
Detailed results:
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\SystemConfigurationCheck_Report.htm
The specified account already exists

There is definitely more amusing endeavours in this world, than trying to understand why an SQL Server install failed. The log files are verbose - but somehow the real information about what went wrong seems to be hiding. Never have proverb about not being
able to see the forest for all the trees felt more appropriate.
Nevertheless, this is where things go sour:
MSI (s) (F4:EC) [09:04:15:744]: Resolving source.
MSI (s) (F4:EC) [09:04:15:744]: Resolving source to launched-from source.
MSI (s) (F4:EC) [09:04:15:744]: Setting launched-from source as last-used.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourceDir property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{2180B33F-3225-423E-BBC1-7798CFD3CD1F}'.
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR ==> \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR product ==> {2180B33F-3225-423E-BBC1-7798CFD3CD1F}
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (F4:EC) [09:04:15:744]: Determining source type
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 2203 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi 3: -2147287038
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 1316 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: Error determining package source type
MSI (s) (F4:EC) [09:04:15:744]: SECUREREPAIR: SecureRepair Failed. Error code: 524F91D34B8
MSI (s) (F4:EC) [09:04:40:775]: Product: Microsoft SQL Server 2008 R2 Native Client -- Error 1316. The specified account already exists.
What account? I supposed you have already asked yourself that and just shaken your head.
But there is another error code 2203, NET HELPMSG 2203 says "The password parameter is invalid." And I note that the source is apparently on a share.
So where is my guess: the MSI installer - which runs as a service, somehow does not have permissions to read the installation from the share. Or is trying to log on to the share with your username/password? No, I don't know, I am just speculating widely.
But my advice would be to copy the installation directory from the share to a local disk.
Maybe that CryptAcquireContext is significant as well - I don't know.
Oh, wait, here is something just before the section above in the log:
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2205 2: 3: Environment
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2228 2: 3: Environment 4: SELECT `Name`,`Value` FROM `Environment`,`Component` WHERE `Component_`=`Component` AND (`Component`.`Action` = 1 OR `Component`.`Action` = 2)
Action start 9:04:15: WriteEnvironmentStrings.
2205 is "The logon processor did not add the message alias." I see that in a successful log that I have, so that is probably benign. But 2228 seems to be
"There are too many names in the user accounts database."
Exactly what that means, I have no clue, but it could be a Windows problem.
Erland Sommarskog, SQL Server MVP, [email protected]

RTC Service already exists

Similar Messages

Maybe you are looking for