Hello, We are facing a problem regarding DSO server reference. We are using DSO action in a filter STM:HelpDeskDLHHP060 with option Distributed Transfer. We are putting mapping name=STM:HelpDesk1DLHHP060, Server=dlhhp060.dlh.st.com, Form=HPD:Helpdesk. We are also making Distributed Mapping STM:HelpDesk1DLHHP060 from server del08mis.dlh.st.com to dlhhp060.dlh.st.com for HPD:Helpdesk form. Mapping was saved correctly with server dlhhp060.dlh.st.com.
Server dlhhp060.dlh.st.com is using temporary DSO license with type Demo. While putting ticket on del08mis.dlh.st.com server. The ticket is going correctly on dlhhp060.dlh.st.com server also. But while after closing filter and again opening filter STM:HelpDeskDLHHP060, mapping name has been changed by itself from dlhhp060.dlh.st.com to del08mis.dlh.st.com (current server name). Same is happening for other filters while we are making reference for dlhhp060.dlh.dt.com server. This field value has either changed to the current server name or become blank. We are saving filters and all with user Demo which is also available on dlhhp060 server. Though the filter's reference was overridden by mapping reference in this case. But we are also using some direct reference by filter while using option Distributed delete. In this case after saving server name value in filter with Distributed Delete and closing and again opening we found server value NULL. DSO instance on server DLHHP060.DLH.ST.COM is up. Could you please suggest why other servers (eg. Del08mis.dlh.st.com) are not saving the reference name for dlhhp060.dlh.st.com server ? Does temp DSO with type Demo create problem ? Please share. Regards, Tarun 199-6082 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
