Search results for query: *

Did you find other directions besides the one you linked to in your first post? I'm in the process of moving our database and app to a new server, which I've done in the past but it was years ago. Trying to plan the best approach.

I've always thought that you were supposed to do the install from a workstation, which would mean that it wasn't able to install anything into the registry? Can you not just transfer the macsql folder to the new server?

I tried opening the file w/ Crystal and got an out of memory error. Same thing with notepad. I'll try renaming it and see if I get any errors over a the next few weeks.

I'm in the process of migrating our SQL server and Macola install into a VM. I'm working through fresh installs instead of doing the P2V. So far it's going rather well, hopefully that is still the case in a few days when I finish.

I have a file (pwe.rpt) in my MacSQL share that is sitting at 4gb in size. Is it safe to delete this file? I've tried searching but came up empty. Is this really just a report file?

I wanted to test a scenario so I re-enabled the old MACSQL share on the first server and now that it's opened back up users are able to login.

I remember now why I was using the 2000 disc to do the install is because the 2005 discs where for 64bit so I wasn't able to install the connectivity tools from them on our 32bit workstations. I hunted around the microsoft site for a download but was unsuccessful (I'm not even sure this is a...

We're running SQL 2005, I just checked the SQL Native Client Configuration and we have both TCP/IP, Named Pipes and Shared Memory enabled. VIA is disabled. The client is set to use TCP/IP to connect. The clients are all using the SQL Server Client Network Utility that was installed off the...

I had found that same document and tried shrinking the screens log file. The beginning file size was 2.5mb and the shrunk size was 1.5mb. Neither of these seems large to me but I maybe wrong. I also tried deleting the ODBC connections but was unable to get the client logged in after numerous...

It looks like using Progression Explorer lets the user in when PWE doesn't. Explorer still seems to be slow opening modules but you're able to get into macola.

After the user is logged in there is still some significant slowness. We also use Goldmine and it's running against the same SQL server without any performance issues.

Yes, we migrated all of the "data" databases as well as the screens db. I've also checked the the users to make sure they have the correct permissions for each database. In the same migration we also upgraded from SQL 2000 to SQL 2005. We're currently running Progression 7.6.400a and Flex...

We have a very similar situation in which we migrated our Macola Progression install from one server to another. Now we have been running into long load times and login errors. The main error we get is: Error occurred during database connection:-2147217871 After saying "OK" to that message...

Yes, I have TCP/IP installed on the SQL server as well as Named pipes. To explain the 64bit issue. We have install disks for SQL 2005 64bit edition but these disks will not run on our workstations to allow us to install the latest connectivity tools. I've tried to search for a download of the...

Ok, I've got an update on this issue which is still occurring randomly on various workstations. A list of things we have tried include switching NICs on the server, replacing all cabling between the server and the main switch closet (which was working fine prior to the upgrade but to be...

On some of the computers there were no Alias' setup. I thought I had read that they weren't needed. I have setup a new alias to point to the server and use TCP/IP. Does Macola require Named Pipes?? Should I have setup the alias to use those instead or should I setup a second alias for named...

We have recently migrated our Macola install to a new server and upgraded to SQL 2005. The move seems to have went fine with the exception of an error we receive on various workstations. ***Begin*** The following error has occurred in MacMSS.dll: [DBNETLIB][ConnectionWrite (send()).]General...