INSTALLATION
SYSTEM
INSTALLATION
 I
installed netVESPA and netSystems before installing MSDE, do I have to repeat
the whole installation?
If you have rebooted the
PC after the MSDE install, you should be able to connect to
the netVESPA and netSystems databases by opening netVESPA and netSystems Database Administrator
and clicking the ‘Reset Databases’
I
have installed MSDE but when installing netVESPA and netSystems, I receive
a message saying that it cannot detect SQL Server running?
You may have to reboot the PC after
the MSDE install to get the service running, otherwise you
may Run the Service Manager now installed in your Startup
group and start the MSSQL Server. Under NT4, Installshield
may not be able to detect the service running; if you can
confirm that it is you may go ahead with the install.
The
MSDE install appears to be failing: it runs through the install,
but near the end the progress bar goes backwards and when
I look it does not appear to be installed. I am using Windows
2000.
We have found that the File and Printer
Sharing for Microsoft Networks component needs to be installed,
though not necessarily enabled. Check your Network Properties
for the Local Area Connection; if File and Printer Sharing
is not on the list of installed components, click Add, Service,
then File and Printer Sharing for Microsoft Networks. Once
done, repeat the MSDE2000 installation.
I
have installed netVESPA and netSystems Solo to a network drive and now the
program will not run.
MSDE cannot operate across a network
drive; you must install MSDE on the file server where the
network drive resides. Once done, open netVESPA and netSystems Database Administrator
and click the ‘Reset Databases’ button.
I
installed 7.4.x once, with no problem, but then re-installed
into a different folder name/drive and now netVESPA and netSystems will not
start. I can see my databases in netVESPA and netSystems Database Administrator,
but when I click ‘Reset Databases’, nothing appears
to happen.
There is a conflict between the database
directory set by netVESPA and netSystems and that being resolved by MSDE.
Uninstall MSDE, reboot, re-install and reboot again. Finally,
return to Database Administrator and click the ‘Reset
Databases’ button to register the databases
I
get a message stating that “netVESPA and netSystems had problem during
startup; there may be missing databases” yet the program
appears to be running normally.
There may indeed be databases referenced
in the master that do not exist in the new installation, the
most likely being ExaPST00 and CompDemo, both former example
scenarios that are no longer included or supported. Use the
Open dialog in netIPT to identify and remove the scenarios
that are no longer present in netVESPA and netSystems.
I
have heard much about the W32.Slammer worm, does the version
of MSDE2000 you provide protect against it?
By default, netVESPA and netSystems installs the SP2 version
of MSDE2000, but we have provided the SP3 update on the CD
as well. This should be suitable for most Windows systems
and fully protects against the Slammer worm.
I
receive a message towards the end of installation ‘Could
not register the netVESPA and netSystems service’ (netVESPA and netSystems Server
only).
The previous version of the service has
not unregistered, however, as the path and filename of the
new service are identical you should find that netVESPA and netSystems would
run normally. If this is not the case then please phone Magenta netLogic Support for instructions on how to register the service
correctly.
The
netVESPA and netSystems server is not starting up but I am getting no message
to indicate what is wrong. How can I see the problem?
Stop the server (you may need to reboot
the machine if the server does not respond, and open the Trace
utility in the Start, Programs, netVESPA and netSystems group. Then from
the file menu, choose ‘Start netVESPA and netSystems debugging’.
This will provide a debug output including the error message.
Save the contents of the Trace window to a text file and email
to support@magenta-netlogic.com
for a diagnosis and solution.
SYSTEM
Why
is Win 98 no longer suitable to run netVESPA and netSystems Solo?
Since the upgrade to SQL database engine,
the hardware requirements for netVESPA and netSystems Solo have increased.
Most corporate desktops or laptops running Win 98 are legacy
systems and no longer able to run netVESPA and netSystems at a reasonable
speed. In addition, the MSDE2000 server requires a stable
operating environment, with applications run in separate memory
space. Win 98 cannot realistically provide such an environment,
so we now insist on a corporate operating system, such as
Windows 2000 or XP, to run our corporate application.
There
is an error during start-up. The Trace utility has been run
and the following error returned: ‘ADO Error: [SQL Server:
\\STC8][42000] Cannot open database requested in login 'mlmaster'.
Login fails.’
The permissions on the database folders
are too restrictive. MSDE2000 generally uses the System account,
but on a netVESPA and netSystems for web server, the Internet Guest Account
also needs access to databases within the Accprice folder
in order to validate user names and passwords. As users data
is also written to one of these databases (admin), permissions
must be extended to the Internet Guest Account to include
at least Read, Write and Execute. For a full list of permissions
required for all versions of netVESPA and netSystems, please see the netVESPA and netSystems/netIPT
System Administration document, or request a copy by emailing
your requirement to support@magenta-netlogic.com
What
is this netsolve_Detached folder on my system?
Under SQL Server, you cannot simply copy
databases around in Windows Explorer, as in previous versions
of netVESPA and netSystems, databases have to be detached from the server
then copied out using the netVESPA and netSystems Database Administrator.
The Detached folder is merely a storage area designated by
the installation. You may choose your own storage area if
you wish.
|
