Adobe Connect User Community
Menu

#1 2012-04-27 21:58:21

**_tpettijohn_**

Issues after upgrade to 8.2.1.3

Hello:

I recently upgraded my test environment from 8.1.2.x to 8.2.1.3. 

When I log in to Connect Pro Central with my normal user account (which is in the Administrator group in Connect) and perform some normal administration tasks, I receive error messages instead of a success messages.

Example 1:
From the Connect Pro Central web interface, click the following tabs/links/buttons in order
Administration > Users and Groups > Administrators - Limited > Information > Edit Information > [make a change (or not)] > Save
I Receive the following error:
  Not Authorized
  You do not have permission to access this item.

Example 2:
From the Connect Pro Central web interface, click the following tabs/links/buttons in order
Administration > Users and Groups > Administrators > Information > Edit Information > [make a change (or not)] > Save
I Receive the following error:
  Not Authorized
  You do not have permission to access this item.


Example 3:
From the Connect Pro Central web interface, click the following tabs/links/buttons in order
Administrations > Account > Notifications > [make a change] > Save
I Receive the following error:
  Content Not Available
  Your content cannot be accessed at this time.


I have tried my local Administrator account and received the same results.  Other on my team who are also Administators receive the same results.

I have been able to duplicate the above examples consistently.  There may also be other task that result in the same errors (above) that I have not yet found.

Has anybody seen these or similar issues? 
Are these known issues?
Any fixes?

Thanks,

Tom

Offline

#2 2012-04-30 09:25:14

**_mrock66_**

Re: Issues after upgrade to 8.2.1.3

Hi Tom,  You need to upgrade to 8.2 before patches.  The 8.2 install will run some necessary SQL scripts that you have missed causing your not authorized messages.  Try this path;

8.2, then 8.2.1.2, then 8.2.1.3.  If you don't have these files you will need to call platinum support and request them.  866-335-2256

Good luck!

Offline

#3 2012-04-30 09:43:53

**_mrock66_**

Re: Issues after upgrade to 8.2.1.3

I just confirmed with my contacts at Adobe;

Looks like C8SP2 is a full installer.  so C8 -> C8SP2 -> 8.2.1.3 patch"

Offline

#4 2012-04-30 11:19:00

**_tpettijohn_**

Re: Issues after upgrade to 8.2.1.3

Hello Matt.

Thank you for your quick reply.

I did install service pack 2 first.  I went from Connect 8 SP1 update 2  to Connect 8 SP 2 (8.1.2 to 8.2.0)

After installing service pack 2, I applied update 1 for SP2 (update_8.2.0x_8.2.1.0_licensed.exe) and then ran the update-2961764.sql file on my sql server.  Finally I made the change to \telephonyservice\conf\telephony-settings.xml as described in the readme_patch_cps_8.2.1pdf file.

After applying SP2 update 1, I ran update_8.2.1.x_8.2.1.3.exe.


I was at 8.1.2.x when I began.
Here is what my version.txt file looked like before I applied SP2, update1 or the patch...

package=8.1.1.0.26.20110501.888510
installer=8.1.1.0.10.20110429.889413
fmg=8.1.0.0.43.20110311.864227
fms=8.1.1.0.2.20110427.772086
presenter=8.0.0.0.47.20100915.690506
cps=8.1.1.0.10.20110429.894462
mssql=8.1.0.0.10.20110311.8644363
teleintercall=8.1.0.0.2.20110207.776631
telepremierena=8.1.0.0.21.20110412.882778
telepremiereemea=8.1.0.0.21.20110412.882778
cpshelp=8.1.0.0.10.20110412.882768
addins=8.1.0.1.7.20110405.856042
dbscripts=8.1.1.0.2.20110421.889108
teleavaya=8.1.0.0.4.20110412.882778
telecisco=8.1.0.0.17.20110412.882778
telemeetingone=8.1.0.0.2.20110207.776631
telephonyservice=8.1.0.0.8.20110228.847019
tomcat=6.0.29
stunnel=4.28
patch=patch_8.1.2_2934147


And this is my version.txt file after installing SP2, update 1 and the patch...

package=8.2.0.0.151.20110908.963902
installer=8.2.0.0.11.20110728.938680
fmg=8.2.0.0.4.20110906.879854
fms=8.1.1.0.2.20110427.772086
presenter=8.2.0.0.6.20110824.924658
cps=8.2.0.0.119.20110830.962848
mssql=8.1.0.0.10.20110311.8644363
teleintercall=8.1.0.0.2.20110207.776631
telepremierena=8.1.0.0.21.20110412.882778
telepremiereemea=8.1.0.0.21.20110412.882778
salesdashboard=8.0.0.0.3.20100608.679740
bama=8.2.0.0.89.20110831.963776
cpshelp=8.2.0.0.4.20110908.964981
fonts=8.0.0.0.20091215.1.604011
addins=8.2.0.0.3.20110831.929039
acpmonitor=7.5.1.0.123.20100330.636620
dbscripts=8.2.0.0.23.20110818.956139
teleavaya=8.1.0.0.4.20110412.882778
telecisco=8.1.0.0.17.20110412.882778
telemeetingone=8.1.0.0.2.20110207.776631
telephonyservice=8.1.0.0.8.20110228.847019
tomcat=6.0.29
stunnel=4.28
patch=update_8.2.0.2_8.2.1.0
patch=update_8.2.1.x_8.2.1.3


As far as I can tell, I installed the SP and updates in the correct order.  I did run the SQL script immediately after installing update 1.

Did I miss something?

Tom

Offline

#5 2012-04-30 15:07:11

**_CB_**

Re: Issues after upgrade to 8.2.1.3

It sure sounds like a versioning conflict....are you clustered?

Offline

#6 2012-04-30 15:39:35

**_tpettijohn_**

Re: Issues after upgrade to 8.2.1.3

CB:

Yes, I am clustered.  I have two (2) Connect servers and one (1) SQL server backend.

I installed SP2 on each server

I then installed update 1 on each server. 

I only ran the SQL update script once since I only have 1 SQL server. 
It completed successfully and returned
"(1 row(s) affected)"

I then applied the patch for update 1 on each server taking me to 8.2.1.3.


I have ran the validate script (validate-2961764.sql). 
It runs successfully and returns...
"Successfully loaded PPS_ACL_FIELDS table"


I have tried re-running the update script (update-2961764.sql). 
It runs and returns the following...
"(1 row(s) affected)
START TRANSACTION 0
TRANSACTION CNT - 1
START ....
Finish with Success ...."


I have NOT tried to run the rollback or cleanup sql scripts.


I have compared many of the files on both servers (the ones listed in the read me files as being replaced) and they all seem to have the same names, dates and byte size, which indicates to me that I indeed did apply everything on both servers.


After re-running the sql update script, I still receive the errors mentioned above in my original post.  And other than the errors mentioned above, Connect seems to be functioning properly (at least so far).


Thoughts?


Thanks,
Tom

Offline

#7 2012-05-02 15:09:11

**_CB_**

Re: Issues after upgrade to 8.2.1.3

tpettijohn

So, this behaviour occurs when you are logged in with your Admin account, correct? Have you tried creating a new Admin account via the console? I'd do that. Not via the application, but via the server. Then I'd test the same functionality.

If it's not a clustering/DB corruption of some kind, it might be the userid.

Best bet, if this doesn't resolve it is to send a copy of your DB to Adobe for examination. it sure sounds like there is a corruption in there.

Offline

#8 2012-05-30 17:03:21

**_CB_**

Re: Issues after upgrade to 8.2.1.3

tpettijohn

Any updates on this issue?

CB

Offline

#9 2012-06-12 05:55:28

**_kinchaa_**

Re: Issues after upgrade to 8.2.1.3

same problem!
any other help please!

Offline

#10 2012-07-06 20:41:30

**_tpettijohn_**

Re: Issues after upgrade to 8.2.1.3

I have found that I can reproduce examples 1 & 2 above in my production 8.1.2 environment as well as in my 8.2.1.3 dev environment.  Example 3 however does not happen in my prod 8.1.2 environment.  Since I have similar issues happening in both my dev and prod evirnoments which are at two different version levels, I guess the problem is not related to upgrade from 8.1.2 to 8.2.1.3 as I first thought. Don't know when it started.  Would still like to figure out what is wrong, and how to fix it, but at present, the issue is having little or no impact on the actual operation of Connect.  Thank you to everyone who responded.

Offline

Board footer