Recruitment-Applicant Actions- Applicant 00000001 already exists

Dear Gurus
hope u'll b doin well.
I  am facing a problem while processing applicant data.  My Hiring action from PB40 --> Initial data entry is working well.
Now I want to insert additional data for applicant.  I have configured "additional data entry actions as follow
Recruitment>app selection>applicant actions
Info group
97                 01     MOD     4001            Applications
97                 02     INS     0022            Education
97                 03     INS     0023            Other/Previous Employers
97                 04     INS     0024            Qualifications
97                 05     INS     4002            Vacancy Assignment
97                 06     INS     4005            Applicant's Personnel Number
I also tried first line on above infogroup in following ways aswell
97 01 COP 4001 Applications
97 01 COP 4000 Applications
I opened transaction PB40.
Insert applicant number. enter date. select this action from list. and execute.
System is giving me following msg.
Applicant 00000001 already exists (initial entry action not allowed)
Message no. PA128
================
Kindly guide me how to resolve this issue.
regards,
Edited by: Ragunath on May 27, 2011 3:25 PM

Hi
For additional data action also you have configured it as initial hiring ... so it is throwing the error
R K

Similar Messages

  • Query on Applicant Actions

    We are implementing both Recruitment & PA modules for the customer. In the Recruitment module, the customer wishes to enter the applicant data into the system only after the initial shortlisting. What are the typical infotypes that are included in the infogroup for Applicant action? As far as I see, Persoal Data, Addresses, Qualification, Previous Employment are the important ones. Are there any more?
    Also, when the applicant is converted to an employee (thru Hiring action), these infotypes should not appear in PA40. How is this integration acheived? Through which integration switch?
    -Shambvi

    May be, I did not explain my query properly. The customer wishes to enter some basic information about the applicant in the Recruitment module. The information typically available at the stage of recruitment are Personal Data (name, address, DOB), Previous Employment Details (like earlier companies, where he worked, along with the duration & designation etc.). Also, when the customer wishes to "Offer" the job to the applicant (if he is selected), they can enter the organizational Assignment data like, position, personnel area/subarea & employee group/subgroup. My first query is, how is  this data entered into the system? Which transaction code? Also, how do we set up the Action (infogroup etc.)? Is it through Applicant Actions?
    Now, if the "Offered" applicant joins the company, then the available applicant info should be transferred to the PA module, so that he becomes "Hired" now. During this process, the applicant, who becomes an employee now, should be assigned a personnel number (internally or externally, depending on the configuration). Also, the user provides the Joining Date. How is this transfer done?
    Once "Applicant to Employee"  transfer is done, should I use PA30 to update the remaining infotypes configured in the Hiring Action?
    Hope I am more clear with my query now.
    -Shambvi

  • FM /BAPI for applicant actions Tx code PB40 in sap hr

    Hello all..
       Could you pls let me know the FM/BAPI for applicant actions (Transaction Code PB40) in  SAP HR ABAP
    Thanks in advance..
    Cheers,
    sami.
    Moderator message: if it exists, you can find it yourself by doing some research.
    Edited by: Thomas Zloch on Mar 15, 2011 2:02 PM

    Hi,
    There are no BAPIs/RFCs to create Infotypes directly. You have to create a custom wrapper RFC around the std function module HR_INFOTYPE_OPERATION to meet your requirements. This function module enables you to maintain master data for employees and applicants. You can transfer one data record ie one infotype record per employee at a time. In your case it would be 3 function calls per each employee. All validation checks take place that would take place in the individual maintenance screens in the dialog. If necessary, the module returns an error message. The error messages are the same as the error messages in the dialog, that is, the individual maintenance screen error messages are transferred rather than interpreted by this module.
    Regards,
    Suresh Datti

  • PB40 Applicant Actions Menu

    Hi All,
    I would like to know that besides configuring Menu 40 - Applicant Actions to display actions according to defined user groups, is it possible to create a new menu ie, Menu 41 instead to display the new actions for different users. I am able to create Menu 41, but in SPRO, it doesn't seem possible to redefine the Action Menu to it.
    Thanks.

    Hi,
    Try this
    SPRO -> Personnel Management -> Recruitment -> Dialog Controls -> Change Action Menu
    You can customize the action menu here, if your customized actions are not being displayed in PB40.
    you can also create different action menus here to be assigned to different users through SU01.
    Hope it helps !!
    Regards,
    Bhavna

  • Applicant Actions-VERY URGENT PLEASE

    Hi,
    Every body,
    In the Transaction Code PB40 ( Where the applicant actions are maintained) How would we be able to have the customer specific actions displayed please. Our client wants the Actions  Like Visa Approval and Visa rejection for the applicant. Please Help. VERY VERY URGENT. Please
    Thanks in anticipation
    parvathi

    Hi Parvathi,
    In IMG go to Personnel Management --> Recruitment --> Applicant Selection --> Applicant actions.  and through configuration, create customer specific actions.
    Hope This helps

  • Applicant actions

    i was unable to see all my applicant actions available initially.
    how to get those actions back and where to assign applicant actions to applicant status
    reply plz
    almost its urgent
    regards

    Hi,
    You can check the Tcode PBA1, PBA2, PBA3, PBA4
    For applicant statistics PBAC.
    Thanks and Regards,
    Revathi.
    Edited by: Revathi on May 12, 2008 2:31 PM
    Edited by: Revathi on May 12, 2008 2:32 PM

  • Context-Root already exists in a deployed object

    I have deployed an EAR project which includes a web module and an EJB module. Now when I right click on any jsp/html file inside my web module (in studio enterprise) to run the file, I get an error stating "Deploying application in domain failed; Context-Root already exists in a deployed object". It appears to be trying to deploy the web module as a stand alone module, but cant because the context root already exists in the EAR deployment. If I run the page from the broswer by typing in the proper URL, it works fine since it is not trying to redeploy.
    If my assumption is true, why is it trying to re deploy as a stand alone module? What can I do to prevent this from happening?
    Thanks!

    - The ide, by default, performs the compile-deploy-run cycle when 'run' is selected. If you move to the 'Files' tab in the project window and expand nbproject|build-impl.xml file, you will see the ant targets used by the build system. Select 'run', right-click and select open; you will see 'run' target depends on run-deploy.
    There are targets available that act on single files, namely compile-single and debug-single that you can try on single files.
    You can also try copying the 'run' target to something like 'my-run' and remove the dependency on run-deploy. The you could select 'my-run' and select 'run-target' right-click menu item.
    In general though, such workarounds are tricky. It is likely i am not understanding the issue here or perhaps it is a bug in the ide or even that ide cannot allow running without redeploy for valid reasons...
    - JSE8.1 is based on NetBeans 5.0.
    Ref: http://forum.java.sun.com/thread.jspa?threadID=5113472
    For J2EE programming, www.netbeans.org site provides a lot of info that are also applicable for jse.
    Docs: http://www.netbeans.org/kb/index.html
    There are several mailing lists, http://www.netbeans.org/community/lists/top.html#top, and some of them dedicated to j2ee. You may want to subscribe to some of these; several j2ee experts are on these mailing lists.

  • "Batch Already Exists" Soft Error

    Hello Everyone.
    We are using batch management as more of a Rev Management tool.  Our issue is that we will perform multiple production receipts that have the same Batch number.  Is there a way to turn off the "soft error" that comes up when we do a production confirmation that states that the "Batch Already Exists".  It is a minor detail but adds many key strokes to our operators day if they have to enter through the soft error.
    Thanks,
    Craig

    Hi,
    Tru turning off the messge in Txn OMCQ for messges 12 - 113 to 120 (whichever is applicable for ur case)
    Regards
    Dheeraj

  • 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

  • HFM deployment issue on EPMA - The application already exists

    The first time I deploy the HFM application everything works fine until I try to redeploy after deleting the application. I have tried registering the application to SS and then try deleting it from there but that does not work. Here is my deployment abort details:
    Submitted Time : Saturday, March 21, 2015 3:38:22 PM
    Last Updated Time : Saturday, March 21, 2015 3:38:33 PM
    User Name : hypadmin
    Process Name :
    Thread : 0
    Server :
    Detail : Initiating Product Action...
    Generating Headers and Callback Information...
    Generating Application Data...
    Posting Product Request...
    Waiting For Status Updates...
    PRODUCT_UPDATE:  Update from product
    Financial Management is transforming metadata from EPMA...
    Creating Application...
    The application already exists.
    Please help and thank you.
    Gideon Seroney

    Got around this issue by creating a classic application over the epma app, provision admin then delete it from consolidation admin.
    Unfortunately it seems that the epma application should never have been registered like a classic app. Always perform 'deploy' and never 'register' since it get stuck in SQL data tables. Unless you are a DBA I would not suggest monkeying with the tables to begin with.
    Thanks!

  • 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]

  • SQL Server 2008 R2 Management Studio (express) install fails (Management Tools Basic Failed) - Error 1316. The Specific account already exists.

    Hi,
    I try to install, the SQL Express 2008 R2 with Advanced 
    The installation has only one error  (Error 1316. The Specific account already exists.) and the Management Tools Basic setup is failed.
    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:                    2015-01-02 16:17:17
      End time:                      2015-01-02 16:24:01
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap
    \Log\20150102_161500\SSCRuntime_Cpu32_1.log
      Exception help link:           http://go.microsoft.com/fwlink?
    LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0
    Machine Properties:
      Machine name:                  KHPNHSI_BNANG
      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
      Installation location:         g:\41bee43707e62fab54ec\x64\setup\
      Installation edition:          EXPRESS_ADVANCED
      Slipstream:                    True
      SP Level                       2
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      True
      AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      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:             
      CUSOURCE:                      
      ENABLERANU:                    True
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION,SSMS,SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          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:                    SQLExpress
      INSTANCENAME:                  SQLEXPRESS
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     g:\41bee43707e62fab54ec\PCUSOURCE
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           PSI\ssamnang
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap
    \Log\20150102_161500\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Passed
      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\20150102_161500\SystemConfigurationCheck_Report.htm
    Please help!
    Samnang.

    Hi SSamnang,
    According to your description, you come across the error that the specific account already exists. Please help to share the complete error log in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150102_161500\SSCRuntime_Cpu32_1.log. You could
    use google drive to upload the error log following the steps in the article:
    https://support.google.com/drive/answer/2424368?hl=en
    From the exception help link, we notice that, the issue could be due to that an attempt fails to install SQL Server Native Client on a computer where SQL Server Native Client is already installed.
    I recommend you to check if there is already an existing SQL Server Native Client on your computer. If there is an existing one, you could uninstall it and install SQL Server again.
    In addition, there is a similar thread for reference:
    https://social.technet.microsoft.com/Forums/en-US/dc31bffd-c9e2-4630-b5d7-9252b03c24fe/sql-2008-r2-management-tools-install-fails-the-specified-account-already-exists?forum=sqltools.
    Regards,
    Michelle Li

  • "condition already exist" – except it doesn't [FM 9.0p230]

    Here is the list of condition tags defined in the document I'm working on, extracted from a .mif copy:
      <CTag `deleted_012006'>
      <CTag `deleted_012007'>
      <CTag `deleted_022007'>
      <CTag `deleted_032006'>
      <CTag `deleted_032007'>
      <CTag `deleted_042006'>
      <CTag `FM8_SYSTEM_HIDEELEMENT'>
      <CTag `FM8_TRACK_CHANGES_ADDED'>
      <CTag `FM8_TRACK_CHANGES_DELETED'>
      <CTag `new_012006'>
      <CTag `new_012007'>
      <CTag `new_022006'>
      <CTag `new_022007'>
      <CTag `new_032006'>
      <CTag `new_042006'>
      <CTag `updated_022007'>
      <CTag `updated_032006'>
      <CTag `updated_042006'>
    So can someone explain why trying to set up a new tag "new_032009" netts me a dull thud and the strangely-worded message "Specified tag already exist"? To make it that bit more annoying, this supposedly pre-existent tag does not show up in either the Conditional Text pod (?) or the list of conditions in the status bar after I press esc, q, C
    Thanks in advance!
    NGN

    So, Sheila ... I sat down this morning to write up a bug-report, and at a given moment suddenly wondered "Can this be a classic pbcak?" Well, yes and no.
    Hard to reproduce, but at least once I've observed the following behaviour:
    When you select an existing condition from the list and see the Add/edit condition tag dialogue, the default button/action is (as you might hope) [Edit]. That is, after all, what you're trying to do; you've selected an existing condition. But changing the style or colour setting deftly switches the default button/action from [Edit] to [Add] – which is not what you're trying to do, given the tag name hasn't changed. And when you then inattentively hit Return instead of thoughtfully clicking on [Edit] ... the system correctly informs you that the tag-name already exists.
    Sneaky, at best! but I suppose the workaround is just to click on [Edit] instead of hitting Return.
    N

  • Win App Deployment include SQL 2008 Express - Check if any SQL Server version already exist

    Hi there
    I have a application that is deploying and installing correctly (Setup and Deployment Project in VS 2008) and has SQL 2008 Express as a pre-requisite. SQL Express installs fine if not found but I don't want it to be installed if any other version of SQL
    Server already exists on the target computer. What do I have to adjust in the Bootstrapper package (package.xml or product.xml)  for SQL Express to do this check? Is the change done within the Bootstrapper package? Do I have to create a Custom Action
    in my Deployment project for this check? Any help is appreciated.
    Thanks
    Dweezil

    Hi Dweezil,
    If you use SQL Express Bootstrapper, you can add the SqlExpressChk.exe package file in the product.xml to check that if SQL Server is already exists. 
    However, please note that SqlExpressChk.exe is limited to only the default instance name, SQLEXPRESS, it won't detect other named instances. A registry check is required when detecting existing SQL Server with custom instance name.
     For more details, please review this
    blog.
    There is also a similar thread for your reference.
    https://dotnetinstaller.codeplex.com/discussions/245326
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.

  • Start VM failed: Domain CCCCCCCC already exists with ID NNN

    Hi,
    I try to start an Oracle VM (currently stopped), the job related to the start action fails and the VM is not started.
    The job log is:
    Message:  OVMAPI_6000E Internal Error: OVMAPI_5001E Job: 1427440127270/Start Vm: ora-aa-u004/Start Vm: ora-aa-u004, failed. Job Failure Event: 1427440128820/Server Async Command Failed/OVMEVT_00C014D_001 Async command failed on server: ovms-aa-us001.mgmt.mydom.com. Object: ora-aa-u004, PID: 32049, Server error: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000b3397000b8916714/VirtualMachines/0004fb0000060000b17c866636533d63/vm.cfg'] failed (1): stderr: Error: Domain '0004fb0000060000b17c866636533d63' already exists with ID '199' stdout: Using config file "/OVS/Repositories/0004fb0000030000b3397000b8916714/VirtualMachines/0004fb0000060000b17c866636533d63/vm.cfg". , on server: ovms-aa-us001.mgmt.mydom.com, associated with object: 0004fb0000060000b17c866636533d63 [Fri Mar 27 08:08:48 CET 2015] [Fri Mar 27 08:08:59 CET 2015]
    Previously I tried to migrate it to another Server of the same pool, the migration Job was successful, the VM resulted running, but actually it was cycling rebooting itself every minutes, after a few steps of the booting process. So I killed it (stopped it) and migrate it back (while in a stopping state) to the original server. When I start it on the original Server, I get the error above.
    Please note that "xm list" on the Server doesn't show that this VM 0004fb0000060000b17c866636533d63 is running, nor that any VM with ID 199 is running.
    Any suggestion? Thanks
    Oscar

    I don't think that advsiing to change the UUID inside the vm.cfg file is too beneficial. It might solve the immediate problem, but it won't make the "ghost" dom go away, which will need a OVMS boot to get rid off.
    Further more it seems like Oracle has fixed this issue and will likely roll the patch out in an upcoming update to xen. Users who have OVM under CSI can request a patch mentioning this BUG: 20687187
    I just received that patch and I will try that out tonight.
    Cheers,
    budy

Maybe you are looking for