Service Pack: COM Exception Error

When updating Erasoft modules & databases, sometimes supports encounter error message stating COM Exception when accessing the Service Pack menu on SM module.

As solution, you just need to re-register the sqldmo.dll.

Here's the step-by-step:

1. Run the command prompt as administrator.

2. Depends on the OS version, you should redirect the directory to C:\WINDOWS\SYSTEM32 (for 32-bit version) or C:\WINDOWS\SYSWOW64 (for 64-bit version). You can do this by using cd.. & cd windows\system32 or cd windows\syswow64.

3. Once on one of the mentioned directory above, type this command regsvr32 sqldmo.dll & hit enter.

Location: Jakarta, Indonesia

Comments

Post a Comment

Popular posts from this blog

DM & RM License Renewal

Image
Dashboard Management (DM) & Reminder Management (RM) modules are part of maintenance contract. These particular modules have its own activation license separately from the HASP dongle. The license has 1-month validity & applies on both modules. As maintenance support, it's your responsibility to renew the module license once a month for each clients. Though the renewal can be done online, sometimes, for particular reasons, it might fail. The solution is offline renewal which requires a flashdisk with 4GB as minimum size. Here's how you can prepare the flashdisk: 1. Quick format the flashdisk into NTFS format & rename it as ERA. 2. Plug in the flashdisk onto the web server. 3. Login into DM module. 4. There will be a file inside the flashdisk (appengine.bin) if you're doing it right. 5. Remove the flashdisk from web server & bring it to the office for further processing. Actually, you can renew the license without bringing back the flashdisk to office. But, i
Read more

Missing SQL Server Configuration Manager

Image
  In case SQL Server Configuration Manager missing from Start Up menu, you can always access it using Run command (press  W + R)  as shown below, then type in sqlservermanager14.msc & press enter. It happens after you install a service pack on SQL Server. I've only experienced it when using SQL Server 2017. This problem never occured to me when doing service pack on SQL Server 2012. For other SQL Server version besides 2017, you can check the detail on this link .
Read more