Host server name change - clients no longer can open DB

[Melagan]

Greetings once again,

For reasons too long to list, the network admins in my company decided to change the names and ip addresses of all of our domain controllers, one of which hosts a shared ACT database. I can open the database when on the server itself, but not on any of the remote workstations.

I have even edited the .PAD file to reflect the new host name. Is there something else I can do to help accomodate this change - or do I need to create a new database and import all of the data from the old one?

<?xml version="1.0" standalone="no"?>
<!DOCTYPE ACTDatabasePADFile>
<!--This file represents a Pointer to an Act Database or [PAD]-->
<ACTDatabase name="FRESNO" host="CA022AFP" location="U:\ACT\NATC_Fresno" type="Sql" />

New host name = CA022AFP
Old host name = CN55601DC

..perhaps something in SQL management? I havn't a clue - appreciate any help!


~Melagan
______
"It's never too late to become what you might have been.

 

[GLComputing]

1. I assume you have followed the details as per:

http://kb.sagesoftwareonline.com/cg...1tYWNoaW5lIG5hbWU*&site_ID=&p_li=&p_topview=1

2. Where is the U: drive located?

3. What is the actual error you are getting?

Regards,
Mike Lazarus
ACT! Evangelist
GL Computing, Aust

http://www.GLComputing.com.au

 

[Melagan]

Error message:

"Cannot find database supplemental files folder FRESNO-database files in this loaction CA022AFP. This could be a problem with the share, or the folder may not exist. Please contact the administrator of your database."

The U: drive is a network share on the CA022AFP server. The physical location on said server is D:\Everyone. The physical location of the ACT database on the server is D:\Everyone\ACT\NATC_Fresno.

I have worked through this article - the Pad File Issues section is the most applicable. I have already checked with database sharing, file/print sharing, and folder security.

http://kb.sagesoftwareonline.com/cg...zdXBwbGVtZW50YWw*&site_ID=1&p_li=&p_topview=1

The only thing I have NOT done at this point is changing the naming method at the shared database. The ACTDiag tool kicks out a long cryptic error message when I try to access the "ACTION" menu; I'm hoping a reboot of this server will help, but I can not do that for about another hour =)

~Melagan
______
"It's never too late to become what you might have been.

 

[GLComputing]

You might try this... rename the PAD file from the server and in ACT! - File | Open and open the ADF file. This will recreate a PAD file on the server.

Copy the new PAD file to the workstation.

Regards,
Mike Lazarus
ACT! Evangelist
GL Computing, Aust

http://www.GLComputing.com.au

 

[Melagan]

Aye - I did try to both edit an existing PAD file and create a new one using the method you suggested. It did not solve the issue. I can open the database on the server itself, but again, none of the remote workstations can open the database.

~Melagan
______
"It's never too late to become what you might have been.

 

[GLComputing]

Try having a look at Knowledge Base Article ID 14101

http://kb.sagesoftwareonline.com/cg...JjaF90ZXh0PTE0MTAx&site_ID=&p_li=&p_topview=1

Regards,
Mike Lazarus
ACT! Evangelist
GL Computing, Aust

http://www.GLComputing.com.au

 

[Melagan]

After all of this - I believe it turned out to be something simple. When I went to use ACTDIAG.EXE to change the naming method from 'machine name' to 'ip address', I was made aware that the database was not shared. (The database must be shared in order to use this feature).

Sure enough, under tools/database maintenance, sharing was not enabled. For some reason when the server was renamed and given a new IP, the database was no longer shared. I sure didn't disable it myself =)

Anyway, having re-shared the database, it seems to be working fine now.

~Melagan
______
"It's never too late to become what you might have been.

 

[Melagan]

By the way, Mike, thanks again for helping me research this stuff!


~Melagan
______
"It's never too late to become what you might have been.