MSH2 Well-known problems

- Setup - Well-known problems
S1. the All-In-One setup package didn't install the requirements correctly
S2. the shortcut to CreateDb.bat from start menu returned message alert
S3. upgrading MSH2, CreateDb.bat doesn't create new DB

- Configuration - Well-known problems
C1. console message: CPA not found

- Run - Well-known problems
R1. the client is not able to receive the message
R2. the message is sent but it doesn't arrive
R3. the sent message is disappear

Setup - Well-known problems

S1)
Problem:
the All-In-One setup package didn't install the requirements correctly.
Cause:
May be there are old versions of software requirements
Solution:
Remove eventual old versions of requirements.
Install manually the requirements one by one in this order:
- dotnetfx\dotnetfx.exe;
- DB_Create\CreateDb.bat;
- install the MSH2 standard package (see Setup page).

S2)
Problem:
the shortcut to CreateDb.bat from start menu returned these message alert:
---
Alert!
Symantec Script Blocking has prevented a script action that could be harmful to you.
Application: WScript.exe
Source file: C:\Program Files\MSH2\DB_Create\CreateDb.vbs
Object: Windows Script Host Shell Object
Method: Run
---
or/and
---
Windows Script Host
Script: C:\Program Files\MSH2\DB_Create\CreateDb.vbs
Line: 14
Char: 2
Error: Object doesn't support this property or method: 'Run'
Code: 800A01B6
Source: Microsoft VBScript runtime error
---
Cause:
An antivirus blocked the script execuxtion.
Solution:
launch manually and directly the file from his location:
(f.e. C:\Program Files\MSH2\DB_Create\CreateDb.bat)

S3)
Problem:
Upgrading MSH2, CreateDb.bat don't create new DB.
Cause:
There is an old version of DB "MSH2" with different structure.
Solution:
Remove the old DB data files. Launch CreateDb.bat again.
(for example:
C:\Programmi\Microsoft SQL Server\MSSQL.1\MSSQL\Data\MSH2.mdf
C:\Programmi\Microsoft SQL Server\MSSQL.1\MSSQL\Data\MSH2_log.LDF )

Configuration - Well-known problems

C1)
Problem:
Tryng to send a message to MSH2 returns this message in the his prompt:
---
18/09/2008 12.09.15 - CPA not found, file
"C:\Program Files\MSH2\CPA\CPA_DE-98765432101_IT-12345678909_0000-00-00.xml" missing
---
Cause:
There isn't a CPA related to outbox message.
Solution:
Check the recipient PartyId both in the message file name and in the CPA file name.
Note: The CPA retrieving from PartyId is case-sensitive.

Run - Well-known problems

R1)
Problem:
the message is sended by Party A, it is on mail server, but MSH2 of Party B is not able to receive it.
May be there is AVG Antivirus on workstation of Party B, the program has an "e-mail scanner" feature that before to do the message download parses the message and it adds, in the message envelope the follow string message:
---
Content-Type: multipart/mixed;
boundary="=======AVGMAIL-47BEEB896F72======="
--=======AVGMAIL-47BEEB896F72=======
Content-Type: Multipart/Related; boundary=MIME_boundary; action=ebXML; start="ebXMLHeader@bologna.enea.it"; type="application/soap+xml"; charset=utf-8
---
Cause:
The added string lines don't allow the correct working of MSH2.
Solution:
Disable the "e-mail scanner" feature in the AVG Antivirus program.

R2)
Problem:
The message is sent but it doesn't arrive.
Cause:
The message is probably on the web server but MSH2 can not receive it because there is a collision of ebMS, SimpleMail subjects.
Solution:
Check the subjects of the two ways to receive messages:
1. ebMS (Options > SMTP & POP > ebMS subject)
2. SimpleMail (Options > SimpleMail > Email subject)
Both subjects have to be different.
Each subject does not have to contain the other.

R3)
Problem:
The message is sent, it was on the web server, MSH2 did not receive it,
and now the sent message is disappear!
Cause:
Some web mails (like gmail) move the message in another place when a SMTP client like MSH2 read it but then does not download the message (see R2 case).
Solution:
Check in the folders of web mail (for example, in gmail, "All messages" folder).
See solution of well-known problem R2.

Contact the administrator to signal a new problem/error.