HI
i installed 8770 R4 on win 2016 Datacenter, when i try to create an oxe i get the error:
"unable to create a new oxe node : maximum number of pcx licenses is reached"
I searched for this error, and found this error for R3.2, which was fixed in Patch_320810E_WAR.
Unfortunately i cannot open an esr cause my certification has run out , and the new one is month ahead.
Anyone any ideas?
8770 R4 error when creating pbx
- mustafa.ahmad
- Member
- Posts: 253
- Joined: 27 May 2010 03:23
Re: 8770 R4 error when creating pbx
Try with the latest patch of R4.
I had faced the same issue with R3.2 Patch number 3207. I have to upgrade the customer 8770 to R3.2 latest patch.
I had faced the same issue with R3.2 Patch number 3207. I have to upgrade the customer 8770 to R3.2 latest patch.
Re: 8770 R4 error when creating pbx
it is the latest...
Re: 8770 R4 error when creating pbx
Now you got it:
the patch E (3.2.08.10) fixes the issue
the patch E (3.2.08.10) fixes the issue
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
Re: 8770 R4 error when creating pbx
Hi
Did you resolve this issue. I have the same problem
Regards
Did you resolve this issue. I have the same problem
Regards
Re: 8770 R4 error when creating pbx
missing patch Patch_400700K_EXE_JAR.zip
unable to create a new oxe node : maximum number of pcx licenses is reached
unable to create a new oxe node : maximum number of pcx licenses is reached
Re: 8770 R4 error when creating pbx
Any solution to this problem for which we do not have version 3.2.08.10?
In my case I have 3.2.08.07 and all installed patches:
[8770.3.2.08.07]
Patch_320807A_LDIF_BAT_JAR=CR8770-6806, CR8770-6927, CR8770-6949
Patch_320807B_BAT=CR8770-6935
Patch_320807C_DM_JAR=CR8770-6948
Patch_320807D_WAR_JAR=CR8770-6802, CR8770-6848, CR8770-6844
Patch_320807E_JAR_WAR_JS=CR8770-6257, CR8770-6432, CR8770-6514, CR8770-6627, CR8770-6694, CR8770-6770, CR8770-6810, CR8770-6813, CR8770-6819, CR8770-6827, CR8770-6828, CR8770-6835, CR8770-6836, CR8770-6854, CR8770-6872, CR8770-6895, CR8770-6898, CR8770-6900, CR8770-6902, CR8770-6903, CR8770-6905, CR8770-6912, CR8770-6920, CR8770-6922, CR8770-6923, CR8770-6925, CR8770-6933, CR8770-6940, CR8770-6941, CR8770-6942, CR8770-6943, CR8770-6944, CR8770-6957, CR8770-6961, CR8770-6962, CR8770-6968, CR8770-6982, CR8770-6985, CR8770-7001, CR8770-7018, CR8770-7034, CR8770-7009, CR8770-6941, CR8770-6990, CR8770-6645
Patch_320807F_EXE=CR8770-6911
Patch_320807G_JAR_WAR_JS=CR8770-6433, CR8770-6813, CR8770-6963, CR8770-7106, CR8770-6926, CR8770-7105, CR8770-6985, CR8770-7038, CR8770-6857, CR8770-7087, CR8770-6869, CR8770-7032, CR8770-7114, CR8770-7115, CR8770-6831
Patch_320807H_REHOST_EJBCA_CERT=CR8770-6842: After rehost, PKI not working.
Patch_320807I_EXE=CR8770-7183
Patch_320807J_JAR=CR8770-7220 8770: UUM can't create OTMC-V user
Patch_320807K_WAR=CR8770-7168, CR8770-6991
Patch_320807L_EXE=CR8770-7197
Patch_320807M_JAR=CR8770-7173
Patch_320807N_JAR=CR8770-7224
Patch_320807O_EXE=CR8770-7255
In my case I have 3.2.08.07 and all installed patches:
[8770.3.2.08.07]
Patch_320807A_LDIF_BAT_JAR=CR8770-6806, CR8770-6927, CR8770-6949
Patch_320807B_BAT=CR8770-6935
Patch_320807C_DM_JAR=CR8770-6948
Patch_320807D_WAR_JAR=CR8770-6802, CR8770-6848, CR8770-6844
Patch_320807E_JAR_WAR_JS=CR8770-6257, CR8770-6432, CR8770-6514, CR8770-6627, CR8770-6694, CR8770-6770, CR8770-6810, CR8770-6813, CR8770-6819, CR8770-6827, CR8770-6828, CR8770-6835, CR8770-6836, CR8770-6854, CR8770-6872, CR8770-6895, CR8770-6898, CR8770-6900, CR8770-6902, CR8770-6903, CR8770-6905, CR8770-6912, CR8770-6920, CR8770-6922, CR8770-6923, CR8770-6925, CR8770-6933, CR8770-6940, CR8770-6941, CR8770-6942, CR8770-6943, CR8770-6944, CR8770-6957, CR8770-6961, CR8770-6962, CR8770-6968, CR8770-6982, CR8770-6985, CR8770-7001, CR8770-7018, CR8770-7034, CR8770-7009, CR8770-6941, CR8770-6990, CR8770-6645
Patch_320807F_EXE=CR8770-6911
Patch_320807G_JAR_WAR_JS=CR8770-6433, CR8770-6813, CR8770-6963, CR8770-7106, CR8770-6926, CR8770-7105, CR8770-6985, CR8770-7038, CR8770-6857, CR8770-7087, CR8770-6869, CR8770-7032, CR8770-7114, CR8770-7115, CR8770-6831
Patch_320807H_REHOST_EJBCA_CERT=CR8770-6842: After rehost, PKI not working.
Patch_320807I_EXE=CR8770-7183
Patch_320807J_JAR=CR8770-7220 8770: UUM can't create OTMC-V user
Patch_320807K_WAR=CR8770-7168, CR8770-6991
Patch_320807L_EXE=CR8770-7197
Patch_320807M_JAR=CR8770-7173
Patch_320807N_JAR=CR8770-7224
Patch_320807O_EXE=CR8770-7255
Re: 8770 R4 error when creating pbx
upgrade to 3.2.08.10??