Re: [foxboro] configuring AIM* to get data from external fdb database file

Dear Alex,

Thank you for your suggestion,

I verified the read only tag on the backup files, there were some in read 
only mode. I put them in R/W mode.

After doing this check I got the same errors.

Then I put in shared mode the partition (D:) of the backup PC where are 
stored the fdb files.

I ensured I could access, read and modify the files from the AW70.

In this way I should not get access rights/security problems.

After modifying the DBPATH parameter as DBPATH=d:\opt\aim\inst;\\backup\d I 
am still getting the same error for each file:

 Historian hist01 Createfile r9087.fdb errno=1326 logon failure unknown user
 name or bad password



I have tried also what you said me, to put some files in a local folder and 
modify the DBPATH according to it. This seems to work but I do not have 
enough free space in the local hard disk to put there all backup files. Is 
there a way to see what is the content of each fdb file in order to put in 
the local folder only the files I need?



Thank you very much



Daniele





----- Original Message ----- 
From: "Dumitru, Alex" <alex.dumitru@xxxxxxxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Monday, January 23, 2006 5:26 PM
Subject: Re: [foxboro] configuring AIM* to get data from external fdb 
database file


> Daniele,
> By the sound of it you have some user rights issues.
>
> I would try the following:
>
> 1. Make sure that the share you are creating has full rights for the user
> "Fox"
> 2. Make sure that on the backup computer (W2K) the local user "Fox" has
> enough rights to access the backed-up files.
> 3. Make sure that the backup files are on a R/W media, that is you do not
> examine these from let's say a CD.
>
> To check that your backed-up files are OK you can create a local folder on
> the AW70 (for example d:\opt\aim\tmprestore\YOUR_INSTANCE_NAME_GOES_HERE)
> and change the DBPATH accordingly (in this example
> DBPATH=d:\opt\aim\inst;d:\opt\aim\tmprestore) and then copy manually some 
> of
> the old files to the newly created folder.
>
> If your manual backup can see the files and you can access the info within
> then your files are OK so you really have to concentrate your attention
> around the user access rights / security issues.
>
> Hope this helps,
>
> Alex Dumitru, Eng.
> SI & IT
> Invensys Systems Canada Inc.
> Phone: (514) 421 8073
> Fax:   (514) 421 8054
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] 
> On
> Behalf Of Daniele Tocco
> Sent: Monday, January 23, 2006 7:13 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] configuring AIM* to get data from external fdb
> database file
>
> Unfortunately, I am still getting some troubles,
>
> I set the same account to both PCs. Same user fox and same password. I 
> have
> tried to connect from the AW7001 to backup and it is working.
>
> When I modify the DBPATH parameter in the historian configurator:
>
> DBPATH=d:\opt\aim\inst;\\backup\d
>
> The instance (hist01) tries to rebuild the DB indexes by considering also
> the files in the backup computer. These files are also visible in the 
> Manual
> Archiver from Historian manager. The only thing is that I am getting 
> errors
> in the log file of instance manager.
>
> For each fdb file in the backup computer I get an error like that:
>
>
>
> Historian hist01 Createfile r9087.fdb errno=1326 logon failure unknown 
> user
> name or bad password
>
>
>
> I also tried to share the \\backup\d folder but I got the same problem.
>
> Does somebody know what could be the problem??
>
> The OS in the backup pc is win2000 pro, the one in AW70 NT4
>
>
>
> Thank you a lot.
>
>
>
> Daniele
>
>
>
>
>
> ----- Original Message ----- 
> From: "Dumitru, Alex" <alex.dumitru@xxxxxxxxxxxxxxxx>
> To: <foxboro@xxxxxxxxxxxxx>
> Sent: Friday, January 20, 2006 2:22 PM
> Subject: Re: [foxboro] configuring AIM* to get data from external fdb
> database file
>
>
>> Hi Daniele,
>> The short answer is "Yes".
>>
>> So far all 70 series stations are being members of a workgroup (in 
>> Windows
>> networking terms). In such a context each station is its own security
>> authority and transparent access to shared folders can only be achieved
>> with
>> accounts that are identical in terms of user name and password on both
>> sides. This setup will work also for shares on computers that are part of
>> a
>> domain to which the 70 series station has access.
>>
>> Regards,
>>
>> Alex Dumitru, Eng.
>> SI & IT
>> Invensys Systems Canada Inc.
>> Phone: (514) 421 8073
>> Fax:   (514) 421 8054
>>
>> -----Original Message-----
>> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
>> On
>> Behalf Of Daniele Tocco
>> Sent: Friday, January 20, 2006 3:43 AM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: Re: [foxboro] configuring AIM* to get data from external fdb
>> database file
>>
>> Thank you Alex,
>>
>> I can now see in manual archiver that the instance is trying to get files
>> from the other computer.
>>
>> The only problem I am getting is the user name or password to use these
>> files. I was aware to this fact from the historian log. I verified that
>> the
>> user fox in the backup computer has no password. I think the fox accounts
>> in
>> both computers have to be the same, this means same user (fox) and same
>> password. Is it correct?
>>
>> After putting DBPATH parameter= d:\opt\aim\inst;\\backup\d\ I had to wait
>> a
>> lot (more than 12 hours) before the instance has stopped rebuilding the
>> database. A lot of logs appeared all said the user or password was
>> incorrect.
>>
>>
>>
>> Thank you again
>>
>>
>>
>> Daniele
>>
>> ----- Original Message -----
>> From: "Dumitru, Alex" <alex.dumitru@xxxxxxxxxxxxxxxx>
>> To: <foxboro@xxxxxxxxxxxxx>
>> Sent: Thursday, January 19, 2006 2:38 PM
>> Subject: Re: [foxboro] configuring AIM* to get data from external fdb
>> database file
>>
>>
>>> Hi Daniele,
>>> 1. You can read old AIM* historian files only with the same instance
>>> that created the files, so I will presume that the old files were
>>> archived and offloaded to another computer.
>>> 2. The DBPATH variable should point to all locations of the files and
>>> for every folder it should stop before the instance name, for example:
>>>   C:\Program Files\aim\inst;E:\Archive;\\backup\d
>>> 3. The easiest way in order to mark the data files as available for
>>> reading by all the client tools is to start the Manual Archiver from
>>> your Historian Manager. Depending on the instance size it may take a
>>> while to rebuild the index files so you have to be patient. When the
>>> file list shows up check for the presence of the files in the list.
>>>
>>> Hope this helps,
>>>
>>> Alex Dumitru, Eng.
>>> SI & IT
>>> Invensys Systems Canada Inc.
>>> Phone: (514) 421 8073
>>> Fax:   (514) 421 8054
>>>
>>> -----Original Message-----
>>> From: foxboro-bounce@xxxxxxxxxxxxx
>>> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
>>> On
>>> Behalf Of Daniele Tocco
>>> Sent: Thursday, January 19, 2006 3:32 AM
>>> To: foxboro@xxxxxxxxxxxxx
>>> Subject: [foxboro] configuring AIM* to get data from external fdb
>>> database file
>>>
>>> Hi All,
>>> I am trying without success to configure an instance of AIM* to read
>>> some old historian files stored in another computer. The machine which
>>> has installed the instance is connected with the other which has the
>> files.
>>> The
>>> connection is ok.
>>> I tried to use historian configurator and set the DBPATH parameter by
>>> putting there the path where the files are. In my case supposing that
>>> the computer where are the files is called Backup I put in the
>>> historian configurator file
>>> DBPATH=\\backup\d\hist01
>>> After this setting I am still not able to use the files.
>>> Somebody can help me?
>>> Are there some other parameters to set or something to verify??
>>> Thanks a lot
>>>
>>> Daniele
>>>
>>>
>>> ______________________________________________________________________
>>> _ This mailing list is neither sponsored nor endorsed by Invensys
>>> Process Systems (formerly The Foxboro Company). Use the info you
>>> obtain here at your own risks. Read
>>> http://www.thecassandraproject.org/disclaimer.html
>>>
>>> foxboro mailing list:             http://www.freelists.org/list/foxboro
>>> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>>> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>>>
>>>
>>>
>>>
>>>
>>> ______________________________________________________________________
>>> _ This mailing list is neither sponsored nor endorsed by Invensys
>>> Process Systems (formerly The Foxboro Company). Use the info you
>>> obtain here at your own risks. Read
>>> http://www.thecassandraproject.org/disclaimer.html
>>>
>>> foxboro mailing list:             http://www.freelists.org/list/foxboro
>>> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>>> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>>>
>>>
>>
>>
>>
>>
>> _______________________________________________________________________
>> This mailing list is neither sponsored nor endorsed by Invensys Process
>> Systems (formerly The Foxboro Company). Use the info you obtain here at
>> your
>> own risks. Read http://www.thecassandraproject.org/disclaimer.html
>>
>> foxboro mailing list:             http://www.freelists.org/list/foxboro
>> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>>
>>
>>
>>
>>
>> _______________________________________________________________________
>> This mailing list is neither sponsored nor endorsed by Invensys Process
>> Systems (formerly The Foxboro Company). Use the info you obtain here at
>> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>>
>> foxboro mailing list:             http://www.freelists.org/list/foxboro
>> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>>
>>
>
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: