USB Printing for Meghdoot Millennium

Meghdoot Millennium Applications Software’s Support USB Printing.
 Most of us are not aware of this . Some of the servers available with
 Post offices only support usb printing. They does not have LPT1
 or COM Ports.Yesterday in one of my office solved this USB printing problem with a simple tweak.

For USB Printing

To enable USB Printing for Meghdoot Applications. First Install
 the printer with USB port. We can select the port by arrow
 keys while installing. Or we can configure the port after installation of printer in LPT.

eMO Client Error??? Error no 701 Login failed for user NRega

While running the emo client in update 5 and 6 an error or message occurs. It shows that "Cannot open database requested in login NREGAEMO. Login failed for user NREGA". While sending this error . The solution provided by CEPT mysore is given below.

Click here to download solution
Unzip the file and copy it to DBAnalyzer folder and run it from the same location. This will solve your problem.

NB. Please backup the database before running the solution

Repair Suspected Database

Repairing Suspect SQL Database

I'm not a DBA but I have a real life experience repairing a suspect databases twice. I guess I can say that I was unlucky at that time as I was presented in a tough situation where I was still in the process of learning how things work and we didn't have a DBA resource (remember I am a developer), but still consider it lucky as even some experienced DBAs might not have even experienced this situation. I experienced a similar situation before, and restoring it was easy before as we have, but that was easier as I have the proper restore points.

Now in this situation, the backups had failed so the last clean backup we had was 2 weeks old, so I could only rely on that one plus the current transaction log which is not backed up for now. So the first thing that came to my mind was to backup the transaction log so I could easily restore the full lot. I tried to backup the transaction log, but I had to remove the suspect status first by running this TSQL:

Collapse | Copy Code

sp_resetstatus 

Now it was not a suspect anymore, I was hoping to run the backup of transaction log by using this TSQL:

Collapse | Copy Code