since ‎27-07-2020
‎11-10-2020
SheetalAgrawalSoni
Level 2
XTK-170036 Unable to parse expression '@contentEditingMode' SheetalAgrawalSoni - Adobe Campaign Classic
I see this error in every delivery and i looked for entire nms:delivery data schema and dont find keyword contentEditingMode. any guidance ?
49
Views
0
Likes
1
Answers and Comments
Re: Tests for Adobe Campaign Classic Upgrade SheetalAgrawalSoni - Adobe Campaign Classic
As a part of upgrade i will definatly do following testing 1. Look for all process are running on server . For Apache :- ps -ef | grep apache and For Neolane :- ps -ef | grep neolane 2. login to app server and run "nlserver pdump" and verify that all processes are running as exptected. 3. once its up and running login to console using http://servername:8080 and https://servername:443 . This test is require to ensure http and https both are working as expected. 4. once login go to external accoun...
80
Views
0
Likes
1
Answers
Re: Access current delivery id from the workflow. SheetalAgrawalSoni - Adobe Campaign Classic
By default, the report shows all offers in all deliveries across all platforms. to narrow the data set, select your delivery from the delivery field or filter the report data by the start and the end dates. Refresh the report to see the most recent data through the applied filters.
103
Views
0
Likes
0
Answers
Re: Help -- Temporary Work Table Limit by Percent of Total SheetalAgrawalSoni - Adobe Campaign Classic
I am looking at your problem. I need your data in excel file form. I am not able to under stand on the image ,so could you send me excel file.
55
Views
0
Likes
0
Answers
Re: Timezone to EST SheetalAgrawalSoni - Adobe Campaign Classic
In Recepient you can use action > mass update and add field timezone and select EST as value .. Update all will update the timezone at user level For Server level timezone change you will have to insure below stuff if hybrid model .. Solution :- Revert back the oracle client to match the oracle database server version and restart. After that timezone will work as expected. however while investigating we did couple things --> 1. Changed the user timezone setting on MTA server2. Changed the MTA se...
83
Views
0
Likes
0
Answers
Re: Timezone for Delivery is 4 hr behind current time in EST SheetalAgrawalSoni - Adobe Campaign Classic
Solution :- Revert back the oracle client to match the oracle database server version and restart. After that timezone will work as expected. however while investigating we did couple things --> 1. Changed the user timezone setting on MTA server2. Changed the MTA server timezone3. on Marketing Adobe Campaign side changed user timezone4. on Marketing Adobe Campaign side downgrade the oracle client on app and web server to match the database version i.e. 12.1.0.2.05. Restarted all
73
Views
0
Likes
0
Answers
Re: Timezone for Delivery is 4 hr behind current time in EST SheetalAgrawalSoni - Adobe Campaign Classic
ACC app server , Web server and Database is hosted in our own env only mid soucring is on adobe env. So yes its hybrid, as mid sourcing server is with Adobe. Oracle database version is 12.1.0.2 and oracle client installed on app server is 12.2.0.1.0. Seems Oracle client installed on app server is little latest version but that should not be problem. isnt it ?
133
Views
0
Likes
0
Comments
Re: Timezone for Delivery is 4 hr behind current time in EST SheetalAgrawalSoni - Adobe Campaign Classic
12.1.0.2 - Database Server version
135
Views
0
Likes
0
Comments
Re: Timezone for Delivery is 4 hr behind current time in EST SheetalAgrawalSoni - Adobe Campaign Classic
oracle server database version is also 12.1.0.2
141
Views
0
Likes
0
Comments
Re: Timezone for Delivery is 4 hr behind current time in EST SheetalAgrawalSoni - Adobe Campaign Classic
yes its oracle database and i see client version is ==> Client Shared Library 64-bit - 12.2.0.1.0
151
Views
0
Likes
0
Comments
Re: Timezone for Delivery is 4 hr behind current time in EST SheetalAgrawalSoni - Adobe Campaign Classic
@amritakedia_epsilon you are right i also started seeing this after upgrade. I recently upgreded the Campaign to 9032.10 build as its gold standard and saw this issue
159
Views
0
Likes
0
Comments
Re: "Default" timezone : Updating WdbcTimeZone to ET doesn't change the delivery timezone SheetalAgrawalSoni - Adobe Campaign Classic
Did it worked for you ?  I am facing same problems 
196
Views
0
Likes
1
Replies
Re: Timezone for Delivery is 4 hr behind current time in EST SheetalAgrawalSoni - Adobe Campaign Classic
its same version but how does it matter on timezone also how did you fixed the issue ?
168
Views
0
Likes
0
Comments
Re: Is Release 20.2.1 - Build 9180 AND gold standard 9032.1... SheetalAgrawalSoni - Adobe Campaign Classic
nope. 9032.10 is gold standard and thats what you should target to update for. 9180 is not stable build.
198
Views
0
Likes
0
Replies
Re: "Default" timezone : Updating WdbcTimeZone to ET doesn't change the delivery timezone SheetalAgrawalSoni - Adobe Campaign Classic
In my case updating WdbcTimeZone options to America/New_York did not changed the system time or logs time or audit or delivery time .. its 4 hrs differenceDoes it required restart ?
199
Views
0
Likes
0
Replies
Timezone for Delivery is 4 hr behind current time in EST SheetalAgrawalSoni - Adobe Campaign Classic
Operator timezone is ESTmid source user time zone is in EST App server time zone in EDTWdbcTimeZone in options is America/New_York Still my delivery , log , time and audit log all shows 4 hrs late time.. Please help
195
Views
0
Likes
13
Answers and Comments
Re: [Release Update] Release 20.2.1 - Build 9180_July 2020 SheetalAgrawalSoni - Adobe Campaign Classic
Nope i think gold standard is 9032.10
206
Views
0
Likes
2
Replies
Re: ERROR SOP-330011 Error while executing the method 'Play' of service 'nms:delivery'. SheetalAgrawalSoni - Adobe Campaign Classic
I faced same issue long back and here are steps that you should try in lower env :- 1- Truncate table XtkWorkflowLog 2- INSERT INTO XtkWorkflowLog(iWorkflowId) values (0) 3. Go to platform > options and Set the LastConsolidated to latest date time and Pointer remove the numbers from Options settings. 4. In technical Workflow section - Restart Tracking workflow it should work ! Have fun ! Sheetal
122
Views
0
Likes
0
Comments
Re: tables involved in tracking configurations ? SheetalAgrawalSoni - Adobe Campaign Classic
I faced same issue long back and here are steps I took for tracking not working :- Here are steps or best practices to resolve the issue :- 1- Truncate table XtkWorkflowLog 2- INSERT INTO XtkWorkflowLog(iWorkflowId) values (0) 3. Go to platform > options and Set the LastConsolidated to latest date time and Pointer remove the numbers from Options settings. 4. In technical Workflow section - Restart Tracking workflow it should work ! Have fun ! Sheetal
108
Views
0
Likes
0
Comments
Re: 403 on /nl/jsp/soaprouter.jsp in ACC 9032.10 on login... SheetalAgrawalSoni - Adobe Campaign Classic
To Solve 403 Forbiddon Error Error /etc/httpd/confLogin as root Change conf. From AllowOverride none Require all denied To AllowOverride All Require all granted Restart Apache
64
Views
0
Likes
1
Answers
Re: 403 forbidden status code SheetalAgrawalSoni - Adobe Experience Platform Launch
To Solve 403 Forbiddon Error Error /etc/httpd/conf Login as root Change conf. From AllowOverride none Require all denied To AllowOverride All Require all granted Restart Apache
81
Views
0
Likes
0
Comments