Comman Run Time Errors and meaning

Run Time Error 5
Illegal function
call Program error, verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 6
OverflowProgram error
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 7
Out of memory
This issue can be caused when the computer does not meet the programs system requirements or to much memory is already being used for the program to run. If your computer meets the requirements try first reinstalling the program to make sure it's not an issues with the program installation. If this does not resolve your issue review for additional information about troubleshooting out of memory issues.

Run Time Error 9
Subscript out of rangeProgram error
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 10
Duplicate definitionProgram error
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 11
Division by zeroProblem with a math formula in the program or the programs code.
Verify no software updates are available for the program causing this error.

Run Time Error 13
Type MismatchMake
sure your system regional settings are setup correctly and that the program you're running is made for your version of Windows.

Run Time Error 14
Out of string spaceProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 19
No ResumeProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 20
Resume without errorProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 28
Out of stack space
This issue can be caused by a program or memory error.
First try going through the out of memory troubleshooting on , if this does not resolve the issue try reinstalling / updating the program.

Run Time Error 35
Sub or Function not defined Program error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 48
Error in loading DLLThis issue is often caused with a bad installation or an issue caused after another program has been installed that replaced the programs DLL.
Close all programs and TSRs and try installing the program again.

Run Time Error 52
Bad file name or numberProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 53
File not foundFile required by the program to run is not found.
Program needs to be reinstalled or missing file(s) need to be copied back to the computer.

Run Time Error 54
Bad file modeProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 55
File already openProgram or file associated with program is being used and program does not have access to use it.
Try closing all open programs and run program again. Additional information about closing TSRs can also be found on

Run Time Error 58
File already existsProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 61
Disk full The disk,
for example, the hard disk drive does not have enough space for the program to run or for associated files to be copied to. Free up disk space on the computer hard drive. Additional information about how to determine hard disk drive space can be found on

Run Time Error 62
Input past end of fileProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 63
Bad record numberProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 64
Bad file nameProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 68
Device unavailableA hardware device or necessary requirement for the program is not being found.
Verify all hardware and software required by the program is installed. If you continue to have the same issues verify the latest updates are installed for the program as well as any hardware device the program needs.

Run Time Error 70
Permission denied
The location of where the program is being copied to does not have proper rights. Or a file that is trying to be copied over because it's currently being used. Try closing all programs and TSRs and running/installing the program again. Additional information about closing TSRs can also be found on .

Run Time Error 71
Disk not ready
Verify you have proper rights to the location you are attempting to install the program to.

Run Time Error 74
Can't rename with different driveProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 75
Path/File access errorProgram does not have rights or access to a file.
Often this is caused when a program is trying to access a network file it doesn't have proper access to either because of network privileges or something is blocking the program. This issue can also be caused when the file is being used by another program or is read-only.

Run Time Error 76
Path not foundDirectory of where the program needs to be copied to or files associated with the program need to be copied to is missing.
Try reinstalling the program.

Run Time Error 91
Object variable set to NothingProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 93
Invalid patternProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 94
Illegal use of NULLProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 102
Command failedProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 339
A file is missing or invalidAn associated program file is missing or corrupt.
Try reinstalling the program.

Run Time Error 429
Object creation failed
Program is corrupted, try reinstalling the program generating the runtime error.

Run Time Error 438
No such property or methodProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 439
Argument type mismatchProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 440
Object errorProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 901
Input buffer would be larger than 64KProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 902
Operating system errorVerify the program is compatible with your version of Windows and/or has any software updates.

Run Time Error 903
External procedure not foundProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 904
Global variable type mismatchProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 905
User-defined type mismatchA setting either in the program shortcut or being defined by the user is correct. Try running just the program without any additional settings or variables.

Run Time Error 906
External procedure interface mismatchProgram error,
verify the program has all the latest updates. If updated try reinstalling the program. If you continue to have the same errors contact the software developer.

Run Time Error 1001
Out of memoryThis issue can be caused when the computer does not meet the programs system requirements or to much memory is already being used for the program to run. If your computer meets the requirements try first reinstalling the program to make sure it's not an issue with the program installation. If this does not resolve your issue review for additional information about troubleshooting out of memory issues.

Run Time Error 1025
DLL is not supported
This issue is often caused with a bad installation or an issue caused after another program has been installed that replaced the programs DLL. Close all programs and TSRs and try installing the program again.

Thanks to Mr. Navneet Devgan, System Manager

Healthy working practice on computers

Computers, as business machines, provide you with a highly powerful tool to perform various activities expeditiously and accurately. But this environment also demands you to take good care of the hardware for continued availability of the system. It also requires you to implement certain security measures to protect yourself. The following list gives you various tips for you to note and follow:

Taking care of computers

You may follow the under mentioned tips for longer life of computers and smooth functioning

Ø Keep the systems covered when not in use. The system includes the monitor, CPU, keyboard, mouse and Printers

Ø Before switching on the system, please ensure that

The UPS is switched on

No floppy is available in the floppy drive

Ø If you cannot switch the system on properly check whether the power cables are connected properly and if there are some loose ends, correct them

Ø When you turn the system on and when the windows logon screen appears, you have to type the username and password allotted to you by the system administrator, correctly for successful logon

Ø Before switching the system off, Shut down windows

Ø If you are working in Windows 2000 environment and when you leave the system temporarily, you can lock the desktop using the Windows security option

Taking care of passwords

Passwords are like keys to locks and they should be taken care of properly. Here are a few tips

ü When the system starts and you enter a windows user account and password, this is to connect to the Server and establish network connectivity

ü On logging on to windows, you may run applications like Meghdoot Point of Sale. Here also you should select a user account and type a password. This password is to permit you to run the application. Please note the difference between the two authentications and their purpose

ü The System administrator sets the initial password. Immediately on logging on, you should set your own password. You can reset Windows password as well as Application password for your user accounts

ü While setting passwords remember the following guidelines

o Use a mixture of alphabetic and number keys for the passwords

o Do not relate the passwords to your name, that of your relative or any other associations

o Change the passwords previously set, at least once in two months

o Do not reveal the password to any one else, even in case of emergency

ü Do not attempt to imagine the password of any other user and try to logon

ü The Supervisors should never part with their passwords for the sake of convenience as this has dangerous consequences.

Project Arrow - DOs and Donts

PROJECT ARROW – NEW DET SCORES

DOs

1. Meghdoot Version 6.6 with all patches to be installed in all Project Arrow Offices.

2. Use WAN wherever it is provided. Install antivirus software from avdop.nic.in and ensure that the system is connected to WAN for auto update.

3. Speednet Version 3.1.1 should be installed in all the Project Arrow offices.

4. Speednet communication module should be executed before opening of speedpost bags so that data pertains to your office are downloaded for virtual scanning.

5. Other two communication modules viz ePayment and eMO are to be executed daily before commencement of any work. Frequency for communication should be fixed according to the requirement.

6. All the transactions viz opening of bags, issue of articles, dispatch of articles are to be done only through software.

7. Unregd articles are to be counted physically. Missent articles should be counted separately.

8. All Regd bags should be opened and brought into Postman module. Missent articles should be segregated without fail before issuing to postmen.

9. All Speed post bags should be opened through Speednet module only. Issue of articles should also be done through speed net only.

10. Beat sorting of regd articles should be done accurately. Exchange of articles within the beat should be done before issuing to postmen through postman module.

11. All the MOs except VPMO should be booked as eMO only.

12. Enter correct pincode while booking of Regd articles as wrong entry of pincode will affect auto sorting in the Despatch Module.

13. Despatch of registered articles should be done only through Despatch module.

14. Printing of eMO received for payment should be done then and there and should not be accumulated.

15. Tolerance of unregistered articles sent out delivery is 0%. Hence all the unregistered articles are to be sent out through Postmen and ensure that the correct details are entered in the WEB.

16. All the unregistered articles issued to Postmen should be delivered and no articles should be returned and kept in deposit.

17. All the registered articles/speed post articles/eMO/MO should be issued to postmen.

18. Tolerance of registered articles undelivered - 5%, Speedpost - 3%, Money Order – 5%. Hence, the delivery officials should be instructed suitably. Subsequent attempts should be done by the Postmen till target is achieved.

19. Speed post articles are to be booked only through point of sale other than BNPL. BNPL articles are to be booked only through Speednet.

20. All BNPL customer details should be made available with the central server (One time measure). Then only, the number of speed post booked articles will reflect in the Speed MIS correctly.

21. Missent of speed post/registered articles are to shown in the Speednet/Postman modules before dispatch.

22. Day end should be done in all the modules according to the procedure given by the PTC Mysore before running account MIS.

23. Data to be entered in the web entry should be collected before starting entry in the web module.

24. Web data entry should be made daily without fail.

25. Account MIS should be run without fail daily after closing of accounts and giving day end in all the modules.

SANCHAY POST

26. In offices where ‘Sanchay Post Project Arrow Interface’ was installed from Meghdoot 6.6 CD uninstall the ‘Sanchay Post Project Arrow Interface’ module and also delete ‘Project arrow reports’ shortcut if available in the desktop. This should be done in all the systems in which the interface was installed.

27. Ensure that Sanchay Post Version 6.5 is installed.

28. Use DBAnalyzer to check whether you have upgraded to Version 6.5 successfully.

29. Use patchstatus.exe to ensure that all the patches available are installed in all the systems running Sanchaypost.

30. While performing day end ensure that the message ‘Day end completed successfully’ is received.

31. With respect to signature scanning

a. Use DB Analyzer with latest exe >> Go to ‘Database discrepancies’ >> ‘Account numbers with blank account status’ for ‘SB’, ‘NSS’ and ‘PPF’ and update.

b. Go to ‘Reports’ >> ‘Signatures without index entries’ >> and delete the entries after confirming that the account numbers listed are not existing.

c. In DBAnalyzer, signature scanning report display screen, click on the button 'List of accounts - signature not scanned'. Then, the account numbers for which Specimen Signature is not scanned will be stored in a file. The file generated can be opened and signatures scanned for the accounts listed.

32. The KPIs are updated during day end process without user intervention. Additionally with respect to information regarding transfers and claim cases the data is to be fed using the web based dataentry interface. In case of further queries contact SDC Chennai at 044-6585086

Don’ts

1. Do not enter number of unregistered articles received without counting. Enter actual number.

2. Do not open the speed post bag without running the speednet communication module. Virtual scanning may not nun.

3. Do not handle the registered/Speed post bag manually. Enter the details of the bags received in the module concerned without fail.

4. Do not keep any article (Unregd/Registered/Speed Post/Money Order etc) in deposit without issuing to Postmen. If any of the organization is closed due to holiday, such article only can be kept in deposit. Do not forget to send a report in this regard to Division/Region.

5. Do not accept returns from the Postman if he returns more articles than the tolerance limit. Do not hesitate to send the postman again for attempting delivery.

6. Do not dispatch missent speed post articles directly after return from Postman. Make missent entry in respect of those articles before dispatch. Otherwise, the missent dispatch articles will be taken as deposit and included in the articles not delivered.

7. Do not keep the articles in deposit which are to be returned to sender immediately. This will also be taken as articles not delivered.

8. Do not book ordinary money orders. Book only eMOs.

9. Do not accumulate the eMOs for authorization. Authorise the eMOs then and there so that eMOs are transmitted then and there.

10. Do not forget to keep the eMO communication in the active mode. Give atleast 5 minutes frequency for transmission/receiving.

11. Do not accept the bulk registered articles manually. Accept the bulk RLs only through the provisions given in the point of sale so that the articles are already available when dispatch list is prepared.

12. Do not prepare the registered list /dispatch list manually. Generate the lists for dispatch through the modules only.

13. Do not book the BNPL articles manually. Book the articles only through the provisions given in the Speednet software.

14. Do not stop communication modules immediately after giving day end. Keep the server and the client systems on, till all datas are communicated to central server.

Joining two domains ( Servers)

Domains by default are unable to communicate with other domains, which means somewhere in domain DOP1 cannot access any resource that is part of domain DOP2. Before a trust relationship is configured

(A) an administrator in DOP1 cannot give permission to any user of domain DOP2 for files or printers

(B) a user of domain DOP2 cannot sit at a workstation that is part of domain DOP1 and login

After a trust relationship is defined, say DOP1 trusts DOP2 the following happens

(A)users of domain DOP2 can sit at a workstation that is part of domain DOP1 and login to their own domain DOP2 (it will be displayed in the domain dropdown box)

(B)an administrator of domain DOP1 can grant permission to any user of domain DOP2 to file and print resources

(C)users of domain DOP2 are included in the Everyone group of domain DOP1

In the example above DOP1 is the trusting domain, and DOP2 is the trusted domain. Also the above is a one-way trust relationship, i.e. while domain DOP2 users can use domain DOP1 resources, users of domain DOP1 cannot use domain DOP2 resources. A two-way relationship would allow each domain to access resources of the other (if given permission).

The basics of a trust relationship is to first configure domain DOP2 to allow domain DOP1 to trust it, and then configure domain DOP1 to trust domain DOP2:

(1)Log onto domain DOP2 as Administrator

(2)Start Active Directory Domains & Trusts for Domains (Start - Programs - Administrative Tools)

(3)Select "the properties" of the DOP2 domain then "Trust Tab"

(4)Click the Add button to " the domains that trust this domain" box

(5)Enter the name of the domain you want to be able to trust you, i.e. domain DOP1

(6)You can type a password in the Initial Password and Confirm Password, however this is only used when the trust relationship is started. You can leave it blank Click OK to complete the addition

(7)Close the Trust Relationship dialog box

(8)Log off of domain DOP2 and login onto domain DOP1 as Administrator

(9)start Active Directory Domains & Trusts for Domains (Start - Programs - Administrative Tools)

(10)Select "the properties" of the DOP1 domain then "Trust" tab

(11)Click the Add button to " the domains trusted by this domain" box

(12)Enter the name of domain DOP2 and the password if one was configured in step 6

(13)Click OK and close.

(14)Domain DOP1 nowPublish Post trusts domain DOP2

Thanks to Navneet Devgan, System Manager Ambala