Database Engine Error Invalid File Name
2005 Posts: 78 BDE Errors In Pathloss 4.0, the following are common BDE (Borland Database Engine) errors with instructions on how to fix them. BDE Error - Operation not applicable There are two possible causes:There are old *.lck files in the shared network directory. The .NET file is corrupt. To fix either, make sure all users, including yourself, are out of The database and Paradox. In Windows Explorer, browse to the shared network directory.Open the directory and check for the two files 'Paradox.lck' and 'Pdoxusrs.lck'. If either or both are present, delete them. Open the directory and check for the file 'Pdoxusrs.net'. Delete it. If you get a message "access is denied", have all database users restart their pc's then try deleting the file above again, if it is still present. NOTE: The 'Pdoxusrs.net' file will recreate itself when the first user logs back in. It is normal for this file to be present even when no user is in the database. During BDE Installation, the Error Message "Merging the Configuration File has Failed" Occurs Summary During BDE installation, InstallShield Express displays the error message "Merging the configuration file has failed". Discussion InstallShield Express includes with your BDE setup a configuration file called Idapi32.cnf. (For a 16-bit setup, this file is named Idapi.cnf.) During installation, InstallShield Express copies this file to a temporary location, and then adds to it the settings you chose in the BDE Alias dialogs. If there exists no BDE on the target system, then InstallShield Express simply saves the Idapi32.cnf file to the default BDE directory as Idapi32.cfg. However, if the target machine already has BDE on it (and so has a preexisting Idapi32.cfg file), InstallShield Express then calls the BDE Merge function to merge the Idapi32.cnf file with the existing Idapi32.cfg file, thereby adding your setup's BDE aliases and settings to those already on the target system. There are several possible reasons why the message "Merging the configuration file has failed" will be displayed during BDE setup: The target machine's preexisting Idapi32.cfg file is set to read-only or is in any other way inaccessible. This will cause BDE's Merge function to fail. InstallShield Express finds the existing IDAPI config
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries Inside-ERP MacProTX VoIP_News Inside-CRM PCMag I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker JoeTorre bracke Locutus Ramnath.Awate Richard DukeGanote Craig Borysowich Dennis Stevenson Nikki Klein mircea_luca AbhaiTripathi http://www.pathloss.com/forums/showthread.php?t=457 knowscognosdoi Clinton Jones bluesguyAZ59 Iqbalyk blrvenkat COMPANIES Juniper Networks CloudLock Avaya Adaptive Planning View All Topics View All Members View All Companies Toolbox for IT Topics PeopleSoft Groups Ask a New Question PeopleTools A forum where peers share technical expertise, solve problems, and discuss issues related to PeopleTools. Home | Invite Peers | More PeopleSoft Groups Your account is http://peoplesoft.ittoolbox.com/groups/technical-functional/peopletools-l/crystal-reports-error-invalid-file-name-736415 ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Crystal Reports error : Invalid File Name CRM_CONS asked May 16, 2005 | Replies (5) I am trying to run a Paycycle and have POS1 produce output to a server other than the one the Process Scheduler resides on. When I use D:\TEMP\ as the Output Destination, the crystal report is generated correctly. "D" drive is a local drive on the process scheduler. If I change the output destination to P:\output\ it returns the invalid file name message. "P" drive is a separate machine with a mapped
help me. I installed Delphi 2.0 on my computer. Here I will tell you what I http://www.delphigroups.info/2/b7/246057.html have done. I made a new alias with help of the https://community.microstrategy.com/t5/Architect/TN47664-quot-Invalid-file-name-Please-check-the-file-name-quot/ta-p/197295 BDE configuration utility. ----------------------------------------- Name: DeskData Type: Standard I add the pathname: c:\Mijn documenten\Desk My default driver becomes: DBase Enable BCD: False ----------------------------------------- Now I start the database explorer from Delphi. I can see clearly my new database named 'DeskData'. When I click it database engine all parameters are Ok. I click the item
General Discussions View all Getting Started with the Community Community News Get Connected Business Strategy & Best Practices Suggestions for this Community Technical Discussions View all Announcements Visualization Gallery Tech Corner Idea Exchange Platform (Installation & Deployment) Object Development Reporting, Dashboards, and Document Development MicroStrategy Desktop Clients (Interfaces & Visualizations) Administration Tools Intelligence Server Mobile Enterprise Assets (Data Sources & Gateways) MicroStrategy Software Development Kit (SDK) Security (Usher) Performance Events View all Events Blog Symposia 2016 Symposia 2015 Education World 2016 Discussions World 2015 Discussions World 2015 Track Sessions & Customer Presentations Community Menu Register · Sign In · Help Architect MicroStrategy > Architect > TN47664: "Invalid file name. Please check the file name." error message appears when trying to load database types from ... CommunityCategoryKnowledge BaseUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. TN47664: "Invalid file name. Please check the file name." error message appears when trying to load database types from a PDS file in MicroStrategy 9.x Started 08-19-2014 by DavidC Modified 09-24-2014 by Jparks Article Options Article History Subscribe to RSS Feed Mark as New Mark as Read Bookmark Subscribe Email to a Friend Printer Friendly Page Report Content Labels: Architect , Connectivity , Developer , ODBC 0 Likes SYMPTOM: When loading database types from a PDS file in MicroStrategy Desktop/Developer 9.x, the following error message may be encountered after selecting the PDS file and clicking "Load". Invalid file name. Please check the file name. CAUSE: This error is encountered if the PDS file selected is located in a network location (indicated by \\ at the beginning of the file path as shown above). ACTION: Move the PDS file to alocation local to the machineand reselect it. The database types can now be loaded successfully as shown below. Did this article solve your problem? Yes No (268 Views) Con