You can set the value of property bulkemailmid_tracking_optout_url  via SAS Management Console --> Application management-->Configuration Manager-->SAS Application Infrastructure-->Digital marketing WebStudio SDMversion to the desired valid html link (for ex. http://www.YourCompanyDomain.com/YourOptout.html) and rebuild and redeploy bess by running the config wizard.   Or else  make change to web.xml of tracking tier application (bess) and restart the mid-tier server. Parameters redirect should be set to true and redirect_link should be set to appropriate value.         <servlet>             <servlet-name>optout</servlet-name>             <servlet-class>com.sas.email.servlets.OptOut</servlet-class>               <init-param>                   <param-name>redirect</param-name>                   <param-value>true</param-value>             </init-param>             <init-param>                   <param-name>redirect_link</param-name>                   <param-value> http://www.YourCompanyDomain.com/YourOptout.html</param-value>             </init-param>             <init-param>                   <param-name>sync</param-name>                   <param-value>true</param-value>             </init-param>             <load-on-startup>1</load-on-startup>       </servlet> ... View more

Have you engaged with SAS Tech Support on this issue? If not you should as only they can do a full diagnostic exercise to find the reason(s) for your problem. We had a similar problem with our SAS VA platform and that is what we did to fix it. ... View more

No, sas = dot_sas sassrv = dot_sassrv   Yes, i have the user in metadata:   Like i said earlier, same metadata is used for other SAS software running on different server (Campaign Management) and servers there start just fine. But for some reason VA server cant autenticate dot_sassrv user.   I did authentication check as said in this note http://support.sas.com/kb/39/891.html for user dot_sassrv. On metadata server it was ok: 20190618-09:25:28 Authenticating user dot_sassrv via pam 20190618-09:25:28 KRB5CCNAME was not set; we'll see if something happens later 20190618-09:25:28 Processing message 1 of 1 20190618-09:25:28 PAM prompted for hidden input; assuming it wants a password 20190618-09:25:28 Prompt text: Password: 20190618-09:25:28 PAM conversation succeeded 20190618-09:25:28 pam_setcred: explicitly reinitializing PAM credentials 20190618-09:25:28 Getting user's group memberships 20190618-09:25:28 User dot_sassrv in 1 groups. 20190618-09:25:28 Authenticated user dot_sassrv (pam).   On VA server it failed: 20190618-09:39:10 Authenticating user dot_sassrv via pam 20190618-09:39:10 KRB5CCNAME was not set; we'll see if something happens later 20190618-09:39:10 Processing message 1 of 1 20190618-09:39:10 PAM prompted for hidden input; assuming it wants a password 20190618-09:39:10 Prompt text: Password: 20190618-09:39:10 PAM conversation succeeded 20190618-09:39:11 Processing message 1 of 1 20190618-09:39:11 PAM wanted to tell us some information: Account locked due to 119 failed logins 20190618-09:39:11 PAM conversation succeeded 20190618-09:39:11 Processing message 1 of 1 20190618-09:39:11 PAM prompted for hidden input; assuming it wants a password 20190618-09:39:11 Prompt text: Password: 20190618-09:39:11 PAM conversation succeeded 20190618-09:39:13 pam_authenticate failed: Permission denied 20190618-09:39:13 User dot_sassrv did not authenticate. Reason: 'Permission denied' (pam) 20190618-09:39:13 Request failed: 'Permission denied'   The user is LDAP user, i can log on with him to linux (VA server). I dont understand how is could be locked as said in the log. Are there any other credentials saved somewhere for VA server?   ... View more

When i go to Tools - Server Configuration - Advanced Server Properties and try to change something, i get following messages. (second message show up right after the first one).    The changes i made are apparently saved, but what bothers are the errors. Which could have something to do with why tracking isnt working.  I couldnt find any leads on this "crumblet URL" or "tracking tier".   Any ideas?   Lukas ... View more

We would suggest contacting technical support on this issue. Please open a ticket or contact directly here https://support.sas.com/en/technical-support/contact-sas.html or you can also email support@sas.com and include your screenshots.  ... View more