Book a Demo

Author Topic: Version Control Configuration  (Read 2777 times)

vidyamanne

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Version Control Configuration
« on: December 28, 2007, 09:51:24 am »
Hi,

I am trying to integrate the MKS Integrity Version Control with the Enterprise Architect.I have an MKS client and configured the sandbox for the EA in that.And coming to the EA I tryed to integrate it with MKS through versioncontrol
  |_ versioncontrolsettings
and when I give the path and try to save it it gives the error that I specified below.
It says that the connection to the MKS is not established.And the error that
I am getting is
                     
           Error : While initializing version control  provider.Error : SCC_E_INITALIZEFAILED.
        Failed to initialize version control provider.

Anyone please help me out as it is very urgent.
Thanks in advance.


   

   

gpc

  • EA User
  • **
  • Posts: 111
  • Karma: +0/-0
    • View Profile
Re: Version Control Configuration
« Reply #1 on: January 02, 2008, 05:05:13 pm »
Hi,
Sorry I have no experience with MKS, but if you're going to use the SCC interface then there should be some sort of SCC client running on the local machine to enable connection to the MKS server. I had some problems getting Perforce to work, then realised I hadn't installed it's SCC client module. Make sure you have this - I guess if you can see the MKS SCC client in the drop down list of SCC Providers then it's installed.
Even a problem with passwords and such would generally produce a dialogue box to retry (unless this is generated by the interface, in which case MKS may silently fail?).
The path setting is the local location of the files and I don't think that an error here would cause a problem until you actually tried to sync.
Do you get the error as soon as you select the MKS SCC or when you try to create/select a client spec or later?