Last Night, purchased and installed Active Sky Advanced on a Client Computer.Problem: Every time I click on my ASA desktop execution icon, I get the following error window:"Database write/corruption problemYour station database files could not be updated. Please make sure sharing is properly setup If using a networked configuration. proper ASA operation is not possible. Please restart ASA to attempt database reset."Please review my setup as defined below and see if you see my mistake.Systems:Primary Computer: New i7-975 CPU, P6T Deluxe V2 Motherboard with 6GB memoryWin Xp Pro 64 Bit with both FS9 and FSX installed and flying beautifully.Secondary Computer: Win XP Pro 32 Bit with both WideFS6 and WideFS7 installed and working.Intel E6600 Core 2 Duo CPU, P4N-SLI Motherbard on 4GB MemoryRunning FSC, FDC, and Proflight2000/PFE through WideFS with no problemsOn my Primary computer:System Harddrive is "C" (Map Network Drive "X")FSX Harddrive is "E" (Map Network Drive "Y")FS9 Harddrive is "F" (Map Network Drive "Z")Each is setup to share from their root directory and are listed under My Computer on the Client unit.Assumption: In reading the manual unless I overlooked something (which is highly possible), it appears that all instruction above "NETWORKED CONFIGURATION FOR FSX" is applicable only after having some success in getting ASA up and running. My assumption is that setup begins on this page.What I have done:1. "NETWORKED CONFIGURATION FOR FSX"primary computer:Right clicked "E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X"Selected "Sharing and Security..."Put a check mark in "Share this folder on the network"Put a check mark in "Allow network users to change my files"The Share name is "Microsoft Flight Simulator X".Right Clicked "C:\Documents and Settings\Administrator\Application Data\Microsoft\FSX"Selected "Sharing and Security..."Put a check mark in "Share this folder on the network"Put a check mark in "Allow network users to change my files"The Share name is "FSX".Right Clicked "C:\Documents and Settings\Administrator\My Documents\Flight Simulator X Files"Selected "Sharing and Security..."Put a check mark in "Share this folder on the network"Put a check mark in "Allow network users to change my files"The Share name is "Flight Simulator X Files".Right Clicked "C:\Documents and Settings\Administrator\My Documents\Flight Simulator Files"Selected "Sharing and Security..."Put a check mark in "Share this folder on the network"Put a check mark in "Allow network users to change my files"The Share name is "Flight Simulator Files".To confirm proper sharing, I can open all of these files on my client computer. In addition to this, under "My Network Places" the following is displayed:"c on Office (Rogers)""e on Office (Rogers)""f on Office (Rogers)""Flight Simulator 9 on Office (Rogers)""Flight Simulator Files on Office (Rogers)""Flight Simulator X Files on Office (Rogers)"fs9 on Office (Rogers)"fsx on Office (Rogers)"Microsoft Flight Simulator X on Office (Rogers)"2. "CONFIGURING SIMCONNECT:I have FSX Deluxe version installedI have FSX Service Pack 1 update installed (Removed, new download, reinstalled)I have FSX Service Pack 2 update installed (Removed, new download, reinstalled)I already had FSX SDK installed ("E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK")I downloaded and installed "FSX SKK SP1A"My assumption is that my "normal IP networking" is "appropriately configured" as the other programs mentioned above communicate with no problem between my two computers. (Plus my home network to my wife's computer, and/or a laptop functions with no problem).3. "STEP 1: VERIFY REQUIREMENTS" (Several times, including as I create this post).4. "STEP 2: CONFIGURE SERVER"Copied "SimConnect.xml" from "E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\config" to "C:\Documents and Settings\Administrator\Application Data\Microsoft\FSX"Copied "SimConnect.ini" from "E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\config" to "C:\Documents and Settings\Administrator\My Documents\Flight Simulator X Files"5. SIMCONNECT.XML""C:\Documents and Settings\Administrator\Application Data\Microsoft\FSX\SimConnect.xml" was edited as follows:<?xml version="1.0" encoding="Windows-1252" ?> - <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> - <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <Address>71.188.206.32</Address> <MaxClients>64</MaxClients> <Port>500</Port> <MaxRecvSize>4096</MaxRecvSize> <DisableNagle>False</DisableNagle> </SimConnect.Comm>- <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>Auto</Protocol> <Scope>local</Scope> </SimConnect.Comm> </SimBase.Document>Note: I determined my IP Address by clicking on: "http://www.myipaddress.com/show-my-ip-address/"6. "SIMCONNECT.INI""C:\Documents and Settings\Administrator\My Documents\Flight Simulator X Files\SimConnect.ini" was edited as follows:"[simConnect]level=verboseconsole=0;RedirectStdOutToConsole=1;OutputDebugString=1;file=c:\simconnect%03u.log;file_next_index=0;file_max_index=9"7. "STEP 3: INSTALLING SIMCONNECT CLIENT ON CLIENT (S)"Copied "E:\Program Files (X86)\Microsoft Games\Microsoft Flight simulator X SDK\SDK\Core Utilities Kit\SimConnect SKD\lib\SimConnect.msi" vfl from the Primary Computer to "C:\" on my secondary computer.Double clicked on the copied file, "SimConnect.msi" and it installed.8. "STEP 4: CONFIGURE CLIENT (S)"Copied "E:\Program Files (X860\Microsoft Games\Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\config\SimConnect.cfg" from the primary computer to "C:\Documents and Settins\Roger T. Hodges\My Documents" on the secondary computer.Edited "C:\Documents and Settins\Roger T. Hodges\My Documents\SimConnect.cfg" as follows:"[simConnect]Protocol=IPv4Address=71.188.206.32Port=500MaxReceiveSize=4096DisableNagle=0"9. "STEP 5: TEST THE CONFIGURATION"Went to "E:\Program Files (X86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\Simconnect SDK\Samples\AI Traffic\"Double clicked "AI Traffic.exe"Got a prompt window that included the following text:"Connected to Flight Simulator!Received:2AI object added: Type 2, Object ID=574"Threre are other "AI Objects" that are continually being added and removed.FSX must be running for me to get the above results. Otherwise, the prompt window only flashes on for an instant. I am assuming that this is the proper reaction. Please confirm.As per the manual instructions, may I now know that SimConnect is working correctly, and my problem with ASA is elsewhere?10. "STEP 6: CONFIGURING ASAThe first time I activated the ASA execution file, I got the following window:"Flight Simulator 2004 Location Not Founr!We were unable to locate required folder/files. Please browse to your Flight Simulator 2004 Location in the next screen. If you are running a networked configuration, select the proper share."I clicked OK and browsed to "My Computer\f on 'Office (Rogers)' (Z)\Program Files (X86)\Microsoft Games\Flight Simulator 9" and clicked "OK"The result was the following window:"FS9 Application Data Location Not Found"You did not select the proper Users\Appdata\Microsoft\FS9 folder. Proper ASA operation is not possible. Please close and restart ASA, selecting the correct path."When I click OK again, I get the "Database write/corruption problem" window I started with (third line of this post)As per the instructions under "STEP 6", I opened "HKEY_CURRENT-USER\Software\HiFi\ASA" with my Registry Editor.The display was as follows with the exception that there was no "FSXMYDocsPath", nor "FS9AppDataPath". line items. I took the liberty of editing to include them as follows:Line 1:Under Name: "(Default)", under Type: "REG_SZ", under Data: No text, this area is blank.Line 2:Under Name: "FS9AppDataPath", under Type: "REG_SZ", under Data: "X:\Documents and Settings\Administrator\Application Data\Microsoft\FS9\"Line 3:Under Name: "FS9MyDocsPath", under Type: "REG_SZ", under Data: "X:\Documents and Settings\Administrator\My Documents\Flight Simualtor Files"Line 4:Under Name: "FS9Path", under Type: "REG_SZ", under Data: "Z:\Program Files (X86)\Microsoft Games\Flight Simulator 9\"Line 5:Under Name: "FSXMyDocsPath", under Type: "REG_SZ", under Data: "X:\Documents and Settings\Administrator\My Documents\Flight Simulator X Files"Line 6:Under Name: "FSXPath", under Type: "REG_SZ", under Data: "Y:\Program Files (X86)\Microsoft Games\Microsoft Flight Simulator X\""Line 7:Under Name: "License", under Type: "REG_SZ", under Data: 358348=48388Z=JKZZZN-B53777"I just realized that one line was missing as per the manual instructions, so I edited to add the following line:Under Name: "FSXMyDocsPath", Under Type: "REG_SZ". under Data: "x:\Documents and Settings\Administrator\Application Data\Microsoft\FSX\I fear I may have set a record for length in a post, but attempted to give all the information one might need to help (Except what I forgot or overlooked)/If anyone sees my mistake and/or has a suggestion I sure would appreciate it.Respectfully:RTH

Half way there (I think)Don't know this for sure, but I think the vast majority of the time I was working with FS9 in my original post. Unfortunately, I never could get far enough to see which FS version ASA was trying to address. I suspect that if I had been able to select FSX, everything would have worked in ASA (For FSX Only).I discovered that if I changed the drive letter in Regedit or enter "//" marks before the Name (i.e. "//FS9Path" or "FSXPath", that it would give me the window again which allowed me to select the path (i.e. "Please browse to your Flight Simulator X Location in the next screen)."I did this, and browsed to ".....Microsoft Games\Microsoft Flight Simulator X" It rebuilt my FSXPath line in Regedit, and ASA seems to work fine now for FSX.Now, I am not sure what to do relative to FS9. Are line items supposed to be in the same folder, "ASA" for FS9? So far, the scenario that worked for FSX has not worked for FS9. I do have the latest FSUIPC payware version installed.To be continued:RTHEdit:If I disable or for that matter delete the "FS9Path" line in Regedit, ASA rebuilds it again when I browse to my FS9 folder exactly in the same way as it does for FSX. Also, the manual seems to say that the same things are required. But, ASA is not working in FS9 (Line 3 of my original post), and it does in FSX."NETWORKED CONFIGURATION FOR FS9" (In the pdf manual)"WideFS is required for networked use of FS9WideFS6 is installed and working fine for FSC, FDC and Proflight2000/PFEOn the separate non-FS9 computer, unpack the ASA installation.zip file to a temporary location, such as C:\ASTEMP (Do not install ASA on the FS9 computer).Run the Setup.exe Program to launch the installation process.Follow the on-screen prompts."ASA is installed and functioning fine for FSX"Setup networking and sharing so the WideClient computer has full access to the Server, especially in all FS9 related p;aths. You will need to share the FS9 Folder (On the FS9 computer) as well as the Application Data Folder (in the FS9 computer's Documents and Settings\User Name Location), or shar the root drives (i.e. C:\) directoly. For more help with networking WideFS, please see the WideFS documentation."All applicable folders have been setup to share as quoted in my original post, and instructed by the paragraph above. WideFS is working fine with other programs."Follow the onscreen prompts to locate the appropriate paths/files, copy required data and test the installation."Not too sure I know everyting they are talking about here. "On-screen prompts" for what, or from where? "Copy required data." What data? "Test the installation." What installation. Prompts for WideFS and ASA installation have been completed. Relative to testing the installation, WideFS6 works for other programs. ASA works for FSX. All relative folders/files can be accessed on the Client computer."Proceed with Configuring FSUIPC and FS9." What needs to be configured in FSUIPC or FS9 so that ASA will start up? Hummmm, back to the beginning of the manual perhaps?"Note: WideFS use requires registered FSUIPC and WideFS licenses. For WideFS/networking help, please read the WideFS documentation."Both WideFS6 and FSUJPC are registered and working normally for other programs."NOTE: Client and Server Use."WideFS6 is connected between the computers."If you are useing WideFS or SimConnect over a network and ASA is installed as a client and hyoualso have an instance of FS9 and/or FSX installed on the client PC you must ensure that the path (s) in the ASA registry setting for FS9 and/or FSX point (s) to your server version."FS9 and FSX are installed only on the primary computer."The registry settings that need adding if yhou are having an issue with ASA locating your server version are:HKEY_CURRENT_USER\SOFTWARE\HIFI\ASA\FS9Path"For this line item, Regedit displays: "FS9Path" for the Name, "REG-SZ" for the type, and "Z:\Program Files (X86)\Microsoft Games\Flight Simulator 9\""HKEY_CURRENT_USER\Software\HiFi\ASA\FS9AppDataPath"Line item: "FS9MyDocPath" for the name, "REG_SZ" for the type, "X:\Documents and Settings\Administrator\Application Data\Microsoft\FS9\"There are line items which are exactly the same for FSX with the exception of the "FSX" designation rather than "FS9". ASA works in FSX, does not in FS9.I also have a line item added: "FS9MyDocPath" for the name, "REG_SZ" for the type, "X:\Documents and Settings\Administrator\My Documents\Flight Simulator Files"This file is not mentioned under the FS9 setup, but assumed to be advisable and the similar file was listed for FSX. I also tried without it.I have selected "FS9" for the mode under options in ASA, and tried simply by editing Regedit as I mantion above with the same unsuccessful results.What have I missed for FS9, that I have for FSX, or what is different that I need to do?Thanks:RTH

Half way there (I think)Don't know this for sure, but I think the vast majority of the time I was working with FS9 in my original post. Unfortunately, I never could get far enough to see which FS version ASA was trying to address. I suspect that if I had been able to select FSX, everything would have worked in ASA (For FSX Only).I discovered that if I changed the drive letter in Regedit or enter "//" marks before the Name (i.e. "//FS9Path" or "FSXPath", that it would give me the window again which allowed me to select the path (i.e. "Please browse to your Flight Simulator X Location in the next screen)."I did this, and browsed to ".....Microsoft Games\Microsoft Flight Simulator X" It rebuilt my FSXPath line in Regedit, and ASA seems to work fine now for FSX.Now, I am not sure what to do relative to FS9. Are line items supposed to be in the same folder, "ASA" for FS9? So far, the scenario that worked for FSX has not worked for FS9. I do have the latest FSUIPC payware version installed.To be continued:RTH

RTH - I do NOT run your type of setup so I *may* be giving you bad info here - I'm sure Jim or some knowledgeable folks will straighten me out BUT IIRC, FS9 does not use Simconnect but does use FSUIPC.I'd begin by looking at the way FSUIPC is configured for FS9 vs FSX and see if something jumps out at you there. Also double check the ASA manual, I believe there is specific setup info relating to FSUIPC and ASA.Vic

Thanks for the reply Vic.You replied just about the same time I posted my last edit which concurs pretty much with what you say. I directly quote the "NETWORKED CONFIGURATION FOR FS)" section of the manual with what I have done relative to that section. You may be right relative to some selection in FSUIPC, or FS9 itself that has a needed selection provision, but so far I have overlooked it.Thanks again:RTH

RTH - I do NOT run your type of setup so I *may* be giving you bad info here - I'm sure Jim or some knowledgeable folks will straighten me out BUT IIRC, FS9 does not use Simconnect but does use FSUIPC.I'd begin by looking at the way FSUIPC is configured for FS9 vs FSX and see if something jumps out at you there. Also double check the ASA manual, I believe there is specific setup info relating to FSUIPC and ASA.Vic

Hi All,At this point I am not sure where this is at!I can review a few things:With FS04 you use FSUIPC and Wide FS. You run the Wide FS client and ASA, while in FS04 mode, should connect to FS.With FSX you use SimConnect correctly set up on the client. That is where the networking chapter will lead you forward.Let us know where you are with all of this.Thanks!

Good Morning Jim (or whatever time it is in your time of the world):"Where" I "am with all of this" is as follows:Summary: Have tried to follow your ASA.pdf manual from the "NETWORKED CONFIGURATION FOR FS9" (and FSX)) and the documentation on the following pages to the letter. Results: ASA works fine with FSX, and I have failed with FS9, mistake or error unknown.Specifics:1. Started up my primary server computer.2. Disabled all Anti-virus and Firewall provisions on this server computer..3. Started up my secondary Client computer.4. Disabled all Anti-virus and Firewall provisions on this client computer.5. Started up FS9.6. Double clicked my WideFS execution Icon on the Client Computer. Shows "WideClient FS98 Eliminator - Connected."7. Double clicked my Active Sky Advanced Desktop Icon.8. ASA Window displays text: "Checking internal Database Files. Please wait."9. About 30 seconds later, the ASA display ribbon begins to move from approximately 15% to 20% forward.10. Moments later the ASA window displays with "Please wait while initial weather process completes..." and "Download Active" text.11. A few moments later, "Download Active" text changes to "Synthesis Active".12. All option Icons change from gray to colored and I get text: "Successful connection to HiFi DataNet X Servers is verified."Assumption: All is as it should be relative to the installation of ASA for FSX and it is operating properly.13. Clicked on the ASA "Options" Icon..14. Clicked on the checkmark next to "FSX" directoly below "FS Mode FSX"15. Selected "FS9".16. ASA displays the "Flight Simulator 2004 Location Not Fouind" Window17. Click on the "OK" Checkmark18. Browse to "My Computer\f on 'Office (Rogers)' (Z:)\Program Files (X86)\Microsoft Games\Flight Simulator 9".19. Click OK20. ASA displays the "FS9 Application Data Location Not Found!" Window21, Click on the "OK" Checkmark22. Browse to "My Computer\c on 'Office (Rogers)' (X:)\Documents and Settings\Administrator\Application Data\Microsoft\FS9".23. Click OK24.ASA Window displays text: "Checking internal Database Files. Please wait."25. A few moments later an ASA Window pops up and displays: "Database write/corruption problem. Your station database files could not be updated. Please make sure sharing is properly setup if using a networked configuration. Proper ASA operation is not possible. Please restart ASA to attempt database reset." When I click on the OK checkmark, ASA shuts down. This cycle with the "Database write/corruption problem" and a shutdown of ASA will then repeat continually when double clicking the desktop ASA Icon in an attempt to restart ASA.I have repeatedly checked that "Share this folder on the network"" and "Allow network users to change my files" is checked for the FS9 folders in both the "Application Data\Microsoft\FS9", and the "Microsoft Games\Flight Simulator 9" folders. On my client folder I can access these files with no problem. The paths were also created in the ASA folder when I check with Regedit.In order to start over so that I may use ASA for FSX, I have had to delete or disable the FSP paths for FS9 in Regedit. Then the startup routine of ASA will ask for the path to the last selection made for the mode, in this case which was FS9. I can then select the path for FSX and ASA starts up just fine, although it will show an FS9 mode, and the Regedit path for FS9 will be to FSX, not FS9. I can then select the FSX mode in the ASA options and go through the routine again and the mode will show correctly (FSX) when ASA restarts.Note: There is no problem in running Flight Simulator Commander, Flightdeck Companion, or Proflight2000\PFE on my Client Computer through WideFS6, so I doubt that the WideFS and/or FSUIPC installations are suspect. However, there may be something I have missed in their options or setup for ASA.Thanks so much for your help. It is greatly appreciated.RTH

Hi All,At this point I am not sure where this is at!I can review a few things:With FS04 you use FSUIPC and Wide FS. You run the Wide FS client and ASA, while in FS04 mode, should connect to FS.With FSX you use SimConnect correctly set up on the client. That is where the networking chapter will lead you forward.Let us know where you are with all of this.Thanks!

6. Double clicked my WideFS execution Icon on the Client Computer. Shows "WideClient FS98 Eliminator - Connected."7. Double clicked my Active Sky Advanced Desktop Icon.RTH

I suppose you should have the WideFS execution to execute ASA as well, otherwise ASA will not connect with Fsuipc via WideFS.Simply add the full adress of your ASA.exe under the [user] tag in your WideFS.ini, then WideFS will execute Actvive Sky Advanced automatically.I have several programs that start when WideFS executes.Something like this:[user]Log=Errors+Run1=C:\Program Files\HiFi\ASA\ASA_Exec.exeRun2=D:\Program Files\Navigraph\nDAC 3\ndac.exeRun3=C:\Program Files\FS Real Time\FSRealTime.exe

Thanks loads for the reply:I am a little confused. I do not see a file called "WideFS.ini" and I did a search for it on both computers.Per chance did you mean: "WideClient.ini", not "WideFS.ini"?I opened "WideFS6\WideClient\WideClient.ini" and under "[user]" added: "Run1=C:\Program Files\HiFi\ASA\ASA_Exec.exe". As you said, "WideFS will execute Active Sky Advanced automatically." now.Unfortunately the same thing happens. If ASA is in the FSX mode, ASA starts up just fine. If it is in the FS9 mode, I still get my "Database write/Corruption problem" error window and when I click on the "OK" checkmark, ASA shuts down.Good try, but I am afraid there is no cigar yet.You are useing ASA with FS9 with your procedure aren't you?Respectfully:RTH

I suppose you should have the WideFS execution to execute ASA as well, otherwise ASA will not connect with Fsuipc via WideFS.Simply add the full adress of your ASA.exe under the [user] tag in your WideFS.ini, then WideFS will execute Actvive Sky Advanced automatically.I have several programs that start when WideFS executes.Something like this:[user]Log=Errors+Run1=C:\Program Files\HiFi\ASA\ASA_Exec.exeRun2=D:\Program Files\Navigraph\nDAC 3\ndac.exeRun3=C:\Program Files\FS Real Time\FSRealTime.exe

Hi All,No need to have WideFS start ASA. Your Wide FS/ASA stuff is fine. The problem lies with the sharing of the proper folders on the FS computer. You need to make sure that the proper folders are shared and both read and write privileges are enabled for those folders.Then you point ASA to them. Again this is a network situation, not a Wide FS/ASA situation, so don't change anything there.Thanks,

Jim, thanks ever so much.I was mistaken two ways.First of all, I thought that full sharing of the individual Application Data\FS9, and Microsoft Games\FS9 folders was all that was necessary. WRONG! I now see that I needed to Secondly in spite of this, I also thought that I had already fully shared the roots of all of my primary computer. WRONG AGAIN!Did some checking, and to my dismay I found that on drive F, which is my FS9 drive, under "sharing and security Share this folder on the network" was checked, but "Allow network users to change my files" was not. I would have sworn that I had it checked and probably did at some point in this scenario. Checked it and ASA comes up just fine for FS9 now.Looking forward to many hours of pleasure as soon as I get your gauge in my aircraft.Thanks again and sorry for being such a nuisence.Respectfully:RTH

Hi All,No need to have WideFS start ASA. Your Wide FS/ASA stuff is fine. The problem lies with the sharing of the proper folders on the FS computer. You need to make sure that the proper folders are shared and both read and write privileges are enabled for those folders.Then you point ASA to them. Again this is a network situation, not a Wide FS/ASA situation, so don't change anything there.Thanks,