Hey Kiran I found the idea! look there... it's result that mistake I have:
This Result By Debugger MySISFileInstall.com
Package Name: Zero
Vendor Name: Zero 6630
Package UID: 0x20006FDF
Capabilities: ReadDeviceData, NetworkServices, LocalServices
Install Type: Standard Application (SA)
Signing Status: Signed
"Signed" means that your SIS file has been through Symbian Signed, or some other equivalent manufacturer signing process (or is signed by a dev cert, which is much the same.) A signed SIS file can make use of capabilities that are not available to a self signed SIS file.
Note: The process this tool uses to determine a SIS file's signing status is not guaranteed 100% accurate, it may be properly signed, but this tool may detect it as self-signed.
Warning: Package UID is also used as a SID!
One (or more!) of the executables this package contains has the same Secure ID as the package UID. While technically allowed, and commonly done this is a stylistic mistake. The package UID and executables Secure IDs are different things. A SIS file only has one package UID, but may have several executables, each with a unique SID.
The offending executables are:
please read The Warning Message then clear for me what the mistake I have, then tell me what I do after..Ok!