FalconView (#1) - Falconview on Windows 7 (#49) - Message List
I am trying to install the Army version (AMPS) on my computer. The OS is 64 bit Windows 7. I have downloaded and installed SQL Express 2005 and created a named instance of JMPS_SQL_SERVER. However I get the COM error message
Source: MDSWraper COM Error --.'\CovSelection?.cpp, line 881 Error code: 0x80004005 Description: Error code 0x80004005 - Unspecified error - OLE DB Error 4060: Cannot open Database "FV-JMPSMapCOV" Requested by the login. The login failed.
Any help would be appreciated. Thanks
-
Message #161
You may want to try the latest version of 4.3 available for download as it has SQL Server SP 1, which supports 64 bit installs. Please post here and let me know how that goes.
joelodom01/14/10 12:16:56 (7 months ago) -
Message #248
I am running Falconview 4.3.0.610 and I can get the program to install just fine on Windows 7 (32-bit). However, when I run Falconview it fails to initialize and generates a login failed error.
The text of the error log is
03/03/10 07:53:38 16c0 * 03/03/10 07:53:38 16c0 *** Starting FalconView version 4.3.0.610. Windows NT version 5.1 build 2600 Service Pack 3. 03/03/10 07:53:38 16c0 * 03/03/10 07:53:38 16c0 INFO: .\factory.cpp line 62. LPTClient interface is not in use! 3/3/2010 7:53:39 AM: TestForArcGIS failed: Could not load file or assembly 'ESRI.ArcGIS.System, Version=9.2.0.1324, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86' or one of its dependencies. The system cannot find the file specified. 03/03/10 07:53:39 16c0 OpenDataSource failed 03/03/10 07:53:39 16c0 errorInfo.hrError = 0x80004005; errorInfo.dwMinor code = 0x4814 03/03/10 07:53:39 16c0 EXCEPTION - Source: CDataSourcesRowset::raw_SelectByFolderName, File .\DataSourcesRowset.cpp, Line 220 - Description: Error code 0x80004005 - Unspecified error - OLE DB Error 18452; Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. 03/03/10 07:53:39 16c0 ERROR: .\MDSWrapper.cpp line 2940. CMdsNotifyEvents Initialize failed: Error = Error code 0x80004005 - Unspecified error - OLE DB Error 18452; Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
I have used the same setup to install Falconview on a Windows XP SP3 machine with no errors at all. I did discover that the install will fail on an XP machine if there is an earlier version of SQL Server, such as SQL Server 2005, installed. You have to remove all occurrences of SQL prior to installation.
I have installed SQL Server 2008 Express SP1 separately by running the following command from inside the SQL folder as suggested by others.
setup.exe /QS /ACTION=Install /FEATURES=BC,SQLEngine /INSTANCENAME=FV_SQL_SERVER /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /BROWSERSVCSTARTUPTYPE=Automatic /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS
Still the same login error. As much as we might not like it, Windows 7 is here and you can't even buy Windows XP in the store anymore. You have to special order XP for extra money to even get it.
I need to get this running on Windows 7.
Thanks for your help.
Garisn03/03/10 09:18:26 (5 months ago)-
Message #253
You Have to "RUN AS ADMINISTRATOR" when opening Falconview.
On Windows 7, simply goto your start menu and right click on "falconview" and choose "run as administator"
Falconview will run fine then
vroomz2803/04/10 16:33:15 (5 months ago)-
Message #254
You can Also Right Click and goto "Properties"
and check the box next to: "Run as Administrator"
vroomz2803/04/10 16:35:56 (5 months ago)-
Message #257
To get Falconveiw to run correctly in Windows, you need the new Vista Compatable version of AMPS (version R7.3.9)
install it, then when you goto run it the first time goto your start/all programs/pfps and right click on falconview.
goto properties and goto the compatability tab
check the box next to "Run as Administrator"
repeat these steps for CFPS
everything should work fine.
vroomz2803/04/10 16:44:41 (5 months ago)-
Message #260
The guys at FalconView made the following comment which corrected the "Initialization Failure..." problem that I was having. Thanks for all the help.
Comment(by ChrisBailey):
We are working on this issue but the workaround (From memory since I am not running it on this computer) is to open up the SQL Server 2008 Configuration Manager (or something like that under the Windows Start Menu) then go through the settings and look for any TCP/IP connection protocols and disable them and then look for any Named Pipes connection protocols and enable them.
Garisn03/09/10 07:35:10 (5 months ago)
-
-
-
-
