11/25/2024 4:22:03 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss SalesLogix synchronization and remote database management. View the code of conduct for posting guidelines.
|
|
|
|
Remote Office Down! Problems after recut - urgent! Invalid object name 'SYSTEMINFO' error
Posted: 31 Dec 06 10:48 AM
|
fiogf49gjkf0d I just recut a remote office and move the .sxd to the remote office db server. The first problem I have is that the attach remote tool won't give me a choice as where I can install the remote db - always installs to C:. I need to put it on D:.
Can I use the SQL server tool to attach the remote or is there another work around?
My second, more urgent problem is that when I get the DB attached and try to login to any of the clients, I get an {Invalid object name 'SYSTEMINFO'} error.
I desperately need help on this and cannot contact tech support until Tuesday. Any help greatly appreciated. Thanks
Steve K. |
|
|
|
Re: Remote Office Down! Problems after recut - urgent! Invalid object name 'SYSTEMINFO' error
Posted: 31 Dec 06 12:21 PM
|
fiogf49gjkf0d Steve,
Yes you can use SQL Attach to attach the database. If you go this route, you will need to run the fix_sysdba.sql script after you attach the database.
BTW, if you create a shortcut for the AttachRemote and add a " \admin" at the end of the shortcut AttachRemote will attach the database without moving it to the default MSSQL data folder. You could also modify the MSSQL folder option.
It sounds like the remote office database may not have been created properly --the system may have run out of some resource. Try rebooting the system then recreate the database.
When was the last time you were able to create and attach the remote office database? |
|
|
|
Re: Remote Office Down! Problems after recut - urgent! Invalid object name 'SYSTEMINFO' error
Posted: 31 Dec 06 12:41 PM
|
fiogf49gjkf0d The last time we recut and attached the remote was probably over a year ago. We had it running fine after the v7 upgrade except one of the mailmerge tables was missing. So we decided to recut since it had been so long..
We are trying a recut. Thanks for the advice Frank. I hope the recut does the trick.
Also found this in the SLX KB - we'll give this a try also:
"Connection Failed: Invalid Object Name "SystemInfo" error when upgrading to 6.2
Entry Type: Informational
Product: Sage SalesLogix
Application: Administrator
Version Reported: 6.2
Description:
When upgrading to 6.2, the following error displays:
"Connection Failed: Invalid Object Name "SystemInfo"
Possible Resolution 1:
In the conversion utility, verify that the sysdba login and password are being used. In addition, ensure that proper ownership of the database has been assigned.
1. In Enterprise Manager, select Security / Logins / sysdba
2. Right-Click and select 'Properties'
3. Click the 'Database Access' tab
4. Select 'Permit in database' role
5. Confirm that public and db_owner are selected
Possible Resolution 2:
Disable all database triggers and set the database recovery mode to simple. For instructions please review the following article: How to disable database triggers and set the database model to simple (default)
If I resolve I'll post for reference puroses. thanks |
|
|
| |
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|