At a company I work for we recently had to downgrade from the 64 bit version of Microsoft SQL Server 2005 back to the 32 bit version (long story ). After removing the 64 bit version of SQL Server and installing the 32 bit version and then recreating the master db and setting up all of the databases again, Optimum no longer worked correctly. I could log in fine, but whenever I tried to open up Employees, or just about anything else, I got a big nasty error message saying “you must declare the scalar variable @USERID”. Read on for the solution to the problem.

Getting Syspro e.net Business Objects to work remotely from a non-Administrator account can be tricky if you’re not familiar with DCOM. Syspro has some general instructions in their Support Zone, but they are missing a couple of steps for Windows Server 2003. Below are the steps I used to configure DCOM for Syspro e.net Business Objects in Windows Server 2003.