We are getting a large number of Open and Create error when the file server 
is a Windows 2012 server.

The errorsys displays the error and gives an option to retry. When the retry 
is selected the action goes through.

I thought it was the issue with the SMB2 Info cache, and installed the .MSI. 
This did not solve the problem.
We know it has to do with the server. We copied the files to a local windows 
7 machine and shared the data. The problem goes away.

Any other ideas we can look at.

Frank Toth
Silver Mountain Software
Tel: (905)853-6922
Fax: (905)853-1709
support@silvermountain.ca
ftoth@silvermountain.ca
www.silvermountain.ca

Hi Frank,

I have had similar problems even with 2008 R2, the problems has always
been assigning the correct rights for the user, 2012 is even more
particular than 2008 R2. Make sure there are no user policies blocking
the process as well.

Hope this helps

Regards

Chris


On Tue, 25 Nov 2014 05:05:36 -0500, Frank Toth wrote:

>We are getting a large number of Open and Create error when the file server 
>is a Windows 2012 server.
>
>The errorsys displays the error and gives an option to retry. When the retry 
>is selected the action goes through.
>
>I thought it was the issue with the SMB2 Info cache, and installed the .MSI. 
>This did not solve the problem.
>We know it has to do with the server. We copied the files to a local windows 
>7 machine and shared the data. The problem goes away.
>
>Any other ideas we can look at.

I think it is more complicated then that. If we rebuild all the files, 
sometimes no errors. Then try again right away and many errors, but a retry 
will let it go through.
The error is either:
File not found - retry and it is found
Can not create file - creating the index file - retry and it goes through

Frank"Chris Chambers" wrote in message 
news:fjed7a5kspst778d3driu751o0ra6fo7mk@4ax.com...
> Hi Frank,
>
> I have had similar problems even with 2008 R2, the problems has always
> been assigning the correct rights for the user, 2012 is even more
> particular than 2008 R2. Make sure there are no user policies blocking
> the process as well.
>
> Hope this helps
>
> Regards
>
> Chris
>
>
> On Tue, 25 Nov 2014 05:05:36 -0500, Frank Toth wrote:
>
>>We are getting a large number of Open and Create error when the file 
>>server
>>is a Windows 2012 server.
>>
>>The errorsys displays the error and gives an option to retry. When the 
>>retry
>>is selected the action goes through.
>>
>>I thought it was the issue with the SMB2 Info cache, and installed the 
>>.MSI.
>>This did not solve the problem.
>>We know it has to do with the server. We copied the files to a local 
>>windows
>>7 machine and shared the data. The problem goes away.
>>
>>Any other ideas we can look at.

Hi Toth,

The symptom you are describing is exactly one of the things that are fixed 
by the
smb2 fix. Unfortunately you tell us that the fix is installed. Please 
forgive my
paranoia and verify on the workstation the registry keys under

HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\LanmanWorkstation\Parameters

Following Entries must exist and the value zero must be set:

FileInfoCacheLifetime, FileNotFoundCacheLifetime and DirectoryCacheLifetime

To recap what we understand. You have a scenario where you encounter
a false behaviour when files are created. The first attemp to create a file 
fails,
a second attemp succeeds right after the first one.

> If we rebuild all the files, sometimes no errors.
> Then try again right away and many errors

How do you mean that exactly. I understand the error situation occurs not
always. The error situation is sporadic. If the error occurs then all files 
are
affected or is it only some of them? Can you reproduce the problem at will?
Or ist it too sporadic?

Let me be a little bit paranoia a second time because this is the reason for
so many different type of problems: We can assume that the issue is not
with the client machines. Is there any anti virus software running on the
server (or on the client anyway). Or is there anything running that 
interfers
the fileio?

  Andreas Herdt
  Alaska Software

--------------------------------------------------------------------

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------

"Frank Toth" wrote in message 
news:5a59a4fe$6e5f56b4$11f6f2@news.alaska-software.com...
>I think it is more complicated then that. If we rebuild all the files, 
>sometimes no errors. Then try again right away and many errors, but a retry 
>will let it go through.
> The error is either:
> File not found - retry and it is found
> Can not create file - creating the index file - retry and it goes through
>
>
> -- 
> Frank"Chris Chambers" wrote in message 
> news:fjed7a5kspst778d3driu751o0ra6fo7mk@4ax.com...
>> Hi Frank,
>>
>> I have had similar problems even with 2008 R2, the problems has always
>> been assigning the correct rights for the user, 2012 is even more
>> particular than 2008 R2. Make sure there are no user policies blocking
>> the process as well.
>>
>> Hope this helps
>>
>> Regards
>>
>> Chris
>>
>>
>> On Tue, 25 Nov 2014 05:05:36 -0500, Frank Toth wrote:
>>
>>>We are getting a large number of Open and Create error when the file 
>>>server
>>>is a Windows 2012 server.
>>>
>>>The errorsys displays the error and gives an option to retry. When the 
>>>retry
>>>is selected the action goes through.
>>>
>>>I thought it was the issue with the SMB2 Info cache, and installed the 
>>>.MSI.
>>>This did not solve the problem.
>>>We know it has to do with the server. We copied the files to a local 
>>>windows
>>>7 machine and shared the data. The problem goes away.
>>>
>>>Any other ideas we can look at.
>

I have seen temp net disconnect problems on some Windows 8 machines. Any 
chance the problem machines are Windows 8??

Jim



On 11/27/2014 02:08 PM, "Andreas Herdt" wrote:
> Hi Toth,
>
> The symptom you are describing is exactly one of the things that are
> fixed by the
> smb2 fix. Unfortunately you tell us that the fix is installed. Please
> forgive my
> paranoia and verify on the workstation the registry keys under
>
> HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\LanmanWorkstation\Parameters
>
>
> Following Entries must exist and the value zero must be set:
>
> FileInfoCacheLifetime, FileNotFoundCacheLifetime and DirectoryCacheLifetime
>
> To recap what we understand. You have a scenario where you encounter
> a false behaviour when files are created. The first attemp to create a
> file fails,
> a second attemp succeeds right after the first one.
>
>> If we rebuild all the files, sometimes no errors.
>> Then try again right away and many errors
>
> How do you mean that exactly. I understand the error situation occurs not
> always. The error situation is sporadic. If the error occurs then all
> files are
> affected or is it only some of them? Can you reproduce the problem at will?
> Or ist it too sporadic?
>
> Let me be a little bit paranoia a second time because this is the reason
> for
> so many different type of problems: We can assume that the issue is not
> with the client machines. Is there any anti virus software running on the
> server (or on the client anyway). Or is there anything running that
> interfers
> the fileio?
>

James,

It is not a disconnect problem. I have checked and the network connect to 
the server drive is still there when the error occurs.

Frank Toth

"James Loughner" wrote in message 
news:6f60e9dd$5ad30eb1$177d4d@news.alaska-software.com...
>I have seen temp net disconnect problems on some Windows 8 machines. Any 
>chance the problem machines are Windows 8??
>
> Jim
>
>
>
> On 11/27/2014 02:08 PM, "Andreas Herdt" wrote:
>> Hi Toth,
>>
>> The symptom you are describing is exactly one of the things that are
>> fixed by the
>> smb2 fix. Unfortunately you tell us that the fix is installed. Please
>> forgive my
>> paranoia and verify on the workstation the registry keys under
>>
>> HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\LanmanWorkstation\Parameters
>>
>>
>> Following Entries must exist and the value zero must be set:
>>
>> FileInfoCacheLifetime, FileNotFoundCacheLifetime and 
>> DirectoryCacheLifetime
>>
>> To recap what we understand. You have a scenario where you encounter
>> a false behaviour when files are created. The first attemp to create a
>> file fails,
>> a second attemp succeeds right after the first one.
>>
>>> If we rebuild all the files, sometimes no errors.
>>> Then try again right away and many errors
>>
>> How do you mean that exactly. I understand the error situation occurs not
>> always. The error situation is sporadic. If the error occurs then all
>> files are
>> affected or is it only some of them? Can you reproduce the problem at 
>> will?
>> Or ist it too sporadic?
>>
>> Let me be a little bit paranoia a second time because this is the reason
>> for
>> so many different type of problems: We can assume that the issue is not
>> with the client machines. Is there any anti virus software running on the
>> server (or on the client anyway). Or is there anything running that
>> interfers
>> the fileio?
>>
>

I have check the registry and the SMB2 fix was applied correctly.

The error occurs frequently when we do a complete pack and reindex of all 
the files (there are over 200 DBF files and their associated indexes)
It is never the same files. It will sometimes only have one or two errors 
running the routine (retry will always work and the program will carry on) 
and other times 30 to 40 errors on the files.

I did another reply on this posting with more details as to what I have done 
so far. The current solution HIDES the problem, but I AM NOT HAPPY, because 
I know the problem is still there in the background.

Frank Toth

"Andreas Herdt" wrote in message 
news:2c6332de$21288baa$12d461@news.alaska-software.com...
> Hi Toth,
>
> The symptom you are describing is exactly one of the things that are fixed 
> by the
> smb2 fix. Unfortunately you tell us that the fix is installed. Please 
> forgive my
> paranoia and verify on the workstation the registry keys under
>
> HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\LanmanWorkstation\Parameters
>
> Following Entries must exist and the value zero must be set:
>
> FileInfoCacheLifetime, FileNotFoundCacheLifetime and 
> DirectoryCacheLifetime
>
> To recap what we understand. You have a scenario where you encounter
> a false behaviour when files are created. The first attemp to create a 
> file fails,
> a second attemp succeeds right after the first one.
>
>> If we rebuild all the files, sometimes no errors.
>> Then try again right away and many errors
>
> How do you mean that exactly. I understand the error situation occurs not
> always. The error situation is sporadic. If the error occurs then all 
> files are
> affected or is it only some of them? Can you reproduce the problem at 
> will?
> Or ist it too sporadic?
>
> Let me be a little bit paranoia a second time because this is the reason 
> for
> so many different type of problems: We can assume that the issue is not
> with the client machines. Is there any anti virus software running on the
> server (or on the client anyway). Or is there anything running that 
> interfers
> the fileio?
>
> -- 
>  Andreas Herdt
>  Alaska Software
>
> --------------------------------------------------------------------
>
> Technical Support:      support@alaska-software.com
>
> News Server:            news.alaska-software.com
> Homepage:               http://www.alaska-software.com
> WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm
>
> Fax European Office:    +49 (0) 61 96 - 77 99 99 23
> Fax US Office:          +1 (646) 218 1281
> --------------------------------------------------------------------
>
> "Frank Toth" wrote in message 
> news:5a59a4fe$6e5f56b4$11f6f2@news.alaska-software.com...
>>I think it is more complicated then that. If we rebuild all the files, 
>>sometimes no errors. Then try again right away and many errors, but a 
>>retry will let it go through.
>> The error is either:
>> File not found - retry and it is found
>> Can not create file - creating the index file - retry and it goes through
>>
>>
>> -- 
>> Frank"Chris Chambers" wrote in message 
>> news:fjed7a5kspst778d3driu751o0ra6fo7mk@4ax.com...
>>> Hi Frank,
>>>
>>> I have had similar problems even with 2008 R2, the problems has always
>>> been assigning the correct rights for the user, 2012 is even more
>>> particular than 2008 R2. Make sure there are no user policies blocking
>>> the process as well.
>>>
>>> Hope this helps
>>>
>>> Regards
>>>
>>> Chris
>>>
>>>
>>> On Tue, 25 Nov 2014 05:05:36 -0500, Frank Toth wrote:
>>>
>>>>We are getting a large number of Open and Create error when the file 
>>>>server
>>>>is a Windows 2012 server.
>>>>
>>>>The errorsys displays the error and gives an option to retry. When the 
>>>>retry
>>>>is selected the action goes through.
>>>>
>>>>I thought it was the issue with the SMB2 Info cache, and installed the 
>>>>.MSI.
>>>>This did not solve the problem.
>>>>We know it has to do with the server. We copied the files to a local 
>>>>windows
>>>>7 machine and shared the data. The problem goes away.
>>>>
>>>>Any other ideas we can look at.
>>
>

This one particular client has been getting the file open and create error 
since they replace the last few XP computes with Windows 7 computers. When 
they had the older XP boxes running off the Windows 2012 server, they say 
the errors were not occurring on the XP boxes. This problem is driving me 
crazy. Their network tech says there is nothing wrong with the network and 
has to be our software.

First thing I did was make sure the SMB2 File cache was installed on all the 
Windows 7 workstations and made sure it was not installed on the Windows 
2012 server.
PROBLEM WAS STILL THERE!

They are running Kaspersky network version. I had the tech exclude the 
program and data folders from being scanned.
PROBLEM WAS STILL THERE!

Next I copied the program and data to a local Windows 7 workstation drive C 
to test.
THE PROBLEM DID NOT occur!!!!

Next I shared the files off the Windows 7 workstation and map it on another 
Windows 7 workstation.
THE PROBLEM WAS STILL THERE over the network, not running off the Windows 
2012 Server???

The issue is that when the error occurs, our Errorsys recognizes that a 
retry can be attempted and gives the user the option to RETRY. MOST TIMES 
THE FIRST RETRY WILL WORK and the program will carry on until it encounters 
the error again. Retry works again.

I made some changes to the Errorsys to catch the error and attempt to do up 
to 5 retries before actually displaying the error.

The error code causing the problems are:
     XPP_ERR_READ     - 73
    XPP_ERR_DOS        - 40
    XPP_ERR_CREATE - 70
    XPP_ERR_OPEN     - 71

It seems to mask the problem, but does not solve the problem.

If anyone has any insight would be greatly appreciated.

Frank Toth
Silver Mountain Software
Tel: (905)853-6922
Fax: (905)853-1709
support@silvermountain.ca
ftoth@silvermountain.ca
www.silvermountain.ca

"Frank Toth" wrote in message 
news:b9d6755$2f5dbc2e$48a08@news.alaska-software.com...
> We are getting a large number of Open and Create error when the file 
> server is a Windows 2012 server.
>
> The errorsys displays the error and gives an option to retry. When the 
> retry is selected the action goes through.
>
> I thought it was the issue with the SMB2 Info cache, and installed the 
> .MSI. This did not solve the problem.
> We know it has to do with the server. We copied the files to a local 
> windows 7 machine and shared the data. The problem goes away.
>
> Any other ideas we can look at.
>
> -- 
> Frank Toth
> Silver Mountain Software
> Tel: (905)853-6922
> Fax: (905)853-1709
> support@silvermountain.ca
> ftoth@silvermountain.ca
> www.silvermountain.ca
>

Hi Frank,

Let's try to retrieve even more information from the myth.

What we have on our side is the fact that the problem is somehow
reproducable. This is precondition to collect some information on
how the client machine is communicating with the file server and
what operation finally failes with what error.

I suggest to download and use the process monitor from sysinternals:

http://technet.microsoft.com/de-de/sysinternals/bb896645.aspx

Using the tool you are able to protocol a bunch of IO operations and
we are able to filter the messages to see only those of interrest.

With the proc monitor it is possible to stop the protocol, you might
like to start protocol operations just before you run the problematik
operations with your application, just to reduce the amount of data
a little bit.

You may stop protocol operations immediately after the problem
occurred and the retry succeeded. This again is to reduce protocol
data amount.

Please ensure that all file operations are part of the resulting log.
Becoming familiar with this tool by reading in it's documentation
is worth the time invested. The process monitor is a great tool
for analyzing various types of problems.

As first attemp you should protocol one client machine. It might
become neccessary to protocol the server, however, first let us see
how the client behaves.

We really are curious what the reason for the failures will be at
the end.

  Andreas Herdt
  Alaska Software

--------------------------------------------------------------------

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------

"Frank Toth" wrote in message 
news:1979a798$5ec367ca$4ac57@news.alaska-software.com...
> This one particular client has been getting the file open and create error 
> since they replace the last few XP computes with Windows 7 computers. When 
> they had the older XP boxes running off the Windows 2012 server, they say 
> the errors were not occurring on the XP boxes. This problem is driving me 
> crazy. Their network tech says there is nothing wrong with the network and 
> has to be our software.
>
> First thing I did was make sure the SMB2 File cache was installed on all 
> the Windows 7 workstations and made sure it was not installed on the 
> Windows 2012 server.
> PROBLEM WAS STILL THERE!
>
> They are running Kaspersky network version. I had the tech exclude the 
> program and data folders from being scanned.
> PROBLEM WAS STILL THERE!
>
> Next I copied the program and data to a local Windows 7 workstation drive 
> C to test.
> THE PROBLEM DID NOT occur!!!!
>
> Next I shared the files off the Windows 7 workstation and map it on 
> another Windows 7 workstation.
> THE PROBLEM WAS STILL THERE over the network, not running off the Windows 
> 2012 Server???
>
> The issue is that when the error occurs, our Errorsys recognizes that a 
> retry can be attempted and gives the user the option to RETRY. MOST TIMES 
> THE FIRST RETRY WILL WORK and the program will carry on until it 
> encounters the error again. Retry works again.
>
> I made some changes to the Errorsys to catch the error and attempt to do 
> up to 5 retries before actually displaying the error.
>
> The error code causing the problems are:
>     XPP_ERR_READ     - 73
>    XPP_ERR_DOS        - 40
>    XPP_ERR_CREATE - 70
>    XPP_ERR_OPEN     - 71
>
> It seems to mask the problem, but does not solve the problem.
>
> If anyone has any insight would be greatly appreciated.
>
>
> -- 
> Frank Toth
> Silver Mountain Software
> Tel: (905)853-6922
> Fax: (905)853-1709
> support@silvermountain.ca
> ftoth@silvermountain.ca
> www.silvermountain.ca
>
> "Frank Toth" wrote in message 
> news:b9d6755$2f5dbc2e$48a08@news.alaska-software.com...
>> We are getting a large number of Open and Create error when the file 
>> server is a Windows 2012 server.
>>
>> The errorsys displays the error and gives an option to retry. When the 
>> retry is selected the action goes through.
>>
>> I thought it was the issue with the SMB2 Info cache, and installed the 
>> .MSI. This did not solve the problem.
>> We know it has to do with the server. We copied the files to a local 
>> windows 7 machine and shared the data. The problem goes away.
>>
>> Any other ideas we can look at.
>>
>> -- 
>> Frank Toth
>> Silver Mountain Software
>> Tel: (905)853-6922
>> Fax: (905)853-1709
>> support@silvermountain.ca
>> ftoth@silvermountain.ca
>> www.silvermountain.ca
>>
>

Hi Frank,

to be sure, that the reg entries are really set, just write a policy on 
the domain controller for all computers.

Try to switch in your network card settings to 100MBit and disable the 
networkcard power settings. This was the solution of one of our customers.

Regards

On 04.12.14 15:37, "Frank Toth" wrote:
> This one particular client has been getting the file open and create
> error since they replace the last few XP computes with Windows 7
> computers. When they had the older XP boxes running off the Windows 2012
> server, they say the errors were not occurring on the XP boxes. This
> problem is driving me crazy. Their network tech says there is nothing
> wrong with the network and has to be our software.
>
> First thing I did was make sure the SMB2 File cache was installed on all
> the Windows 7 workstations and made sure it was not installed on the
> Windows 2012 server.
> PROBLEM WAS STILL THERE!
>
> They are running Kaspersky network version. I had the tech exclude the
> program and data folders from being scanned.
> PROBLEM WAS STILL THERE!
>
> Next I copied the program and data to a local Windows 7 workstation
> drive C to test.
> THE PROBLEM DID NOT occur!!!!
>
> Next I shared the files off the Windows 7 workstation and map it on
> another Windows 7 workstation.
> THE PROBLEM WAS STILL THERE over the network, not running off the
> Windows 2012 Server???
>
> The issue is that when the error occurs, our Errorsys recognizes that a
> retry can be attempted and gives the user the option to RETRY. MOST
> TIMES THE FIRST RETRY WILL WORK and the program will carry on until it
> encounters the error again. Retry works again.
>
> I made some changes to the Errorsys to catch the error and attempt to do
> up to 5 retries before actually displaying the error.
>
> The error code causing the problems are:
>      XPP_ERR_READ     - 73
>     XPP_ERR_DOS        - 40
>     XPP_ERR_CREATE - 70
>     XPP_ERR_OPEN     - 71
>
> It seems to mask the problem, but does not solve the problem.
>
> If anyone has any insight would be greatly appreciated.
>
>

Hello,

Had same problems on Win-8 computer.
I manged to fix the most errors as foloows:

1. Exclude anti-virus scanner on folders where your data is.
2. Disable indexing.  (Explorer\Properties\Advanced uncheck 2nd checkbox)

Regards,
Jack Duijf


On Tue, 25 Nov 2014 05:05:36 -0500, Frank Toth wrote:


>We are getting a large number of Open and Create error when the file server 
>is a Windows 2012 server.
>
>The errorsys displays the error and gives an option to retry. When the retry 
>is selected the action goes through.
>
>I thought it was the issue with the SMB2 Info cache, and installed the .MSI. 
>This did not solve the problem.
>We know it has to do with the server. We copied the files to a local windows 
>7 machine and shared the data. The problem goes away.
>
>Any other ideas we can look at.
Regards
Jack Duijf

-------------------------------------------------------------
Also a member off the XXP (http://www.xxp.nl)

Problem Solved. I had originally told the user it was their Kaspersky Virus 
Scanner. The Tech guy swore it was not.
Guess What? IT WAS KASPERSKY. They contacted Kaspersky and they supplied a 
patch and the problem has gone away.

I have spent hours on this issue. What a waste of time.

Frank Toth

"Frank Toth" wrote in message 
news:b9d6755$2f5dbc2e$48a08@news.alaska-software.com...
> We are getting a large number of Open and Create error when the file 
> server is a Windows 2012 server.
>
> The errorsys displays the error and gives an option to retry. When the 
> retry is selected the action goes through.
>
> I thought it was the issue with the SMB2 Info cache, and installed the 
> .MSI. This did not solve the problem.
> We know it has to do with the server. We copied the files to a local 
> windows 7 machine and shared the data. The problem goes away.
>
> Any other ideas we can look at.
>
> -- 
> Frank Toth
> Silver Mountain Software
> Tel: (905)853-6922
> Fax: (905)853-1709
> support@silvermountain.ca
> ftoth@silvermountain.ca
> www.silvermountain.ca
>

Hi Mr Toth,

Thank you for posting the solution here.

  Andreas Herdt
  Alaska Software

--------------------------------------------------------------------

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------

"Frank Toth" wrote in message 
news:6bdb62f8$cf4176d$2a85c@news.alaska-software.com...
> Problem Solved. I had originally told the user it was their Kaspersky 
> Virus Scanner. The Tech guy swore it was not.
> Guess What? IT WAS KASPERSKY. They contacted Kaspersky and they supplied a 
> patch and the problem has gone away.
>
> I have spent hours on this issue. What a waste of time.
>
> Frank Toth
>
> "Frank Toth" wrote in message 
> news:b9d6755$2f5dbc2e$48a08@news.alaska-software.com...
>> We are getting a large number of Open and Create error when the file 
>> server is a Windows 2012 server.
>>
>> The errorsys displays the error and gives an option to retry. When the 
>> retry is selected the action goes through.
>>
>> I thought it was the issue with the SMB2 Info cache, and installed the 
>> .MSI. This did not solve the problem.
>> We know it has to do with the server. We copied the files to a local 
>> windows 7 machine and shared the data. The problem goes away.
>>
>> Any other ideas we can look at.
>>
>> -- 
>> Frank Toth
>> Silver Mountain Software
>> Tel: (905)853-6922
>> Fax: (905)853-1709
>> support@silvermountain.ca
>> ftoth@silvermountain.ca
>> www.silvermountain.ca
>>
>