Hello-

We decided to release the SLXCustomerPortal to ISS and make it part of our extranet offerings so customers could submit tickets directly to SLX DB.  It was working great then all of a sudden it stopped working.  (We believe we deployed the portal when someone was logged in but have no way of knowing if this was the cause) We use the Sage SalesLogix portal and this one works just fine and was not affected.

In Application Architect the SLXCustomerPortal builds without any errors (build and full rebuild).  However when we attempt to deploy it using IIS… These error messages are displayed in the output:  (it then says deploy was sucessfull which it was but no login ablility)

ERROR - Unable to retrieve deployment items from deployment provider : Sage.SalesLogix.Web.AdminModule.SLXWebAccessConnectionStringDeploymentAction

ERROR - Object reference not set to an instance of an object.

ERROR -    at Sage.SalesLogix.Web.AdminModule.WebAccessConnectionConfigShadowCopyProvider.GetItems(BackgroundWorker worker)

   at Sage.SalesLogix.Web.AdminModule.SLXWebAccessConnectionStringDeploymentAction.GetDeployableItems(PortalApplication portal, BackgroundWorker worker)

   at Sage.Platform.Deployment.PortalDeploymentManager.<>c__DisplayClass7.<GetPortalDeploymentItems>b__5(IDeploymentActionProvider provider)

I have deleted the IIS site and attempted to redeploy it again and the noticed the connection.config file did not carry over/exist.  When I tried to access the site it told me this.  I then attempted to copy it from the SalesLogix Client (working portal) the error goes away.  I then get the this error message appears when we attempt to login: 'Your login attempt was not successful. Please try again.’  This is the original error message we were seeing after the first redeploys above.

I then had a backup copy of the SLXCustomerPortal (C:\Devel\ProdVFS\Model\Portal\SLXCustomerPortal) from yesterday (3/9) when this portal worked fine and I attempted to restore this and rebuild/deploy.  This generated the same ‘Login attempt failed...’ error message.

I have restarted IIS service numerous times.  I have not tried a reboot since this is a production server.  I am near the point of uninstalling and reinstalling the Application Architect but realize Sage bundled all of these together in the: SLX Admin Tools and Services.  This is not worth a complete reinstall of the server...  I have yet to try a reboot but may try tonight.  It appears restoring the connection.config file is key and do not believe a reboot would fix a missing file.  Any ideas how to add the connection.config  back again and deploy it?  Any other ideas how to resolve error messages?  Any ways to nicely remove Application Architect and rebuild it from the ground up?  I am willing to reapply the 3 hotfixes needed to make the WebClient work in the first place. 

Thanks for any assistance you can offer.

• Did you set the SLX Account you want to use for Customer Portal in AA?


• Check your connection.config file in the Customer Portal deployed site.  There may be password garbage in it.

Thank you Phil.

Connnection.config file is now present...

I know what happened... I thought 'oh I dont need the CustomerPortal user anymore in SLX Admin after I setup it up' only to realize you do...  Rebuilt the application in AA connnection.config magically appeared and it all played nicely.  Always the obvious items after a few hours to troubleshooting.

Now for some reason it is no longer externally facing but this could be a different issue... can each of these portals be on the same port: 3333 in our case?

Thanks once again.

Yes, they all can be on the same port.  If you need it on a different port you can set that up in the Deployment Manager (if on the same IIS Server, you'll want to create another Web Site using that port).