You may want to monitor the SQL memory usage at session logon - you may be experiencing the initial load of required table data and perhaps sql procedures into memory.
If that is the case, you can either live with that or attempt to pre-load some of the common security and module master tables...
Are there any related log entries in the server system or application logs when the queue crashes? Is there any indication of whether it's crashing due to system or pervasive error conditions/messages?
Is the queue actually abending or does it just hang?
Lloyd Freiday
Sounds like your close to a solution here.
Is it safe to assume that you installed SQLBase on the other client systems that are experiencing the same issue?
You could run SQL setup and choose to install the client tools again. This should either repair or replace the SEM on the client. It...
The product CD used to contain the Magic table def's that could be imported into Magic. I'm afraid I don't have the export file myself :-(
Lloyd Freiday
With the eBackOffice financial apps, the dates are stored in SQL as julian dates. The application uses two sp's, appdtjul_sp and appjuldt_sp to convert between gregorian and julian dates.
The essence of the conversion that you can paste into a SQL stored proc or trigger is this:
[color...
I can't think of why that wouldn't work for you. I checked it on my SEM to confirm and it is saving the last position in the tree and displaying the taskpad view for that database ok.
I guess you should make sure that visit the DB's you want to have the taskpad view on and select that view...
You might want to try and reset the logon account/password for the sqlserveragent service and restart on the SQL7 box. Then reset the service startup account via SEM for the 'SQL Server Agent' to the same account and password.
Afterwards, set the Mail Session profile and test from the same...
There are a couple of things that may help you out.
First, find the shortcut to Enterprise Manager and check the properties. The target should be something like C:\WINDOWS\system32\mmc.exe /s "C:\Program Files\Microsoft SQL Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC"...
I would propose that you work from a workstation and not the server where the files exist. What version of Btrieve/Pervasive are you running? Do you have the server engine installed or are you just using local workstation engines to access the shared data files?
Depending on the version of DB...
Your going to need an ODBC driver for Pervasive(Btrieve) to begin with. Once that is installed, you will need to have the .ddf file(s) for the version of PFW you are running. Then you can create your ODBC connection using the Pervasive driver, pointing to your data folder and also to the .ddf...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.