Configuration Management System

Hi,
Is there support for Microsoft Visual Source Safe in JDeveloper 9i?
Regards,
Kriba.

Hi Kriba,
Unfortunately, we do not currently support using Visual Source Safe in 9i JDeveloper.
Given that customers may well use such tools, we decided to publish the source code
control extension that we use in JDeveloper to provide support for Oracle9i SCM, CVS
and ClearCase. You can find the Javadoc for this 'SCM Framework API' in:
<,jdev_home>/jdev/doc/ohj/jdev-scm-doc.zip
We are also working on a 'Developer's' Guide', which is almost done and we'll publish
it here on OTN as soon as possible.
Secondly, I believe several forum members here are working on producing their own
extension for VSS using this extension. Would anyone of those members like to offer
Kriba their thoughts, tips? Does anyone have a complete, working VSS extension?
Hope this help. Regards,
Dominic Battiston
JDeveloper Product Management
Oracle Corp

Similar Messages

Managed system Configuration : The JMX metrics of this Host / Byte Code Adapter are missing

Hi Friends
While Configuring EP system with SOLMAN 7.1 SP12 it is giving below message in self Diagnosis Phase.
1. Solman system is already having ISAGENT version 8 and 9 installed (but Managed system is having 8)
2. I have followed the automatic Process as below
==========================================
Automated Installation of the Introscope Agent via SMD
The Solution Manager provides an application that performs the setup of the Introscope
byte code agent for Java automatically. This section explains the steps to run the setup.
Before you can run the Introscope agent setup, the setup wizard for the managed system
must have been executed.
1.
2.
3.
4. Launch the Introscope Setup application: SAP Solution Manager Configuration 
Managed Systems Configuration  Step 7 Configure Automatically  Automatic
Activity “Byte Code Adapter Installation”  “Open Java URL” (only available in edit
mode). Your screen will look similar to the image below:
5. Check the Enterprise Manager Settings at the top of the screen. These are the
connection parameters that will be used by the agent to connect to the Enterprise
Manager.
6. In the pane Introscope Agent Setttings, select the system that you want to instrument
with the agent. Check “select all” and click “Retrieve Current Settings”. This will display
the current status of the agent setup.
7. To initially setup or update the agents, click Setup Introscope Agent …. This will open
the setup dialog as shown below. Select the desired agent version (by default only one
available) and choose the profile. Next, check the desired instrumentation areas, and,
in the case of AIX, review the AIX settings to match your environment (J9 or classic
mode).
8. Finally, hit Apply to perform the necessary changes in the agent configuration. Agent
config files will be adapted and the Java VM parameters will be set as required for the
managed system.
================================================================
3. Restarted SAP but error still present.
Please help to resolve the issue.
Thanks

Found the solution :
1819577 - Workload Analysis data missing for Java systems when using ISAGENT 8.2.4.0
Cause
l This issue has been identified as product defect and documented in note 1273028
Resolution
l As mentioned in note 1273028, update to ISAGENT 8.2.4 Patch 1 timestamp: 2012-06-26, please proceed as described below)
1. Enable the Maintenance Mode in the Agent Administration UI (http://solmanserver:port/smd/AgentAdmin)
2. Deploy the file to the Solution Manager JAVA stack using the Software Deployment Manager (SDM)
3. Disable the Maintenance Mode in the Agent Administration
4. Execute again the activity 'Byte Code Adapter Installation' of the step 'Configure Automatically' in the 'Managed System Configuration' for the
affected systems. This activity will deploy the new version of the
Introscope JAVA agent in the managed system servers and reconfigure the JVM parameters to use the new version of Introscope JAVA
Agent;
5. Check from Introscope Agent Admin if "IS Agent State" contains value "Running but needs restart"
6. Restart the affected managed system(s)
Finally Solution is update your SOLMAN system patch ISAGENT 8.2.4.0 from patch 0 to 1 via SDM.
Thanks
Mukesh

Plug-in status not performed in Managed system configuration

Dear Experts,
I had configured Managed system configuration in SolMan 7.1 SP10. I could find plug-in status " not performed" (grey) in solman_setup screen . Below screenshot for your reference. I had highlighted the plug-in status in blue for easy recognition. Please provide your valuable inputs.
Thanks,
Phani.

Hi Phani,
It is an open issue, pls see below; you might have to hang on till SP12 is available.
1954303 - The Plug-in Status (ST-A/PI) Grey for Managed System In Solution Manager SP10 and SP11.
A fix for this issue is planned for SP12, please note that this is subject to change
Regards,
Vivek

Solman_setup - Managed System Configuration - ST-PI plugin not up-to-date

Hi,
I have a problem with configuring managed systems in Solution manager using txn solman_setup. When I select the managed system, enter all the data for the READ destination, TMW destination and Back destination and click "Maintain Connection" the system comes back with message:
ST-PI Plugin not up-to-date for managed system IVE, see note 1274287
When I check the OSS note and my managed system I see that my managed system is already on the right required level for SAP Solution Tools Plug-In which is: ST-PI 2008_1_700.
I did check also for service packs but these do not yet exist.
Can someone help me with this issue?
Next list shows current version of the managed systems:
SAP ECC 6.0
SAP ABA 700 Sp 13
SAP Basis 700 SP13
St-PI 2008_1_700 SP 0
PI-Basis 2005_1_700 SP 13
SAP BW 700 SP 15
SAP AP 700 SP9
ST-A/PI 01l_ECC600 SP 0

I did finally resolve my problem with input from OS which is listed below.
You're using the latest version of ST-PI. There's no patch levels
available to download in this moment. To solve this issue I ask you to
first apply the latest version of this note below. Please, read
carefully step by step this note below and follow all the procedures.
Number 1172948
Short text SAP Solution Manager - Basic functions
After you applied the central note, I ask you to apply these notes belowWhen you had all these notes applied, this issue will be solved.
Number 1274287
Short text End-to-End Diagnostics SP18
Number 1244225
Short text Solution Manager 7.0 EhP 1: recommended
corrections
Please, apply the latest patch level for lmservice too.

Managed System SLM~ABAP is not configured (Step 10: Configuration Check)

When I try to spend the last procedure "Configuration Check" (item 10 - Managed System Configuration) I get here is only an error message
The definition of Technical System 'SLM~JAVA' is not correct: 'SLM~JAVA': Operating System 'Linux~2.6.32-358.23.2.' of Host 'sslm' must have at least one Software Component Version
'SLM~JAVA': Operating System 'Linux~2.6.32-358.23.2.' of Host 'sslm' must have at least one Software Component Version
Outside Discovery issue: refer to SAP Note 1611483
Managed systems setup | Managed System Definition Status (post setup) | SYSTEM =SLM~JAVA
What a way such settings: Managed systems setup | Managed System Definition Status?
I probably know only the tab SapSolution Manager: Configuration-> Managed system configuration-> Technical systems, but there make these settings is not possible.
How do I resolve this is "must have at least one Software Component Version"?
ps said note (1611483) has been done, but apparently no effect brought

Hi Michael,
Can you please check below :
Correct Software Component version is displayed in LMDB -> Host - > Tab Installed Software.
Managed System setup -> Assign Diagnostic agent -> Check SAP Host agents (to enusre agent is running)
You may restart both Diagnostic and Host agent and check again after few minutes if data is updated.
Additionally please check below SAP notes which might help resolve the issue :
1890035 - Error "Host 'hostname' must have at least one installed Technical system" during the step 'Check Prerequisites'
1799138 - Solution Manager configuration check returns "The definition of Technical System '{SID}~{STACK}' is not correct: '{SID}~{STACK}' : Operating System '{OSName}' of Host '{hostname}' must have at least one Software Component Version"
Hope this helps.
Thanks & Regards,
Nisha

Managed system diagnostics setup problem

Hi
I am trying to configure managed system setup for NW 7.2 ce java system. I passed check prereq and manual configuration.
However I got stuck at phase "configure diagnotsics". I am getting the "None of the instances making-up this system was selected for setupPlease select at least one instance" message. The managed products : SAP NETWEAVER AS JAVA 7.2 and the product instance :Application Server Java.
the smsy configuration is configured to transfer data from solman sld.
Do you have any idea of Why this message appears? which part should I check?
Thanks....
Edited by: Turgay SAMDANLI on Apr 4, 2011 10:08 AM
Edited by: Turgay SAMDANLI on Apr 4, 2011 10:09 AM

Hi Turgay,
Fisrtly, you should have Solman at least on SP23 in order to configure a CE 7.2 for diagnostics. Before this version the
CE 7.2 is not supported.
Also, check the relevant instances in SMSY definition for the Netweaver CE 7.2.
Kind Regards,
Allam Drebes

I can not make a "Automated Installation of the Introscope Agent" (Managed System Configuration, p.7)

I can not make a "Byte Code Adapter Installation"
When I open meets both paragraphs in step Managed System Configuration is somewhat obscure situations that do not allow the automatic configuration Introscope agent and Introscope Manager
Please help to resolve a number of questions that might help me complete the setup :
1. Why has the status of Enterprise Manager : <No Enterprise Manager configured> ( see picture)
I set up Enterprise Manager in accordance with the installation instructions and complied with all the setting items . Since without any configuration can be associated with the appearance of this status ?
2 . Why Server Node is empty detail settings ?
JDK Location:
Enterprise Manager Host:
Enterprise Manager Port:
Introscope Agent Name:
Introscope Agent Profile:
Autoprobe Directives:
Wily Version:
Introscope Agent Version:
Introscope Agent Log Location:
3 . What a mistake ($ MC: DIAG_WILY_MSG: 032 : L), which appears when I click configuration "Configure Introscope Agent Setup ...", and what it can be linked ? ( see picture )
And the last question , which is also linked to the process of automatic configuration and refers to a phrase from the instruction (Introscope Version 9
Installation Guide For SAP July 2012) points out "Automated Installation of the Introscope Agent via SMD"
there is such an item:
2 . Deploy ISAGENTJ5 *. SCA which is the Introscope Java Agent 9 with SDM to Solution Manager. You may need to deploy also ISAGENT *. SCA which is Introscope Java Agent 8.
However, nowhere does it say where exactly ( on what the absolute path ) I must perform unloading and then what to do with this discharge

The problem was resolved a small manipulation - on stage Basic Configuration,
point 3 "Configure CA Introscope"
I forgot to add to the list of CA Introscope Enterprise Managers link to my manager.
Thus it is necessary to take into account that the path should be correct (usually for linux - /usr/sap/ccms/apmintroscope) and the directory should be applied appropriate privileges.
Then in paragraph "Byte Code Adapter Installation" - there are all the necessary data, and it starts to work correctly

Understanding and using Logical Components for Managed System configuration

Experts.....
I am embarking on a fresh installation of SolMan 7 EhP1 SPS25 and after a few bugs along the way, I am finally nearing the end of including the first Managed System. Somewhat related to {forum:id=10293771] I am hoping I can get some advice, but specifically with regards to Logical Components.
General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
I am at the last step of the managed systems configuration wizard : "create logical components" and only want to ensure that I set things up to hopefully ensure that later usages (Maintenance Optimizer, etc) will handle things correctly!!!
- Our SAP landscape is not very complex
1. only ERP and EP (Dev/Test/Prod).
2. We are utilizing HR Self Service (XSS).
3. The ERP ABAP systems are on Netweaver 7.01.
4. EhP4 has been installed, however we only activated the HCM business functions. Therefore SAP_HR is on 604 whereas SAP_APPL is on 600. I think this might be driving some of the confusion in SMSY
For the DEV ABAP system I am trying to configure:
1. The system is showing up in two products : "SAP ERP" and "SAP ERP Enhancement Package" with the header data for both showing "EHP4 FOR SAP ERP 6.0 / NW7.01" and "SAP ERP 6.0"
2. Under "SAP ERP" the "product instance selection" shows only "SAP NW - Adobe Docu. Service" and "SAP ECC Server" as relevant
3. Under ""SAP ERP Enhancement Package" the "product instance selection" shows only "Human Capital Mgmt" as relevant by default. I manually flagged the development portal system as "relevant" for "SAP XSS (Self Services)"
4. The RCA DBA Cockpit system is complaining "No data available for extractor activation. Please check product mapping and Software Components in SMSY"
5. In the Managed System wizard, there is no logical component for any of the "EHP4 FOR SAP ERP 6.0 / NW7.01" selections
From what I can tell, I think this is correct:
1. Create a Z_EHP4 logical component and assign the DEV/QAS/PRD systems to them
2. Also assign the DEV/QAS/PRD to the existing SAP logical component "SAP ERP ECC SERVER"???
3. For the Solutions, my plan is to create
a. Non-Production ERP : with the dev/test erp/ep systems, but test system as the leading system
b. Production ERP with the prod erp/ep systems only
Thanks for any advice/guidance to help me avoid future problems!!
Edited by: Eric Poellinger on Jun 15, 2011 6:32 PM

General question - I have a slide from SAP that shows a picture from Product->System->Instance->Logical System (client)->Logical Component. I am confused because it shows that Client 100 of a given ABAP system could be assigned to Logical Component A, whereas Client 200 of the same system could be assigned to Logical Component B. This seems wrong to me?
Client 100 could be assigned to any number of logical components, client 200 could be assigned to those same ones or none of them. A logical component is just a grouping of systems used to accomplish some task in SolMan.
For example with ChaRM you could have 2 logical components.
ZCHARM_DEV development (100) -> QA (200) -> prod (300)
ZCHARM_SEC security (900) -> QA (200) -> prod(300)
One is used to show the path for moving development changes to prod, the other for security changes. 200 belongs to both, but 100 only to one.
Set them up in whatever way meets you needs. It looks like for you, you could just use the default one and assign your clients to the various system roles. Not all functionality in SolMan uses the logical components though.

Link SAP PI 7.3 to SolMan 7.1 - error during managed system configuration

All,
I installed my diagnostics agent twice with different options:
- Direct P4 connection via Java EE Dispatcher Node with port 5xx04
- P4 connection via SCS message server with port 81xx
In both cases I get an error during the managed system configuration of SAP PI 7.3: Remote error : Connection to P4 port of managed system failed.
I'm a bit confused with the step Enter System Parameters. In the Java parameters section, I can only enter port 39xx. if not, I get an error.
Also, I marked and unmarked the option concerning the ABAP user store, but the error persists.
Please advice.
Thanks a lot.

Hi Allam,
I checked the KBA and I think now, I have the correct HTTP port.
The error I now get is S:CL_DIAGSTP_MESSAGE:483
When I take the next step, Configure Automatically, I get this error during the Byte Code Adapter Installation phase when I open the Java URL stated in the navigation column:
DIAG_WILY_MSG:157:S - com.sap.smdagent.vmmanager.VMManagerP4Exception: com.sap.smdagent.plugins.connectors.p4.exceptions.P4AuthorizationException: Access is denied to SAP System sid: check the connection credentials.More details about the error in agent 'sappi' log file (SMDAgentApplication.X.log).; nested exception is:
com.sap.engine.services.security.exceptions.BaseLoginException: Error during authentication. For more information see the remote server traces.
Any idea?
Thanks.

Error in Managed System Configuration - Sol Man 7.1

Dear Experts,
Whle configuring using solman_setup, I am getting below mentioned error in Managed System Configuaration:
Cannot retrieve CIM Instances from CIM Class 'SAP_DiagnosticsRelevantSoftwareFeature'!
Cannot retrieve all CIM Instances from CIM class name 'SAP_TechnicalScenario' via LMDB Mass Access API!
Cannot retrieve all CIM Instances from CIM class name 'SAP_DatabaseSystem' via LMDB Mass Access API!
Any suggestions??
Regards
Vivek

Hi Paul ,
Thanks for the note that you provided.
I am reconfiguring the LMDB and conteny Sync... The refresh will take 15-16 hours.. I am just waiting for the
sync to be finished. Let's see what is in the store for me
Keeping my fingers crossed untill then.
Regards
Vivek

Document Management System Configuration

Hi All,
As I have Installed ECC6.0 EHP5,now I want to configure Document Management System into it.
As I am new into it.Can anyone provide me details regarding the same?
Thanks & Regards
Ajitabh
Edited by: jitu001 on Jan 18, 2012 12:36 PM

Hi
I hope you have installed the content server.
For configuration you may find following link useful:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/53/96b53cb74e1676e10000000a114084/frameset.htm
Regards

Configuration Check Error in Managed System Configuration

Hi dear experts,
I come across a problem as the screenshot shows blew:
I check some relevant information, but no issues found:
1.
DEWDFLSSC5062:/usr/sap/hostctrl/exe # ./saphostexec -status
saphostexec running (pid = 7094)
sapstartsrv running (pid = 7097)
10:46:34 24.06.2014 LOG: Using PerfDir (DIR_PERF) = /usr/sap/tmp
saposcol running (pid = 7130)
DEWDFLSSC5062:/usr/sap/hostctrl/exe # cat host_profile
SAPSYSTEMNAME = SAP
SAPSYSTEM = 99
service/porttypes = SAPHostControl SAPOscol SAPCCMS
DIR_LIBRARY = /usr/sap/hostctrl/exe
DIR_EXECUTABLE = /usr/sap/hostctrl/exe
DIR_PROFILE = /usr/sap/hostctrl/exe
DIR_GLOBAL = /usr/sap/hostctrl/exe
DIR_INSTANCE = /usr/sap/hostctrl/exe
DIR_HOME = /usr/sap/hostctrl/work
service/admin_users = daaadm
service/logfile_000 = /tmp/s
service/logfile_001 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace*.trc
service/logfile_002 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.*.trc
service/logfile_003 = /usr/sap/DAA/SMDA97/SMDAgent/log/smdagent_trace.trc
And the version of hostagent is up-to-date.
2.The URL
- http://<SMDhost>:1128/SAPOscol/?wsdl
- http://<SMDhost>:1128/SAPHostControl/?wsdl
can be accessed.
3.The step 3 in managed systems configuration is executed successfully.
4.I have even uninstalled and re-installed the SMD and hostagent, and change the alert_timeout parameter in T-code DMD, but the issue insisted.
5.Only a few SMDs in my landscape, so I think the parameter MaxThreadCount, InitialThreadCount, MinThreadCount should be no problem.
Now I have no idea how to proceed, please give me some advice, thank you in advance.
Best Regards,
Pany Pan

Hi Pany
Kindly check the below two sapnote
1935653 - Error "A timeout occured during the execution of the OS Command Console" when performing a Managed System Configuration - Solution Manager 7.1
1865122 - Solution Manager 7.10 Configuration Check errors : "A timeout occured during the execution of the OS Command Console" "An unexpected error occured"
Moreover , you need to check/verify/maintain the parameter in configtool
ThreadManager -> MaxThreadCount
Total number of Diagnostics Agents * 2 + 50
1250
ThreadManager -> InitialThreadCount
Total number of Diagnostics Agents * 1.5
900
ThreadManager -> MinThreadCount
Total number of Diagnostics Agents
600
ConnectionManipulator -> maxSoTimeOutConnections
Total number of Diagnostics Agents * 1.35
810
ConnectionManipulator -> MaxParallelUsers
Total number of Diagnostics Agents + 50
650
In Diagnostics Agent Troubleshooting - SAP Solution Manager Setup - SCN Wiki
guide check the section Required Solution Manager Java Stack Settings (Scalability)
I face the same issue , which got resolved by maintaining the above parameters, maxthreadCount,
minthreadcount , maxSoTimeOutConnections.
With Regards
Ashutosh Chaturvedi

Error in Managed system configuration.

Hi Folks,
In Solman 7.1 i am configuring my Java system in managed system configuration on the last phase of configuration which is "Check Configuration" i got the below error...
Can any one guide me on this....
I installed the Diagnostic agent as well as willy inter scope.
Regards,
Anil.

check the note which describes your problem
1776959 - Solution Manager 7.1 Manged System configuration. Error: Timezone from managed system could not be retrieved: Timezone of J2EE Engine (GMT+01:00) does not match the timezone of the diagnostics agent (Europe/Berlin)
Resolution
Open the instance.properties file of the J2EE Engine on the managed system
Locate the parameter "-Duser.timezone=" and its value
If the -Duser.timezone is not set the JVM uses GMT
Set the -Duser.timezone parameter in the JVM of the SMD Agent. If there was no "-Duser.timezone in the J2EE's instance.properties file use the timezone that was indicated in the error message e.g. GMT+01:00 (from the above error message, this might differ on your environment) To do this:
Locate the smd.properties file (for newer agents the files is called: smdagent.properties)
The path is: .../usr/sap/<DiagnosticAgentSID>/SMDA<SYSNumber>/SMDAgent/smdagent.properties
The -Duser.timezone= parameter of the Diagnostics Agent and the SAP J2EE engine need to be set to the same timezone. That means the string needs to be the same for both parameters
e.g.
If the -Duser.timezone= parameter of the J2EE engine is set to -Duser.timezone="GMT+01:00"
set the Diagnostics Agent parameter to:
smdagent.javaParameters=-DP4ClassLoad=P4Connection -Xmx256m -Xms256m -Duser.timezone="GMT+01:00"
Restart the Agent
Re-run the "Configuration Check" in the "Managed System Configuration"
Please make sure that the time zone configuration is correct according to the SAP recommendations: http://wiki.sdn.sap.com/wiki/display/Basis/Timezone+changes+best+practices

Deploying Office 365 Pro Plus using System Center Configuration Manager 2012 SP1

Hello,
I am trying to deploy Office 365 Pro Plus to my client machines (more than 100) via. System Center Configuration Manager 2012 SP1. It will use one administrator account for installation. But as per the licensing, we can install Office for up to 5 PCs/Macs
and 5 more Windows tablets/iPads with one Office 365 Pro Plus licenses. If this is the case, then I cannot install Office 365 Pro Plus with one admin account to my 100+ machines, as it will violate the licenses of O365 Pro Plus.
So, what is the alternative approach?
Thanks
Raj

If this is the case, then I cannot install Office 365 Pro Plus with one admin account to my 100+ machines, as it will violate the licenses of O365 Pro Plus.
Hi,
this is incorrect.
There is no licensing restriction/control for the *installation* account at all, the licensing is related to who is *using* Office365ProPlus *after* installation is performed. This control, is implemented by the Microsoft Account, or OrgID, used to sign-in/activate
to Office365 when *using* Office365ProPlus.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Kerberos Configuration Manager for SQL Server: Access of system information failed!

I'm trying to use the new Kerberos Configuration Manager for SQL Server tool that was released recently to verify SPN on several SQL Servers, but any time I attempt to connect to a server I get the following error in the log:
6/24/2013 3:48:22 PM Info: Connect to WMI, \\<HOSTNAME>\root\cimv2
6/24/2013 3:48:25 PM Error: Access of system information failed System.DirectoryServices.AccountManagement.PrincipalOperationException: An error (1332) occurred while enumerating the group membership. The member's SID could not be resolved.
at System.DirectoryServices.AccountManagement.SAMMembersSet.IsLocalMember(Byte[] sid)
at System.DirectoryServices.AccountManagement.SAMMembersSet.MoveNextLocal()
at System.DirectoryServices.AccountManagement.SAMMembersSet.MoveNext()
at System.DirectoryServices.AccountManagement.FindResultEnumerator`1.MoveNext()
at System.Linq.Enumerable.Contains[TSource](IEnumerable`1 source, TSource value, IEqualityComparer`1 comparer)
at KerberosCM.WMIHelper.isUserLocalAdmin(SystemInfo si, UserPrincipal user)
at KerberosCM.WMIHelper.getUserInfo(SystemInfo mi)
6/24/2013 3:48:25 PM Error: Error System.Exception: Access of system information failed!
at KerberosCM.WMIHelper.getUserInfo(SystemInfo mi)
at KerberosCM.SystemInfo.GetInfo()
at KerberosConfigMgr.Utility.Login(String serverName, String login, String password, Boolean isCmdLine, Form uiForm)
Things I have tried to resolve this:
1. Verified that my account is a Domain Admin.
2. Attempt to connect locally without inputting any information for server/user/pw
3. Attempt to connect remotely using server/user/pw
I always receive the same error message and log: Access of system information failed!
Has anyone else run into this issue?

Update to this:
There were some invalid user accounts added to the Local Administrators group only showing up as a GUID. This caused the enumeration of the group to fail and generate the error in my original post. Removing those user accounts from the Administrators group
got past the enumeration error.
However, now when attempting to connect to the servers (locally or remotely) I get this error:
6/27/2013 10:24:24 AM Info: Connect to WMI, \root\cimv2
6/27/2013 10:24:38 AM Error: Access of system information failed System.Runtime.InteropServices.COMException (0x80070035): The network path was not found.
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.PropertyValueCollection.PopulateList()
at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
at System.DirectoryServices.AccountManagement.SAMStoreCtx.ResolveCrossStoreRefToPrincipal(Object o)
at System.DirectoryServices.AccountManagement.SAMMembersSet.MoveNextForeign()
at System.DirectoryServices.AccountManagement.SAMMembersSet.MoveNext()
at System.DirectoryServices.AccountManagement.FindResultEnumerator`1.MoveNext()
at System.Linq.Enumerable.Contains[TSource](IEnumerable`1 source, TSource value, IEqualityComparer`1 comparer)
at KerberosCM.WMIHelper.isUserLocalAdmin(SystemInfo si, UserPrincipal user)
at KerberosCM.WMIHelper.getUserInfo(SystemInfo mi)
6/27/2013 10:24:38 AM Error: Error System.Exception: Access of system information failed!
at KerberosCM.WMIHelper.getUserInfo(SystemInfo mi)
at KerberosCM.SystemInfo.GetInfo()
at KerberosConfigMgr.Utility.Login(String serverName, String login, String password, Boolean isCmdLine, Form uiForm)

Configuration Management System

Similar Messages

Maybe you are looking for