Two instances can not simlutaneouly work together on Windows Server 2003 R2

Hi Gurus,
I installed Netweaver on a server which is already having ECC 6.0 which we are using on insctance 10 but i can work only one at a time if one is Up and running the other one should be down this is what am facing.
I have the developer trace log file. Pleaase see below and help me with this.Log below is for Netweaver that i installed and if ECC is UP it throws this in trace.
Total Physical Memory of server = 32 GB
Available Physical Memory of server = 11 GB
In task Manager it shows PF usage of 73 GB and total paging file size set for all drives is 44.98 GB.
LOG
trc file: "dev_disp", trc level: 1, release: "700"
sysno      20
sid        NWC
systemid   562 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    144
intno      20050900
make:      multithreaded, Unicode, 64 bit, optimized
pid        13772
Wed Mar 04 16:06:10 2009
kernel runs with dp version 232000(ext=109000) (@(#) DPLIB-INT-VERSION-232000-UC)
length of sys_adm_ext is 576 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (20 13772) [dpxxdisp.c   1243]
     shared lib "dw_xml.dll" version 144 successfully loaded
     shared lib "dw_xtc.dll" version 144 successfully loaded
     shared lib "dw_stl.dll" version 144 successfully loaded
     shared lib "dw_gui.dll" version 144 successfully loaded
     shared lib "dw_mdm.dll" version 144 successfully loaded
rdisp/softcancel_sequence :  -> 0,5,-1
use internal message server connection to port 3920
Wed Mar 04 16:06:15 2009
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5371]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >specsaptm_NWC_20                        <
DpShMCreate: sizeof(wp_adm)          25168     (1480)
DpShMCreate: sizeof(tm_adm)          5652128     (28120)
DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
DpShMCreate: sizeof(comm_adm)          552080     (1088)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)          0     (104)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)          0     (72)
DpShMCreate: sizeof(vmc_adm)          0     (1864)
DpShMCreate: sizeof(wall_adm)          (41664/36752/64/192)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 000000000CD60050, size: 6348592)
DpShMCreate: allocated sys_adm at 000000000CD60050
DpShMCreate: allocated wp_adm at 000000000CD62150
DpShMCreate: allocated tm_adm_list at 000000000CD683A0
DpShMCreate: allocated tm_adm at 000000000CD68400
DpShMCreate: allocated wp_ca_adm at 000000000D2CC2A0
DpShMCreate: allocated appc_ca_adm at 000000000D2D2060
DpShMCreate: allocated comm_adm at 000000000D2D3FA0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 000000000D35AC30
DpShMCreate: allocated gw_adm at 000000000D35ACB0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 000000000D35ACE0
DpShMCreate: allocated wall_adm at 000000000D35ACF0
MBUF state OFF
DpCommInitTable: init table for 500 entries
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
ERROR => <EsNT> CreateFileMapping name=ES_SEG_20_001 error=1455 [esnti.c      1184]
ERROR => <EsNT> paging file too small for 2044 MB mapfile [esnti.c      1186]
Memory diagnostic                                 *
Systeminformation
Processor-Typ             : Processor-Count           : 16
Operating System          : NT 5.2, Build 3790
Service Pack              : Service Pack 1
NT Pagefile Informations
Config. minimum size      : 47185920 K
Config. maximum size      : 47185920 K
Avail.  maximum size      : 47185920 K
Num
Pagefile
Min.Size
Max.Size
Avail.Max
Curr.Size
1
c:\pagefile.sys
20971520 K
20971520 K
20971520 K
20955136 K
2
o:\pagefile.sys
15728640 K
15728640 K
15728640 K
15728640 K
3
s:\pagefile.sys
10485760 K
10485760 K
10485760 K
10485760 K
NT Task Manager Informations
Total Handles             :        0
Total Threads             :        0
Total Processes           : 2027253931
Commit Charge Total       :        0 K
Commit Charge Limit       : 2143554319 K
Commit Charge Peak        :     2047 K
Phys.Memory Total         : 131657184 K
Phys.Memory Available     :        0 K
File Cache                : 2143594271 K
Kernel Memory Total       :     2047 K
Kernel Memory Paged       :   393225 K
Kernel Memory Nonpaged    :     3851 K
Memory usage of current process
Total virt.address space  : 0000008589934464 K
Avail.virt.address space  : 0000008589043192 K
Private Pages             :        0 K
Total heap size           :    26229 K
Virtual memory regions    :        0 K
Uncommitted heap memory   :    16392 K
Allocated heap memory     :     8196 K
Moveable heap memory      :     2202 K
DDE shared heap memory    :        0 K
Memory usage of all processes
PID
Image
Instance
Work.Set
WS Peak
Priv.Pages
PP Peak
Pg Fault
17072
sapstartsrv.exe
21452 K
21848 K
23768 K
23888 K
85
11308
msg_server.EXE
[MS] NWC_21
10624 K
10624 K
13984 K
13984 K
2
11712
enserver.EXE
[**] NWC_21
16476 K
16476 K
58040 K
58040 K
4
7116
msg_server.EXE
[MS] NWC_20
10960 K
10960 K
14432 K
14436 K
2
13772
disp+work.EXE
43272 K
43648 K
75636 K
82264 K
11
17560
igswd.EXE
[**] NWC_20
4108 K
4408 K
3208 K
3572 K
1
7072
igsmux.exe
14308 K
14308 K
18036 K
18072 K
3
16988
igspw.exe
3544 K
3544 K
4012 K
4012 K
0
5504
igspw.exe
3544 K
3544 K
4012 K
4012 K
0
Sum
128288 K
215128 K
Error 11 while initializing OS dependent part.
ERROR => DpEmInit: EmInit (1) [dpxxdisp.c   9634]
ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c   9561]
DP_FATAL_ERROR => DpSapEnvInit: DpMemInit
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=1
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Mar 04 16:06:26 2009
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long)               Wed Mar 04 10:36:26 2009
========================
No Ty. Pid      Status  Cause Start Err Sem CPU    Time  Program          Cl  User         Action                    Table
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
0 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
1 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
2 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
3 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
4 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
5 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
6 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
7 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
8 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
9 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
10 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
11 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
12 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
13 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
14 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
15 ?         -1 Free          no      0   0        0                                                                         
ERROR => DpRqTxt: bad rqtype -1 [dpxxrq.c     785]
16 ?         -1 Free          no      0   0        0                                                                         
Dispatcher Queue Statistics               Wed Mar 04 10:36:26 2009
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
0
0
2000
0
0
--------++++--
+
DIA
0
0
2000
0
0
--------++++--
+
UPD
0
0
2000
0
0
--------++++--
+
ENQ
0
0
2000
0
0
--------++++--
+
BTC
0
0
2000
0
0
--------++++--
+
SPO
0
0
2000
0
0
--------++++--
+
UP2
0
0
2000
0
0
--------++++--
+
max_rq_id          0
wake_evt_udp_now     0
wake events           total     0,  udp     0 (  0%),  shm     0 (  0%)
since last update     total     0,  udp     0 (  0%),  shm     0 (  0%)
Dump of tm_adm structure:               Wed Mar 04 10:36:26 2009
=========================
Term    uid  man user    term   lastop  mod wp  ta   a/i (modes)
Workprocess Comm. Area Blocks               Wed Mar 04 10:36:26 2009
=============================
Slots: 300, Used: 0, Max: 0
--------++--
+
id
owner
pid
eyecatcher
--------++--
+
NiWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd=1
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL

If you installed the system with default memory parameters both instances will try to allocate 1/2 of the virtual memory on startup.
I suggest you decrease the parameter
es/initial_size_MB
to a value that both instances will fit into physical memory (so e. g. 4000). Then try to start both instances.
Markus

Similar Messages

  • Can not find "Work Folder" in windows server standard edition

    Guys, I have a testing lab and all is working with the exception of the fact that I can not find "work Folder" to install it.  I'm using windows server 2012 standard evaluation copy edition.  Normally work folder should be under >file
    and storage service>file and iSCSI services.  However, it is not there.  Can someone help please
    staphisco

    Hi,
    From the overview, Work Folder is not supported in Windows Server 2012 (only Windows Server 2012 R2). 
    Work Folders Overview
    http://technet.microsoft.com/en-us/library/dn265974.aspx
    Software requirements
    Work Folders has the following software requirements for file servers and your network infrastructure:
    A server running Windows Server 2012 R2 for hosting sync shares with user files 
    If you have any feedback on our support, please send to [email protected]

  • Installing 10g and Grid control together on Windows Server 2003

    Hi all,
    I've been having some trouble installing both the Grid Control and Oracle 10g together on a Windows Server 2003 box.
    Here's the steps I've followed (if im stepping away from the norm, please tell me.. i REALLY need to do this properly without any hacks.. right now im on a test box.. but soon enough I have to do it in a live production environment and I really need a clean install).
    I had a copy of Oracle 9i installed - my databases are pretty small.. 1.5Gb at most and I have been advised to just do an export and import them back in later.. which is fine by me..
    I uninstalled Oracle 9i, making sure to check all the environment variables were clear and the registry settings were gone.
    I ran the grid control setup
    Set Home name = Ora10gGC
    Set home path = C:\Oracle\Ora10gGC
    I selected Enterprise Manager 10g Grid Control Using a New database 10.1.3.0
    I set my passwords, and then set the global database name as emrep (the default)
    All the optional configuration assistants ran successfull
    Once this was all done and the install was finished, I restarted the server
    Then I inserted the Oracle 10g cd
    I ran 10g setup
    Click Advanced installation
    Set home name = Ora10g
    Set home path = C:\Oracle\Ora10g
    I selected Enterprise edition
    Selected General purpose database
    I got the following message:
    The ORACLE_HOME environment variable is current set. This will prevent proper use of Multiple Oracle Homes and since it is not required for any Oracle products to function, it will be unset in your environment.
    I set the global database name on my starter database to STARTER, I selected Use Grid Control for Database Management and set my paths and passwords, then I clicked install.
    The install worked up till it tried to create the starter database, then it failed with an ORA-12560 error.
    I checked the environment variables and it seems that ORACLE_HOME wasn't unset after all. I deleted it from my environment variables and restarted the server, but I still get the ORA-12560 error when i try to create a new database.
    I'd really appreciate it if someone could tell me how to install these 2 products together properly.. Thanks!

    I suggest you to read Metalink Note:344537.1 "Installing EM 10g Grid Control Fails to Start the TNSListener Due to Environment Settings"
    Additionaly could you post the fragment from alert.log and listener.log files, so more diagnostic information can be provided on this issue.
    ~ Madrid.

  • ORA-12516: TNS:listener could not find ... on Windows Server 2003

    We are getting "ORA-12516: TNS:listener could not find available handler" while testing asp.net web application.
    We have following configuration:
    - A 10g database server on Windows Server 2000
    - A Web Server running IIS6 on Windows Server 2003
    - ODP.Net for 10g client installed on Web Server
    we are testing our web app with 75 concurrent users, as far as I can tell we are closing connections in our app and open connection only while retrieving and saving records.
    I saw this error very first time when we upgraded our web server to use 10g client. Before that we were using Oracle 9 client and have tested this app with 100 concurrent users without any error.
    Does anyone can help or point a resource that can help to resolve this error?
    Thanks.

    Hi,
    You'll likely want to take that up with the networking folks as the error seems to be coming from the Listener.
    How many connections does each instance of your app make? If you make the same number of connections via sqlplus for example rather than ODP, do you see the same results? I know creating 60 or sqlplus sessions may not be fun, but it will help determine if this issue is truly somehow related to ODP. It doesnt seem likely it would be, and if ODP can be removed from the picture, it will be that much easier to troubleshoot.
    One thing I'd suggest though, is to make sure your app is cleaning up after itself properly to as to use resources efficiently. If you have access to My Oracle Support, see the following note:
    Note 730678.1 Oracle Data Provider for .Net Best Practices
    Hope it helps,
    Greg

  • One of the DC can't connect to AD for Windows server 2003

    Dear Sir,
    We have 2 Domain Controllers in our Domain, DC1 and DC3, which is running on Windows Server 2003 SP2, I found the DC3 failed to connect to AD, and I found the following error message logged in the system event many time
    Source: MRxSmb
    Type : Error
    主瀏覽器從電腦 DC1 收到 認為它是傳輸 NetBT_Tcpip_{C1D9AA59-2423-4059-A773 網域主瀏覽器的伺服器宣告。 主瀏覽器已中止或已強制選擇。
    Source: KDC
    Type: warning
    找不到事件識別碼 20 (在來源 KDC 中) 的描述。本機電腦可能沒有所需的登錄資訊或訊息 DLL 檔案，因此無法顯示發自遠端電腦的訊息。您可以使用 /AUXSOURCE= flag 來重新抓取這個描述。請參閱 [說明及支援] 來了解詳細資料。以下資訊為事件的一部份: 事件日誌檔已損毀。
    Source: Kerberos
    Type: Error
    The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/dc1.domain.com.  This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically
    named  machine accounts in the target realm (Domain name), and the client realm.   Please contact your system administrator.
    I have searched on internet, and tried some of the suggestions but still can't fixed the issue, I also can't depromo the DC3, and can't use remote desktop connection connect to DC3
    What can I do now, can I just reinstall the DC3 and process the dcpromo again?

    Hi Calin,
    Here is the log content for your reference:-
    Domain Controller Diagnosis
    Performing initial setup:
       * Verifying that the local machine DC3, is a DC.
       * Connecting to directory service on server DC3.
       * Collecting site info.
       * Identifying all servers.
       * Identifying all NC cross-refs.
       * Found 2 DC(s). Testing 1 of them.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\DC3
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             * Active Directory RPC Services Check
             ......................... DC3 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\DC3
          Starting test: Replications
             * Replications Check
             [Replications Check,DC3] Inbound replication is disabled.
             To correct, run "repadmin /options DC3 -DISABLE_INBOUND_REPL"
             [Replications Check,DC3] Outbound replication is disabled.
             To correct, run "repadmin /options DC3 -DISABLE_OUTBOUND_REPL"
             ......................... DC3 failed test Replications
          Test omitted by user request: Topology
          Test omitted by user request: CutoffServers
          Starting test: NCSecDesc
             * Security Permissions check for all NC's on DC DC3.
             * Security Permissions Check for
               DC=ForestDnsZones,DC=domain,DC=COM,DC=HK
                (NDNC,Version 2)
             * Security Permissions Check for
               DC=DomainDnsZones,DC=domain,DC=COM,DC=HK
                (NDNC,Version 2)
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=domain,DC=COM,DC=HK
                (Schema,Version 2)
             * Security Permissions Check for
               CN=Configuration,DC=domain,DC=COM,DC=HK
                (Configuration,Version 2)
             * Security Permissions Check for
               DC=domain,DC=COM,DC=HK
                (Domain,Version 2)
             ......................... DC3 passed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             Verified share
    \\DC3\netlogon
             Verified share
    \\DC3\sysvol
             ......................... DC3 passed test NetLogons
          Starting test: Advertising
             Warning: DsGetDcName returned information for
    \\dc1.domain.COM.HK, when we were trying to reach DC3.
             Server is not responding or is not considered suitable.
             The DC DC3 is advertising itself as a DC and having a DS.
             The DC DC3 is advertising as an LDAP server
             The DC DC3 is advertising as having a writeable directory
             The DC DC3 is advertising as a Key Distribution Center
             The DC DC3 is advertising as a time server
             [DC1] LDAP bind failed with error 8341,
             Win32 Error 8341.
             Server DC3 is advertising as a global catalog, but
             it could not be verified that the server thought it was a GC.
             ......................... DC3 failed test Advertising
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=COM,DC=HK
             [DC1] DsBindWithSpnEx() failed with error -2146893022,
             Win32 Error -2146893022.
             Warning: DC1 is the Schema Owner, but is not responding to DS RPC Bind.
             Warning: DC1 is the Schema Owner, but is not responding to LDAP Bind.
             Role Domain Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=COM,DC=HK
             Warning: DC1 is the Domain Owner, but is not responding to DS RPC Bind.
             Warning: DC1 is the Domain Owner, but is not responding to LDAP Bind.
             Role PDC Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=COM,DC=HK
             Warning: DC1 is the PDC Owner, but is not responding to DS RPC Bind.
             Warning: DC1 is the PDC Owner, but is not responding to LDAP Bind.
             Role Rid Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=COM,DC=HK
             Warning: DC1 is the Rid Owner, but is not responding to DS RPC Bind.
             Warning: DC1 is the Rid Owner, but is not responding to LDAP Bind.
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=COM,DC=HK
             Warning: DC1 is the Infrastructure Update Owner, but is not responding to DS RPC Bind.
             Warning: DC1 is the Infrastructure Update Owner, but is not responding to LDAP Bind.
             ......................... DC3 failed test KnowsOfRoleHolders
          Starting test: RidManager
             * Available RID Pool for the Domain is 9126 to 1073741823
             * dc1.domain.COM.HK is the RID Master
             ......................... DC3 failed test RidManager
          Starting test: MachineAccount
             Checking machine account for DC DC3 on DC DC3.
             * SPN found :LDAP/DC3.domain.COM.HK/domain.COM.HK
             * SPN found :LDAP/DC3.domain.COM.HK
             * SPN found :LDAP/DC3
             * SPN found :LDAP/DC3.domain.COM.HK/domainHK
             * SPN found :LDAP/34106c30-327d-4d63-ae93-fec48cac2975._msdcs.domain.COM.HK
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/34106c30-327d-4d63-ae93-fec48cac2975/domain.COM.HK
             * SPN found :HOST/DC3.domain.COM.HK/domain.COM.HK
             * SPN found :HOST/DC3.domain.COM.HK
             * SPN found :HOST/DC3
             * SPN found :HOST/DC3.domain.COM.HK/domainHK
             * SPN found :GC/DC3.domain.COM.HK/domain.COM.HK
             ......................... DC3 passed test MachineAccount
          Starting test: Services
             * Checking Service: Dnscache
             * Checking Service: NtFrs
             * Checking Service: IsmServ
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: RpcSs
             * Checking Service: w32time
             * Checking Service: NETLOGON
                NETLOGON Service is paused on [DC3]
             ......................... DC3 failed test Services
          Test omitted by user request: OutboundSecureChannels
          Starting test: ObjectsReplicated
             DC3 is in domain DC=domain,DC=COM,DC=HK
             Checking for CN=DC3,OU=Domain Controllers,DC=domain,DC=COM,DC=HK in domain DC=domain,DC=COM,DC=HK on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=COM,DC=HK in domain CN=Configuration,DC=domain,DC=COM,DC=HK on 1 servers
                Object is up-to-date on all servers.
             ......................... DC3 passed test ObjectsReplicated
          Starting test: frssysvol
             * The File Replication Service SYSVOL ready test
             File Replication Service's SYSVOL is ready
             ......................... DC3 passed test frssysvol
          Starting test: frsevent
             * The File Replication Service Event log test
             There are warning or error events within the last 24 hours after the          SYSVOL has been shared.  Failing SYSVOL replication problems may cause         
    Group Policy problems.
             An Warning Event occured.  EventID: 0x800034C4
                Time Generated: 11/04/2014   15:59:23
                (Event String could not be retrieved)
             ......................... DC3 failed test frsevent
          Starting test: kccevent
             * The KCC Event log test
             Found no KCC errors in Directory Service Event log in the last 15 minutes.
             ......................... DC3 passed test kccevent
          Starting test: systemlog
             * The System Event log test
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 11/05/2014   11:11:27
                Event String: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/dc1.domain.com.hk.  The target name used was
    ldap/dc1.domain.COM.HK/[email protected]. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this
    is due to identically named  machine accounts in the target realm (domain.COM.HK), and the client realm.   Please contact your system administrator.
             An Error Event occured.  EventID: 0x00000423
                Time Generated: 11/05/2014   11:11:27
                Event String: The DHCP service failed to see a directory server for authorization.
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 11/05/2014   11:29:56
                Event String: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/dc1.domain.com.hk.  The target name used was
    LDAP/dc1.domain.COM.HK/[email protected]. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this
    is due to identically named  machine accounts in the target realm (domain.COM.HK), and the client realm.   Please contact your system administrator.
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 11/05/2014   11:29:56
                Event String: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/dc1.domain.com.hk.  The target name used was domainHK\DC1$. This indicates that the password
    used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (domain.COM.HK), and the client realm.   Please contact your system administrator.
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 11/05/2014   11:43:20
                Event String: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/dc1.domain.com.hk.  The target name used was cifs/dc1.domain.COM.HK. This indicates that the
    password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named  machine accounts in the target realm (domain.COM.HK), and the client realm.   Please contact your system
    administrator.
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 11/05/2014   11:50:39
                Event String: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/dc1.domain.com.hk.  The target name used was ldap/dc1.domain.COM.HK. This indicates that the
    password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named  machine accounts in the target realm (domain.COM.HK), and the client realm.   Please contact your system
    administrator.
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 11/05/2014   11:50:41
                Event String: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/dc1.domain.com.hk.  The target name used was ldap/ba3f48bc-fa6a-4698-9947-ba8435cbf92b._msdcs.domain.COM.HK. 
    This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named  machine accounts in the target realm (domain.COM.HK), and the client realm.  
    Please contact your system administrator.
             An Error Event occured.  EventID: 0x40000004
                Time Generated: 11/05/2014   11:50:41
                Event String: The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/dc1.domain.com.hk.  The target name used was LDAP/ba3f48bc-fa6a-4698-9947-ba8435cbf92b._msdcs.domain.COM.HK. 
    This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named  machine accounts in the target realm (domain.COM.HK), and the client realm.  
    Please contact your system administrator.
             ......................... DC3 failed test systemlog
          Test omitted by user request: VerifyReplicas
          Starting test: VerifyReferences
             The system object reference (serverReference)          CN=DC3,OU=Domain Controllers,DC=domain,DC=COM,DC=HK and backlink on         
    CN=DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=COM,DC=HK          are correct.
             The system object reference (frsComputerReferenceBL)          CN=DC3,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domain,DC=COM,DC=HK         
    and backlink on CN=DC3,OU=Domain Controllers,DC=domain,DC=COM,DC=HK are          correct.
             The system object reference (serverReferenceBL)          CN=DC3,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=domain,DC=COM,DC=HK         
    and backlink on          CN=NTDS Settings,CN=DC3,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=COM,DC=HK          are correct.
             ......................... DC3 passed test VerifyReferences
          Test omitted by user request: VerifyEnterpriseReferences
          Test omitted by user request: CheckSecurityError
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
       Running partition tests on : domain
          Starting test: CrossRefValidation
             ......................... domain passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... domain passed test CheckSDRefDom
       Running enterprise tests on : domain.COM.HK
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope          provided by the command line arguments provided.
             ......................... domain.COM.HK passed test Intersite
          Starting test: FsmoCheck
             Warning: Couldn't verify this server as a GC in this servers AD.
             GC Name:
    \\dc1.domain.COM.HK
             Locator Flags: 0xe00003fd
             PDC Name:
    \\dc1.domain.COM.HK
             Locator Flags: 0xe00003fd
             Time Server Name:
    \\dc1.domain.COM.HK
             Locator Flags: 0xe00003fd
             Preferred Time Server Name:
    \\dc1.domain.COM.HK
             Locator Flags: 0xe00003fd
             KDC Name:
    \\dc1.domain.COM.HK
             Locator Flags: 0xe00003fd
             ......................... domain.COM.HK passed test FsmoCheck
          Test omitted by user request: DNS
          Test omitted by user request: DNS

  • Can't install DPM agent for Windows Server 2003

    Hi,
    We have DPM 2012 backup server.i try to install DPM Agent on Windows server 2003 PC. but installation failed.below error are Occured.
    Install protection agent on (serverName.domain name) failed:
    Error 347: An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on (serverName.domain name).
    Error details: %1 is not a valid Win32 application
    Recommended action: Verify that the Agent Coordinator service on(serverName.domain name) is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent operation.
    HOW CAN SORTED OUT FOLLOWING ISSURE
    Thanks,
    Gayan

    Hi,
    The below blog outlines the needed steps for protecting
    Windows Server 2003 computers using Data Protection Manager 2012 R2.
    http://blogs.technet.com/b/dpm/archive/2014/06/11/details-on-protecting-windows-server-2003-computers-using-data-protection-manager-2012-r2.aspx
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually
    answer your question. This can be beneficial to other community members reading the thread. Regards, Dwayne Jackson II. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights."

  • Does it  work well on Windows Server 2003 (Stratus hardware based cluster)?

    Wonder, how well does Sun's JMS work in Windows Server 2003 environment?
    I want to run it on Stratus Hardware, but found bin only for Lunix and Sun OS???!!!

    I've been running Arch on my fileserver for about two years now.
    It's seen many a "pacman -Syu" and most of the time its survived. I have had a few times where it has refused to boot, but after about 5 minutes with the arch install cd I have been able to fix things up right away.
    All in all, I'd say it works well for my purposes as a webserver and file server, though I did look into mailserver documentation at one time and I deemed it too complex for my doing. It has since been a while, but I have yet to tackle it.
    The nice thing about arch for me, is that since i'm farmilar with it on my desktop, I feel very comfortable working on it and maintaining it over say Debian or Gentoo.
    If you're willing to spend some time on configuration of your mailserver then go for it. Heck, if you find an easier way to do things then add it to the Wiki!
    Anways just for refrence...
    http://wiki.archlinux.org/index.php/Hula_Howto
    http://wiki.archlinux.org/index.php/PostFix_Howto
    http://wiki.archlinux.org/index.php/Exi … MTP_server
    Apache, PHP, MYSQL work like a dream on arch and are VERY easy to setup, so no problems there. I'd say go for it and take the time to figure out the proper way to setup postfix for your situation.
    Regardless of what you choose, best of luck!

  • DI Server stopped working after automatic Windows Server 2003 update

    One of my customers is running SBO 2005A SP1 PL22 in Windows 2003 Server environment.
    They are also using DI Server as an integration tool. On September 11, DI Server suddenly stopped working. They just get the notorious -1 / Could not commit transaction error message on each login attempt. I have tried all the usual and unusual quick fixes to resolve the issue, but nothing seems to help.
    To make things odd, I was successful a couple of times when I experimented with different login messages. For instance, if I omitted the <language> and <licenseserver> elements from the message, I was able to get through once. However, a new attempt with the exact same message failed again. Thus the DI Server is not completely down, it's just in some kind of limp mode.
    I checked what had changed that night and I realized that there had been huge automatic Windows updates on the evening of September 10, 2009. There was IE8, .NET Framework 3.5 SP1 and a huge array of security etc patches that had been automatically installed. I'm pretty confident that one of these is the cause of the problem. However, I would hate to blindly roll all those updates back.
    Is there anyone out there who's had this same problem and possibly found a cure ?
    As the customer is running a version that's no longer supported, no support can be expected from SAP. They will just tell us to upgrade to 2007 before any further help is given. Weill, it seems that people out here in the SDN usually have a much better knowledge about the product than SAP does
    Henry

    Hi Gordon,
    Is DI Server really using some version of the .NET framework? If so, do you know which one ?
    Best Regards,
    Henry

  • C:/ disk is not showing on my computer window server 2003 standard edition (UCCX7.0)

    Hi all,
    Today I was checking the server and I find that C: disk is not showing Under "My computer" whereas it is showing under disk management and its status is okay. Please tell what the problem and how I resolve that issue? Because server is in production and we can't afford sudden downtime.
    Regards
    Ali Raza

    Hi Walter,
    OS image is 2003.1.5.
    Regards
    Ali Raza

  • Latest version not getting installed in Windows Server 2003 SP@

    check the download is good
    Spiceworks MD5 Checksum: 7954b4e9ded9f7afff01212eaa4ad822

    Hi,
    I had the old version of SpiceWorks working fine on Windows Server 2003 SP2 & thought of upgrading the version to 7.4. When i double click on the downloaded setup, the windows hour glass would show up for few seconds & nothing was happening. Thinking that this was due to old version, i uninstalled it completely & removed the installed directories. Even then i am unable to install the latest version & not finding the source for old version.
    Please help.
    Regards
    Murali S L
    This topic first appeared in the Spiceworks Community

  • Slave instance can not synchronized with the master for a long time

    Hi,
    Slave instance can not synchronized with the master for a long time, and the gap of LSNs between slave and master are more and more larger. The transfer bytes per second between master and slave is 118MB/s , upper limit to the ethernet card. Why???
    ENVIRONMENT:
    1. A network program which we called mcdb is based on BDB 4.8.30. It is used to accept get/set requests and then query data from bdb or save data to bdb.
    2. mcdb implements replication with bdb replication manager api. The default start replication policy is DB_REP_ELECTION, rep ack policy is DB_REPMGR_ACKS_ONE_PEER and rep priority is 100.
    3. The bdb data files, bdb log files, region files and rep files are all in the same home directory.
    4. There are two instances of the mcdb are separately on two standalone servers which has no other programs. These two instances are in one replication group which can elect a master automatically.
    5. The master instance is online, which has lots of requests (get, set, delete).
    ACTIONS:
    1. Start two mcdb instances on two servers and the two instance make a replication group. Slave has already synchronized with the master.
    2. Stop the slave for a long time (more than 20 hours).
    3. Start the slave instance to synchronize data with master.
    RESULT:
    1. the gap of LSNs between slave and master are more and more larger.
    2. db_stat of master and slave:
    master db_stat:
    467170     Number of PERM messages not acknowledged
    9245     Number of messages queued due to network delay
    172415     Number of messages discarded due to queue length
    25880     Number of existing connections dropped
    3407     Number of failed new connection attempts
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_REPMGR site information:
    10.67.15.146 (eid: 0, port: 30011)
    Environment configured as a replication master
    331726/3574994     Next LSN to be used
    0/0     Not waiting for any missed log records
    328872/466092     Maximum permanent LSN
    0     Next page number expected
    0     Not waiting for any missed pages
    0     Number of duplicate master conditions originally detected at this site
    2147M     Current environment ID (2147483647)
    100     Current environment priority
    49     Current generation number
    50     Election generation number for the current or next election
    2323     Number of duplicate log records received
    0     Number of log records currently queued
    6768     Maximum number of log records ever queued at once
    55284     Total number of log records queued
    120M     Number of log records received and appended to the log (120475988)
    111     Number of log records missed and requested
    2147M     Current master ID (2147483647)
    2     Number of times the master has changed
    0     Number of messages received with a bad generation number
    8505306     Number of messages received and processed
    12     Number of messages ignored due to pending recovery
    471869     Number of failed message sends
    12M     Number of messages sent (12959945)
    0     Number of new site messages received
    1     Number of environments believed to be in the replication group
    990543     Transmission limited
    0     Number of outdated conditions detected
    0     Number of duplicate page records received
    0     Number of page records received and added to databases
    0     Number of page records missed and requested
    Startup complete
    6244678     Number of transactions applied
    0     Number of startsync messages delayed
    1     Number of elections held
    1     Number of elections won
    No election in progress
    0.057097     Duration of last election (seconds)
    8944103     Number of bulk buffer sends triggered by full buffer
    0     Number of single records exceeding bulk buffer size
    5273M     Number of records added to a bulk buffer (5273592170)
    10M     Number of bulk buffers sent (10490865)
    0     Number of re-request messages received
    0     Number of request messages this client failed to process
    0     Number of request messages received by this client
    slave db_stat:
    0     Number of PERM messages not acknowledged
    0     Number of messages queued due to network delay
    0     Number of messages discarded due to queue length
    1454     Number of existing connections dropped
    0     Number of failed new connection attempts
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    DB_REPMGR site information:
    10.67.15.147 (eid: 0, port: 30011)
    Environment configured as a replication client
    329544/2916048     Next LSN expected
    330433/2013808     LSN of first log record we have after missed log records
    329543/5500501     Maximum permanent LSN
    0     Next page number expected
    0     Not waiting for any missed pages
    0     Number of duplicate master conditions originally detected at this site
    2147M     Current environment ID (2147483647)
    100     Current environment priority
    49     Current generation number
    50     Election generation number for the current or next election
    5256M     Number of duplicate log records received (5256599432)
    3925284     Number of log records currently queued
    3925285     Maximum number of log records ever queued at once
    4880561     Total number of log records queued
    3578038     Number of log records received and appended to the log
    1912297     Number of log records missed and requested
    0     Current master ID
    1     Number of times the master has changed
    0     Number of messages received with a bad generation number
    12M     Number of messages received and processed (12980442)
    2     Number of messages ignored due to pending recovery
    0     Number of failed message sends
    1912307     Number of messages sent
    0     Number of new site messages received
    0     Number of environments believed to be in the replication group
    0     Transmission limited
    0     Number of outdated conditions detected
    0     Number of duplicate page records received
    0     Number of page records received and added to databases
    0     Number of page records missed and requested
    Startup incomplete
    110568     Number of transactions applied
    80     Number of startsync messages delayed
    0     Number of elections held
    0     Number of elections won
    No election in progress
    0     Number of bulk buffer sends triggered by full buffer
    0     Number of single records exceeding bulk buffer size
    0     Number of records added to a bulk buffer
    0     Number of bulk buffers sent
    0     Number of re-request messages received
    0     Number of request messages this client failed to process
    0     Number of request messages received by this client
    Edited by: 899585 on 2013-1-4 下午10:54
    Edited by: 899585 on 2013-1-4 下午10:55

    Hi,
    Unfortunately, this issue is beyond the level of what is supported over the forum. Performance related issues are extremely complex and require an in-depth understanding of your environment and dedicated support. In a generic sense, you can look at this as a basic queueing problem. You have a server that went down and work is still coming in. When the server gets started it is possible that it may never catch up depending on new work coming in and the rate at processing the old work.
    So what would you do in this case --- one thing would be to reduce the new work coming in. In HA terms this would be slowing the master down and you can increase DB_REP_ACK_TIMEOUT for this. Another thing you could do is add fresh servers to help reduce the workload. In HA terms, this would be the equivalent of restarting the client and give it a fresh look at everything. Another thing you could do is replan the system and load balance. In HA terms, it would mean something like take a hot backup of the master and reinit a client from scratch.
    If you are interested in getting a dedicated support person working on this concern, please let me know and we can move forward down that path. Just respond to the thread with your email address and I will get in contact with you so we can pursue that approach.
    thanks
    mike

  • Instance can not be started successfully!

    The process "disp+work.EXE" is yellow and has the status "Running but Dialog Queue standstill, J2EE: Connection to message server"
    The system is ECC6.0+MaxDB on Windows Server 2003
    Following is the developer trace:
    trc file: "dev_disp", trc level: 1, release: "700"
    sysno      03
    sid        EC1
    systemid   560 (PC with Windows NT)
    relno      7000
    patchlevel 0
    patchno    52
    intno      20050900
    make:      multithreaded, Unicode, optimized
    pid        7552
    Wed Aug 02 17:39:56 2006
    kernel runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)
    length of sys_adm_ext is 572 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (03 7552) [dpxxdisp.c   1231]
         shared lib "dw_xml.dll" version 52 successfully loaded
         shared lib "dw_xtc.dll" version 52 successfully loaded
         shared lib "dw_stl.dll" version 52 successfully loaded
         shared lib "dw_gui.dll" version 52 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    Wed Aug 02 17:40:05 2006
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 9 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5233]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: start server >superjxy_EC1_03                         <
    DpShMCreate: sizeof(wp_adm)          12672     (1408)
    DpShMCreate: sizeof(tm_adm)          3954072     (19672)
    DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
    DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
    DpShMCreate: sizeof(comm_adm)          528064     (1048)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)          0     (72)
    DpShMCreate: sizeof(vmc_adm)          0     (1452)
    DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 07310040, size: 4607512)
    DpShMCreate: allocated sys_adm at 07310040
    DpShMCreate: allocated wp_adm at 07311E28
    DpShMCreate: allocated tm_adm_list at 07314FA8
    DpShMCreate: allocated tm_adm at 07314FD8
    DpShMCreate: allocated wp_ca_adm at 076DA570
    DpShMCreate: allocated appc_ca_adm at 076E0330
    DpShMCreate: allocated comm_adm at 076E2270
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 07763130
    DpShMCreate: allocated gw_adm at 07763170
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 077631A0
    DpShMCreate: allocated wall_adm at 077631A8
    Wed Aug 02 17:40:06 2006
    MBUF state OFF
    EmInit: MmSetImplementation( 2 ).
    MM diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 1024 kByte.
    Using implementation flat
    <EsNT> Memory Reset disabled as NT default
    <ES> 511 blocks reserved for free list.
    ES initialized.
    Wed Aug 02 17:40:07 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 6588
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3540
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1617]
    ***LOG Q0K=> DpMsAttach, mscon ( superjxy) [dpxxdisp.c   11414]
    DpStartStopMsg: send start message (myname is >superjxy_EC1_03                         <)
    DpStartStopMsg: start msg sent
    Wed Aug 02 17:40:08 2006
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    Wed Aug 02 17:40:09 2006
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpJ2eeLogin: j2ee state = CONNECTED
    DpMsgAdmin: Set release to 7000, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
    DpMsgAdmin: Set patchno for this platform to 52
    Release check o.K.
    Wed Aug 02 17:41:55 2006
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
    ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1528
         (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3552) [nixxi.cpp    4235]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6588)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Wed Aug 02 17:42:08 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 5704
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3618
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Wed Aug 02 17:43:24 2006
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
    ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1488
         (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3619) [nixxi.cpp    4235]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5704)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Wed Aug 02 17:43:28 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 7028
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3650
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Wed Aug 02 17:44:49 2006
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
    ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1480
         (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3651) [nixxi.cpp    4235]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=7028)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Wed Aug 02 17:45:08 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 6392
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3692
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Wed Aug 02 17:46:30 2006
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
    ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1476
         (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3693) [nixxi.cpp    4235]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6392)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Wed Aug 02 17:46:48 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 7064
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3728
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Wed Aug 02 17:48:10 2006
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
    ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1496
         (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3729) [nixxi.cpp    4235]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=7064)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Wed Aug 02 17:48:28 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 5660
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3764
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Wed Aug 02 17:49:44 2006
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
    ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1484
         (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3765) [nixxi.cpp    4235]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5660)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Wed Aug 02 17:49:48 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 6372
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3801
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Wed Aug 02 17:51:09 2006
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
    ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1468
         (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3802) [nixxi.cpp    4235]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6372)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Wed Aug 02 17:51:28 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 7324
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3838
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Wed Aug 02 17:52:49 2006
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
    ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1464
         (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3839) [nixxi.cpp    4235]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=7324)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Wed Aug 02 17:53:08 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3968
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3884
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Wed Aug 02 17:54:29 2006
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]
    ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1460
         (SI_ECONN_BROKEN; I4; ST; 127.0.0.1:3885) [nixxi.cpp    4235]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3968)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Wed Aug 02 17:54:48 2006
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 188
      argv[0] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[1] = C:\usr\sap\EC1\DVEBMGS03\exe\jcontrol.EXE
      argv[2] = pf=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=3923
      argv[5] = -DSAPSYSTEM=03
      argv[6] = -DSAPSYSTEMNAME=EC1
      argv[7] = -DSAPMYNAME=superjxy_EC1_03
      argv[8] = -DSAPPROFILE=C:\usr\sap\EC1\SYS\profile\EC1_DVEBMGS03_superjxy
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED

    Thank you for your response
    Following is std_server0.out file:
    stdout/stderr redirect
    node name   : server0
    pid         : 2764
    system name : EC1
    system nr.  : 03
    started at  : Tue Aug 01 21:39:10 2006
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 4584] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 1766 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 312 ms.
    Loading: ThreadManager ... 31 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 406 ms.
    Loading: LockingManager ... 156 ms.
    Loading: ConfigurationManager ... 10313 ms.
    Loading: LicensingManager ... 31 ms.
    Loading: CacheManager ... 172 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service runtimeinfo started. (16 ms).
      Service memory started. (250 ms).
      Service timeout started. (250 ms).
      Service cross started. (312 ms).
      Service file started. (937 ms).
      Service trex.service started. (78 ms).
      Service p4 started. (6140 ms).
      Service classpath_resolver started. (281 ms).
      Service cafeucc~api started. (12453 ms).
      Service userstore started. (16 ms).
      Service jmx_notification started. (46 ms).
      Service log_configurator started. (21562 ms).
      Service locking started. (0 ms).
      Service naming started. (969 ms).
      Service ts started. (281 ms).
      Service licensing started. (0 ms).
      Service javamail started. (750 ms).
      Service failover started. (78 ms).
      Service appclient started. (203 ms).
      Service jmsconnector started. (109 ms).
      Service iiop started. (1547 ms).
      Service connector started. (688 ms).
      Service cafeugpmailcf started. (250 ms).
      Service http started. (1250 ms).
      Service webservices started. (1953 ms).
      Service deploy started. (28125 ms).
      Service configuration started. (16 ms).
      Service MigrationService started. (47 ms).
      Service bimmrdeployer started. (47 ms).
      Service dbpool started. (3687 ms).
    Aug 1, 2006 9:40:26 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_74] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "     No logon possible (no hw ID received by mssg server)                ". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      receiverid=master
      sysnr=$$
      client=001
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=localhost
      poolmaxwait=10000
    Aug 1, 2006 9:40:26 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_74] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
    Aug 1, 2006 9:40:26 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_74] Fatal:
    Aug 1, 2006 9:40:26 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_74] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Aug 1, 2006 9:40:26 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_74] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 2764
    system name : EC1
    system nr.  : 03
    started at  : Tue Aug 01 21:40:31 2006
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 7752] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 1047 ms.
    Loading: PoolManager ... 15 ms.
    Loading: ApplicationThreadManager ... 78 ms.
    Loading: ThreadManager ... 32 ms.
    Loading: IpVerificationManager ... 15 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 390 ms.
    Loading: LockingManager ... 79 ms.
    Loading: ConfigurationManager ... 8031 ms.
    Loading: LicensingManager ... 31 ms.
    Loading: CacheManager ... 156 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (47 ms).
      Service cross started. (15 ms).
      Service file started. (219 ms).
      Service trex.service started. (171 ms).
      Service runtimeinfo started. (15 ms).
      Service cafeucc~api started. (16 ms).
      Service timeout started. (16 ms).
      Service userstore started. (0 ms).
      Service jmx_notification started. (203 ms).
      Service p4 started. (610 ms).
      Service classpath_resolver started. (15 ms).
      Service log_configurator started. (6359 ms).
      Service locking started. (16 ms).
      Service http started. (422 ms).
      Service naming started. (515 ms).
      Service failover started. (125 ms).
      Service javamail started. (266 ms).
      Service jmsconnector started. (296 ms).
      Service appclient started. (265 ms).
      Service ts started. (265 ms).
      Service licensing started. (31 ms).
      Service cafeugpmailcf started. (250 ms).
      Service connector started. (406 ms).
      Service iiop started. (547 ms).
      Service webservices started. (765 ms).
      Service deploy started. (14735 ms).
      Service MigrationService started. (47 ms).
      Service bimmrdeployer started. (32 ms).
      Service configuration started. (47 ms).
      Service dbpool started. (3063 ms).
    Aug 1, 2006 9:41:11 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_73] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "     No logon possible (no hw ID received by mssg server)                ". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      receiverid=master
      sysnr=$$
      client=001
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=localhost
      poolmaxwait=10000
    Aug 1, 2006 9:41:11 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_73] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
    Aug 1, 2006 9:41:11 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_73] Fatal:
    Aug 1, 2006 9:41:11 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_73] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Aug 1, 2006 9:41:11 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_73] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 2764
    system name : EC1
    system nr.  : 03
    started at  : Tue Aug 01 21:41:21 2006
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 2744] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 594 ms.
    Loading: PoolManager ... 16 ms.
    Loading: ApplicationThreadManager ... 78 ms.
    Loading: ThreadManager ... 31 ms.
    Loading: IpVerificationManager ... 31 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 234 ms.
    Loading: LockingManager ... 78 ms.
    Loading: ConfigurationManager ... 8000 ms.
    Loading: LicensingManager ... 32 ms.
    Loading: CacheManager ... 343 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (16 ms).
      Service userstore started. (15 ms).
      Service cross started. (16 ms).
      Service file started. (31 ms).
      Service p4 started. (157 ms).
      Service classpath_resolver started. (32 ms).
      Service timeout started. (78 ms).
      Service trex.service started. (63 ms).
      Service cafeucc~api started. (16 ms).
      Service runtimeinfo started. (16 ms).
      Service jmx_notification started. (47 ms).
      Service log_configurator started. (6297 ms).
      Service locking started. (171 ms).
      Service http started. (250 ms).
      Service naming started. (562 ms).
      Service appclient started. (140 ms).
      Service failover started. (188 ms).
      Service jmsconnector started. (266 ms).
      Service javamail started. (328 ms).
      Service ts started. (360 ms).
      Service licensing started. (16 ms).
      Service cafeugpmailcf started. (313 ms).
      Service connector started. (469 ms).
      Service iiop started. (390 ms).
      Service webservices started. (906 ms).
      Service deploy started. (14906 ms).
      Service MigrationService started. (47 ms).
      Service bimmrdeployer started. (15 ms).
      Service configuration started. (32 ms).
      Service dbpool started. (3125 ms).
    Aug 1, 2006 9:41:59 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_66] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "     No logon possible (no hw ID received by mssg server)                ". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      receiverid=master
      sysnr=$$
      client=001
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=localhost
      poolmaxwait=10000
    Aug 1, 2006 9:41:59 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_66] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
    Aug 1, 2006 9:41:59 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_66] Fatal:
    Aug 1, 2006 9:41:59 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_66] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Aug 1, 2006 9:41:59 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_66] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    stdout/stderr redirect
    node name   : server0
    pid         : 2764
    system name : EC1
    system nr.  : 03
    started at  : Tue Aug 01 21:42:07 2006
    Reserved 1610612736 (0x60000000) bytes before loading DLLs.
    [Thr 3696] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    SAP J2EE Engine Version 7.00   PatchLevel is starting...
    Loading: LogManager ... 609 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 78 ms.
    Loading: ThreadManager ... 47 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 250 ms.
    Loading: LockingManager ... 78 ms.
    Loading: ConfigurationManager ... 8016 ms.
    Loading: LicensingManager ... 31 ms.
    Loading: CacheManager ... 344 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service memory started. (16 ms).
      Service cross started. (15 ms).
      Service file started. (110 ms).
      Service userstore started. (0 ms).
      Service timeout started. (78 ms).
      Service runtimeinfo started. (0 ms).
      Service p4 started. (203 ms).
      Service classpath_resolver started. (31 ms).
      Service cafeucc~api started. (15 ms).
      Service trex.service started. (141 ms).
      Service jmx_notification started. (78 ms).
      Service log_configurator started. (6985 ms).
      Service locking started. (0 ms).
      Service http started. (500 ms).
      Service naming started. (703 ms).
      Service failover started. (141 ms).
      Service appclient started. (484 ms).
      Service javamail started. (515 ms).
      Service ts started. (469 ms).
      Service jmsconnector started. (750 ms).
      Service licensing started. (32 ms).
      Service connector started. (844 ms).
      Service cafeugpmailcf started. (594 ms).
      Service webservices started. (1000 ms).
      Service iiop started. (625 ms).
      Service deploy started. (15016 ms).
      Service MigrationService started. (47 ms).
      Service configuration started. (47 ms).
      Service bimmrdeployer started. (46 ms).
      Service dbpool started. (2953 ms).
    Aug 1, 2006 9:42:44 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_79] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "     No logon possible (no hw ID received by mssg server)                ". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
      passwd=********
      receiverid=master
      sysnr=$$
      client=001
      poolmaxsize=10
      user=SAPJSF
      receiverid_guest=master
      ashost=localhost
      poolmaxwait=10000
    Aug 1, 2006 9:42:44 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_79] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
    Aug 1, 2006 9:42:44 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_79] Fatal:
    Aug 1, 2006 9:42:44 PM    com.sap.security.core.InternalUMFactory [SAPEngine_System_Thread[impl:5]_79] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:346)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:211)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:142)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
    Caused by: com.sap.security.api.UMException: Could not initialize principal factory class 'com.sap.security.core.imp.PrincipalFactory'!: Could not instantiate principal factory class 'com.sap.security.core.imp.PrincipalFactory'!:      No logon possible (no hw ID received by mssg server)               
         at com.sap.security.core.InternalUMFactory.initializeClass(InternalUMFactory.java:1258)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:302)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:251)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Aug 1, 2006 9:42:44 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_79] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

  • WLC CT2504: Interface IP can not be used as internal DHCP server IP

    Hello all,
    I've got a new CT2504 controller with software version 7.0.220.0
    Regarding to
    http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0080af5d13.shtml
    I've tried to configure the internal DHCP on a dynamic-interface, but this is not possible:
    (Cisco Controller) >config interface dhcp dynamic-interface vlan401 primary 172.16.x.3
    vlan401 Interface IP can not be used as internal DHCP server IP
    It works, if I use another IP (aka DHCP server) in the same subnet or in another subnet. It works also for the management interface.
    (Cisco Controller) >show interface detailed management
    Interface Name................................... management
    MAC Address...................................... d0:c2:82:xx:xx:xx
    IP Address....................................... 10.2.x.135
    IP Netmask....................................... 255.255.255.240
    IP Gateway....................................... 10.2.x.129
    External NAT IP State............................ Disabled
    External NAT IP Address.......................... 0.0.0.0
    VLAN............................................. 400
    Quarantine-vlan.................................. 0
    Active Physical Port............................. 1
    Primary Physical Port............................ 1
    Backup Physical Port............................. Unconfigured
    Primary DHCP Server.............................. 10.2.x.135
    Secondary DHCP Server............................ Unconfigured
    DHCP Option 82................................... Disabled
    ACL.............................................. Unconfigured
    AP Manager....................................... Yes
    Guest Interface.................................. No
    L2 Multicast..................................... Disabled
    Scopes are defined and Proxy is enabled.
    (Cisco Controller) >show dhcp summary
      Scope Name                   Enabled          Address Range
    ap                               Yes      10.2.x.137 -> 10.2.x.140
    intern                            Yes      172.16.x.20 -> 172.16.x.30
    (Cisco Controller) >show dhcp proxy
    DHCP Proxy Behaviour: enabled
    Has somebody an explanation for this issue?
    Thanks in advance,
    Regard,
    Robert

    You can use the internal dhcp, but you need to set the primary dhcp as the management ip. So in your dynamic interface, your primary dhcp is configure with the wlc management ip address. Dhcp proxy also needs to be enabled and is enabled by default.
    Thanks,
    Scott Fella
    Sent from my iPhone

  • I can not install Waik and mdt on server 2012 so that i can deploy windows 7 please may you help me?

    i can not install  Waik  and mdt on server 2012 so that i can deploy windows 7 on target machine, i have downloaded mdt  Waik i got error saying you must install frame 2.0  which needs also adk windows 8. i am using hyper  machine.
    thank you

    Hi Warsame12,
    It is worth mentioning that don’t use IPV6 PXE, Windows 7 doesn’t support WDS 2012 deployment over IPv6 PXE. If IPv6 PXE boot is enabled and a 
    Windows 7 installation is selected, a blank screen will appear and Setup will not run.
    The related KB:
    Windows 7 client deployment over IPv6 PXE network boot does not work.
    http://support.microsoft.com/kb/2803741
    I’m glad to be of help to you!
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Can not get an ip from pppoe server

    Hello,
    i have this problem with linksys WRT54GL it's can not get ip from server but the problem with with the router not the isp coz i used another router WRT54S it's work great,
    i'm using the last update for WRTS54GL V1.1 (4.30.14).
    THE PROBLEM FROM ROUTER I THING FROM THE SOFTWARE 
    IS THERE ANY SOLUTION FOR THIS ???
    THANKS 

    Thanks for replay 
    first the modem work as bridge 
    the router can not connect to the server 
    in status page the error is "can not get an ip from pppoe server" when i used the WRT54GL
    if i used other router (WRT54GS) it's connect and get ip and DNS on the status page 
    the user and password is correct .
    the router(WRT54GL)  work when i used DHCP  but not connect when i used PPPOE protocol 
    1.WORKING     modem(bridge)------>router (WRT54GS)PPPOE----------> Router (WRT54GL)DHCP-------> PC
    2.WORKING     modem(bridge)------>router (WRT54GS)PPPOE-------> PC
    3.NOT WORK   modem(bridge)------>Router (WRT54GL)PPPOE-------> PC
    i need the third scenario.
    i think the problem with the router not with the configuration.
    Thanks

Maybe you are looking for