We have been running a Visual FoxPro (version 9) application on a Server under Microsoft Windows Server 2003 Operating system for a number of years now. We are now trying to migrate it to a different Server running under Microsoft Windows Server 2003 R2 and the application crashes. The problem occurs when it is trying to create HTML files from the FoxPro reports it has just created. To do this is uses the system variable _ReportOutput and aborts with the message “ox is not an object”. The application resides on the Network in a directory accessible to both Servers. Since hitting this problem I have changed the program to use the Htmllistener class within _ReportListener and get the same problem (works on one not on the other (R2)). Wait windows have been inserted to gain additional information but they only show that the object has not been created returning a data type of .Logical. It appears to me the problem is with the R2 version of the operating system, has anybody any ideas.
Have you installed ReportOutput.APP in the same folder as the application?
Related
Brand new Windows 10 Pro system running 1809. Just installed Access via Office 365 (version 1904). We have a database that was originally created in 1998 and has been updated and working on other Windows 10 systems without a problem. However, when we open it on this new system, we are getting the following error right away:
Compile error. in query expression 'IIf(Hour(Time())<12,"Good Morning",IIf(Hour(Time())>11 And Hour(Time())<18,"Good Afternoon","Good Evening")'
Removing this query does nothing but bring up additional compile errors.
All of the other computers were running Office Pro 2007 at some point - probably when the database was converted from an .MDB to an .accdb file. They are now running the latest version of Access without issue. They all also have an Inactive Application Add-in called "Microsoft Office 2007 Access Database Engine Conflict Resolver" installed and set to Load on Demand. I don't know if this has anything to do with it.
I did install Office 2007 to this computer (Access module only) and that same add-on then appeared in the newer Access. But I have since uninstalled Office 2007 after the issue remained unresolved. (That add-on is now gone.)
My (probably ignorant) guess is that there is old code that isn't being processed correctly and the current batch of computers are handling it via something that was installed during the upgrade process? Our database needs are pretty simple and there are very few users.
Any help in getting this new system into the loop would be appreciated.
Argh. I think the issue was that I installed the 64-bit version of Office 365. All works now under 32-bit. Sorry and thanks.
We have a backup application that uses the Windows API BackupRead. It works correctly on Windows Server 2003, 2008, 2008 R2. It does not work on Storage Server 2008 R2. It always fails with error 50 - The request is not supported. The documentation for BackupRead gives no indication that it will not work with Storage Server 2008 R2.
Anyone else have any experience using this API on Storage Server 2008 R2? Did you need to make any changes to your use of the API in order for it to work?
Known problem between Windows 2008 and non-2008 volumes. Hot fix resolves it.
I have developed a POS System Recently and workin on its deployment.
Application Specifications:
The application is basically a POS system.
Back end = SQL Server 2008 Express R2.
Front End = C#
I also used SMO libraries.
Deployment Method = Click-once.
Target Framework = 4.0.
Development Tool = Visual Studio 2012 RC.
OS = Windows 7 Home Premium.
Used some SQL feature packs like Shared management Objects, CLR types. and others.
The prerequisites are selected and i packaged them also.
In brand new windows 7 the installation was fine. and application is running upto date.
In win XP the installation is fine. but when i start the app. it colses with this error.
SQL Server database is not installed and or not running.
and application quits.
IMPORTNAT NOTE:
THE 'WINDOWS XP SP3 PROFESSIONAL'
ON WHICH I AM TESTING IS INSTALLED ON VIRTUAL MACHINE
In the code i am running some SMO library functions in order to install *.sql script for the application's first time use.
SQL Server 2008 R2 is installed with all of its dependencies. and other feature packs. All the prerequisites are installed on XP.
Can you run SQLServer Management Studio on the XP VM and see SQLServer? If you run the SQLServer Configuration Manager on the VM, and click on SQL Server Services, does it show the service is running?
How do you have the connections configured? Do you have named pipes and TCP/IP enabled for the SQLServer Network configuration? What about the SQL Native Client configuration?
Do you have SQLServer Express ticked as a prerequisite in the ClickOnce deployment? What happens if you run setup.exe? Does it recognize that it's installed?
The SQLServer Express that's installed -- is it a named instance, or did you leave it as ".\SQLExpress" ? Id the connection string being used by the ClickOnce application right?
We've got an old VB6 app which uses Crystal Reports XI Release 2 to run reports against a SQL Server 2005 database. This has worked well over the years. Also, for the last upteen years we've used Windows XP. Well, we're beginning to migrate to Windows 7. Well, now one of the users on Windows 7 cannot run the report. It gives him an error of “Logon failed. Details: [Database Vendor Code: 6]”. All of the Crystal Reports used in this application use an system ODBC connection. I've verified, twice, that the system DNS properly authenticates against the SQL Server database. However, when the user attempts to run any of the reports in the VB6 app, they all give that same error. The weird thing is we've got another old VB6 app, which also uses Crystal Reports, and that app's reports work fine. But that app runs against a local Microsoft Access database, not against SQL Server.
So the question is, are there any known issues involving SQL Server, Crystal Reports XI Release 2 and Windows 7?
Something else we just noticed. On the 2 user machines that are exhibiting this problem, both are 64-bit Windows 7 machines. So, could it instead be an issue of a 64-bit version of Windows, SQL Server and Crystal Reports XI Release 2?
Crystal Report 11.5 does run on 64 bit windows. Minimum req.ment is CR11 R2 SP6 to run on 64 bit.
Using C++ Builder under Rad Studio XE I have created a simple Datasnap server service from scratch. I wanted to test the service installation process before adding any functionality, and found that while it will install successfully on a range of Windows machines, I haven't been able to get it to Start under a clean installation of Windows 7 x64.
The error message trying to start the service is: Windows could not start the service on Local Computer. Error 2: The system cannot find the specified file.
I have turned off both dynamic linking and run-time libraries. It starts fine under Windows XP and 2003 operating systems, just not this single Win7 machine that I have. I have opened the firewall for the specified ports, and confirmed no other app is using them as well. The service was installed under Administrator, and logs on as Local System account.
Is there a problem with a C++ Builder compiled service under Windows 7, or maybe 64 bit? Hopefully someone can point me in the right direction so I don't have to bang my head against the wall too many more time.
Thanks!
Since C++ Builder creates 32bit applications only, make sure you install the service in the c:\Windows\SysWOW64 folder on 64bit Win7 systems. Windows 7 x64 expects to find only 64bit files/services in the system32 folder.