LMS4.2 sending out 2 set of report link & server name

Question

2 set of link report( different module) was sent from LMS , but only 1 set of them is opening.
The server name had not changed since LMS 4.2 was setup for about 1 month.
the working set#1 link:
http://LMS:1741/rme/changeAuditJobDetails.do?button=details&jobid=1050&instanceid=22
below the set#2 link that is not working:
http://LMS.na.abc.com:1741/cmapps/utReportJob.do?crosslaunch=dashboard&reportID=1000.2
http://LMS.na.abc.com:1741/cmapps/utReportJob.do?crosslaunch=dashborad&reportID=1010.14
It seem that the server name appear as" LMS.na.abc.com"  in the Campus module report.
and in the DCR Device Polling job (DCRDevPollReport) DCR unreachable Device report.
but Server Name " LMS41" from RME link report.
We notice any link with set#1 type works, even if we edit the set2 link manually , it works.
ie both " LMS " and  " LMS.abc.com " will work, but not " LMS.na.abc.com"
Is there anywhere we could edit the link that is being send out by the report.?
Does hostname change script command works ( no actual hostname changes so far)?

Answer 1

Hi,
DBNetLib (Database Network Library) errors occur when the BizTalk Server runtime is unable to communicate with either the MessageBox or Management databases. When this occurs, the BizTalk Server runtime instance that catches the exception shuts down and
then cycles every minute to check to see if the database is available.
Check if there is any server restart activity happening every night?
Alternatively, you might need to
Set the SynAttackProtect registry setting as described in
http://support.microsoft.com/kb/899599. Additionally,
look at the Group policy for that SQL server to be sure that the Group Policy does not periodically UNDO the setting change that you did above.
Refer:
[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
Other possible causes could be
1) Low hardware specs (Could be hard disk memory issue, check the free space on the server)
2) Sharing one server or disk for more than one group of BizTalk databases
It could also be a network card issue that could we worked around by turning off TCP Chimney using the following command:
Netsh int ip set chimney DISABLED
For more information, see
Microsoft support article 942861.
Refer for details:
Avoiding DBNETLIB Exceptions
Similar issue reported here ->
BizTalk service stopping automatically.
Also refer this link and look into the description of Error 6,10 and 11.
BizTalk - Errors and Warnings, Causes and Solutions 
Rachit
Please mark as answer or vote as helpful if my reply does