Logical Path not defined..?

Hi,
I recently got CRM 5.0 installed on my system. Very first step of 'Maintain Business Partner' it says, 'Logical Path not defined'.
Tried to open activities, says' Logical system not defined'
Please suggest what is the problem & how to rectify this.
A prompt reply wil be highly appreciated.
Thanks
Anil

Hi ,
You need to Define Logical System for your System to Allow you to Execute Actions
Path:SAP Web Application Server>Business Intelligence>Links to Other Source Systems>General Connection Settings::
In this step, you can define the logical systems in your distributed system.
Caution:Logical systems are defined cross-client.
Activities
1. To create a logical system, choose Edit -> New Entries.
2. Enter a name for the logical system that you want to create.
3. Enter a description of the logical system.
Enter the Logical System that you are using,
These Links may Further Help up for Details:
http://help.sap.com/saphelp_crm50/helpdata/en/b4/b0b13bb3acef3ce10000000a11402f/frameset.htm
http://help.sap.com/saphelp_crm50/helpdata/en/55/38e74110cf0b7fe10000000a155106/frameset.htm
Hope it Answered your Queries..
Thanks and Regards,
RK.
Added Links for Further Help: RK on Mar 5, 2009 12:07 PM

Similar Messages

LSMW LOGICAL PATH not set error

Hi,
    when i save an lsmw the error is coming as logical path not set. I guess this is for the CONV and READ files. Can ne one tell where can we speicfy this path. Right now we have to manually store the paths for these. Where in the settings can we defualt this path for these files.

Check the Specify Files Step:
Files
        Legacy Data          On the PC (Frontend)
            Input File                     D:\Documents and Settings\file4.txt
                                           Data for One Source Structure (Table)
                                           Separator Tabulator
                                           Field Order Matches Source Structure Definition
                                           With Record End Indicator (Text File)
                                           Code Page ASCII
        Legacy Data          On the R/3 server (application server)
        Imported Data        File for Imported Data (Application Server)
            Imported Data                  /usr/sap/tmp/ZHR.lsmw.read
        Converted Data       File for Converted Data (Application Server)
            Converted Data                 /usr/sap/tmp/ZHR.lsmw.conv
        Wildcard Value       Value for Wildcard '*' in File Name

LSMW by BI : Unable to specify file in step 7; logical Path not assigned

Hi,
I'm trying to uplaod HR DATA using object 0555 and method 0000 for Program RPDUSTD00 using LSMW Batch Input Method.
In step 7 when i specify file which tab delimited text file at front end pc(at my pc) let say c:\test.txt and save I got error message 'Logical path not assigned'.
Please suggest what I'm missing and what i need to do to get it correct.
Thanks,
Anshuman.

Hi,
There are other files specified in the screen for imported and converted data. These files must be accessible on SAP application server. If the logical file names are not created use physical ones lik /tmp/blabla.lsmw.read etc.
Make sure you use different files for different objects.
Kind regards
Michael

Logical system not defined in table SMOF_ERPSH!

Hello,
In the inbound queue of CRM, the queues are in 'SYSFAIL' status. The error message is ' logical system not defined in table SMOF_ERPSH!' .
the table has an entry for relevant ERP system.
I dont know where else to check.
I have checked the logical destinations on CRM and it is defined correctly.
can anyone help me here.
Regards,
Pratima

Hi Pratima,
I am also facing the same issue. I checked all the entries and Entries are there in the respective tables but still the same issue.
But if I delete the queue, the changes are replicated for that time but after some time again the queues are getting blocked with the same issue.
Pratima, can you please tell you whether your issue got fixed on this.
Thanks,
Sharath.

LSMW-logical path not specified

Hi experts,
I am doing an LSMW object for purchasing info records conversion.
In the step "specify files" i am not able to save wat i have done cos i am getting an error 'No logical path has been specified' .I have choosed the file from PC-Frontend. Due to this problem am not able to go ahead with further steps.
please help.
Thanks,
Neela

Hi
Have u followed all the steps perfectly while creating a lsmw ???
There are 14 steps that are normally used and these are :
1)   Maintain Object Attributes.
2)   Maintain Source Structures.
3)   Maintain Source Fields.
4)   Maintain Structure Relations
5)   Maintain Field Mapping and conversion rules .
6)   Maintain Fixed Values,translations ,user defined routines.
7)   Specify Files .
8)   Assign Files .
9)   Read DATA.
10) Display Read Data.
11) Convert Data.
12) Display Converted Data.
13) Create Batch Input Session.
14) Run Batch Input Sesion.
Check this link
http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm
www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc -
Regards
Pavan

Error in IDES while cratimg PO - Logical system not defined

Hi,
While creating PO in IDES , system is giving following error ,
"Logical system is not defined"
Pl suggest the solution,
Thanks a ton in advance,
NB

Hi
in BD54 Check have u defined logical system for client 800
for more details post ur prob. in SAP NetWeaver forum
Vishal...

Event trace error: own logical system not defined ?

Hello,
i am trying to start a workflow when the status of a document changes to "completed". I was checking the event trace with transaction code : "SWEL" and i found out that the workflow is trying to start but there is some kind of error and the event trace is saying :
Your own logical system has not been defined for this client. Most of the ALE functions therefore cannot be used. No links can be written.
Any suggestiobns on what can be the problem ?
points are awarded
Regards

Sounds like you need to setup your client as a logical system, to do so..
To do setup the Logical System follow the following steps
In IMG Settings
Cross Applications -> Distribution (ALE) -> Basic Cofiguration.
Set up Logical System -> Maintain Logical System.
Create New Entries

Logical system not defined.

Hello
Can some body help me to identify the issue which gives me an error,No Logical system for FI is manitained .
This error, I receive at the time of approving shopping carts.
Thanks.
Jayawant Gokhale

Hi,
Pls refer the foll threads:
PO transfer from SRM to vendor system
PDP issue - ext reqts missing in SRM system
External system to SRM
Re: Upload PO from XML file in SRM
BR,
Disha.
Pls reward points for useful answers.

Local logical system is not defined

Hello
We are trying to setup a logical system - created or defined the logical system
when we try the BD64 it gives out the error "Local Logical system not defined"
I am using ECC 6 version
IS there any way to bypass and do the setup ?

HI Anil,
Best Methodology for creating a RFC Destination that also includes setting up Logical System is:
Use Transaction -> SALE /b]
1) Define Logical system :
Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Logical System -> Define Logical System

2) Assign Client to Logical system:
Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Logical System -> Assign Logical System to Client
3) Create RFC Destination: T-CODE (SM59)
Select Idoc Interface / Application Link Enabling (ALE) -> Basic Setting -> Communication -> Create Rfc Connection
Follow steps in sequence. Hope it answers every thing.
Cheers,
*RAJ*
*POINTS IF FOUND HELPFULL*

LSMW : Unable to Specify Files . Logical path incorrect ?

Hi Guys,
I am trying to upload Goods movement Using the Standard LSMW 0110 program RM07MMBL.
When I try to execute the step Specify Files ,system displays an error message "No Logical Path specified."
The Source File is in my Local PC .
When I click the Converted Data File in the Specify files list
I get a popup which asks me for a Logical path and a Logical File and both these parameters a mandatory.
I tried to maintain the parameters and entries in transaction FILE also.
But it says 'logical path not assigned to the physical directory.'
What is the correct method for this.
What steps should I follow ..
Pls advice
Message was edited by: hao fu

Hi,
Refer the oss note 753511 released for this kind of error you face in LSMW, I am pasting the content of the note below,
******************Note Content,
Symptom
The system issues an error message for the logical path or file when you perform the "Specify files" step in the Legacy System Migration Workbench (transaction LSMW) although you have made the correct assignment in transaction FILE.
The error messages are as follows:
The logical path <PATH> does not point to the physical directory.
The logical file <FILE> is not assigned to the physical file.
or
A logical path was not specified.
Other terms
Logical path, logical file, transaction FILE, LSM Workbench
Reason and Prerequisites
Some import interfaces that you can also use with transaction LSMW work with logical path and file names.
Transaction LSMW itself, however, works with physical file names. To be able to transfer the LSMW file with the converted data to the import program, you must specify a logical file name for the file with the converted data in addition to the physical file name. In this case, the system displays additional fields in the 'Specify files' step in which you must enter the logical path and file name.
Solution
The error messages may be due to several causes. Check the following:
Have you maintained the logical path and logical file name and have you assigned them to the physical file specified in the "File" input field of transaction LSMW?
These settings are maintained in transaction FILE.
When you use logical file and path names, you must specify the name of the physical file with its path. If you have not specified any directory, you cannot assign any directory to the logical path in transaction FILE. In this case, the system uses the SAP Home directory on the application server by default. Bear in mind that the file name must not exceed the maximum length of 45 characters, including the path.
Up to LSMW version 1.7.2 (*):
If the logical file name specified does not point to the physical file (although it should do), the system adjusts the logical file name, that is, the information in transaction FILE is changed to the entries made in transaction LSMW. This may lead to unwanted side effects if the logical file is also used somewhere else. Therefore, SAP recommend that you always use separate logical paths and file names for transaction LSMW (the problem is corrected as of LSMW version 1.8.0, see below). If the logical file does not exist yet, it will be created upon request.
As of LSMW version 1.8.0 (*):
The settings of the logical file are checked but no longer adjusted automatically as in version 1.7.2 (see above). If there are inconsistencies, the system issues an error message. If the user is authorized to maintain logical paths and file names (as for transaction FILE: "Maintenance authorization for cross-client tables"), transaction LSMW can create the logical path, the file name and the file. Due to this automatic generation, the user no longer needs to make adjustments in transaction FILE. Therefore, we especially recommend this procedure.
To display the version of transaction LSMW, select "Extras" --> "Display LSMW version" in the main menu of the initial screen.
You should also bear in mind that as of Basis Release 6.20, that is, as of LSMW version 4.0, transaction LSMW is no longer an add-on but is delivered with the standard system.
Hope this helps,
Rgds,

Logical file name or logical path name incorrectly defined

Dear All,
We are doing archival in our IDES for test purpose before we do it to our Production.
Steps Performed
Copied AM_ASSET archive object to ZAM_ASSET
Logical Path
Logical path ZAM_ASSET
Name Asset
Syntax group UNIX Unix compatible
Physical path /archive/test/<FILENAME>
Logical File Name
 Logical file ZAMASSET
 Name Asset
 Physical file FI_<MONTH>_<DAY>.txt
 Data format ASC
 Applicat.area AM
 Logical path ZAM_ASSET
But when we run the WRITE though SARA , in the job log we get the following
Logical file name or logical path name incorrectly defined
When generating a file name for an archive file that is to be created, the system determined that the logical file name FIAA_ARCHIVE_DATA_FILE or the logical path name ARCHIVE_GLOBAL_PATH was defined incorrectly.
But we have maintained a Logical name ZAMASSET , so we are unable to change the location of archived file and as well as the format.
So is there any setting we need to maintain apart from the logical file name and logical file path.
Suggestions are highly appreciated.
Thanks in anticipation

hi,
follow this steps :
- transaction SARA
- enter authorization objects, eg SD_VBAK
- hit button CUSTOMIZING
- Archiving Object-Specific Customizing: execute Technical Setting
- field Logical File Name enter or select ARCHIVE_DATA_FILE
- leave CONTENT REPOSITORY as blank if you are not using 3rd party for storing (eg. IBM Tivoli)
- back to customizing
- from Basis Customizing, execute : Cross-Client File Names/Paths
- on Logical FIle Path Definition, highlight (select) ARCHIVE_GLOBAL_PATH on the right pane
- double click on the Assignment of Physical Paths to Logical Path on the left pane
- double click on OS used, eg. UNIX, define Physical Path where archive file (on WRITE process) will be stored
- save changes made
- double click Logical File Definition, Cross Client on the left pane
- double click ARCHIVE_DATA_FILE on the right pane
- make sure that logical path is already set to ARCHIVE_GLOBAL_PATH
- save changes made
this setting also can be done using transaction FILE
we have experienced on this case using SAP standard archiving (SARA, SARI) and everything is fine with this setting above.
hope it help you.
rgds,
Alfonsus Guritno

SFLIGHT is NOT defined for the current logical database.

I have just started learning ABAP and bought an ABAP Objects book by Horst Keller. I have installed 4.6d mini sap and SAP GUI 6.4 on win XP Prof. I executed S_FLIGHT_MODEL_DATA_GENERATOR to load DB tables.
(1). When I tried to check a sample program, I get an error message SFLIGHT is not defined for the current logical database.
Here is the partial code:
REPORT zbcb01f1 .
TABLES: sflight, sbook.
DATA: BEGIN OF sr OCCURS 100,
 carrid LIKE sbook-carrid,
 connid LIKE sbook-connid,
 fldate LIKE sbook-fldate,
 bookid LIKE sbook-bookid,
 order_date LIKE sbook-order_date,
 loccuram LIKE sbook-loccuram,
 END OF sr.
GET sflight. <---- Error is pointed here
(2). I am also not getting Graphical Screen Painter when selecting Layout for a screen. Instead, I am getting alphanumeric editor.
Someone please help me.
Raizak.

Hi Raizak,
the easiest way is to go to service.sap.com/notes and enter the note number. For this time I've copied the 2 notes below.
Best regards,
Christian
Symptom
The Graphical Layout Editor of the Screen Painter either does not start or terminates.Error message 37527 is displayed in the session in which the call was made (Graphical Layout Editor not available.
Additional key words
() EUNOTE, EUSCREENPAINTER, 37 527
Cause and prerequisites
This note comprises all the common causes for error message 37527 and provides you with information on how to systematically trouble shoot the problem.
1. Windows32 or UNIX/motif?
As of Release 4.6B there is only the program version for 32bit Windows (NT, 95, 98, 2000 ff.).Up to Release 4.6A there was also a version for UNIX/Motif.All of the more current notes (with the exception of Note 45490) refer only to the Windows version.
2. Termination at the start or during use?
The following diagnostic steps refer to the causes of the errors which prevent the Graphical Layout Editor from starting. However, there are also known error causes, which result in the program terminating when the application is being used and which also produce the 37527 error message. This affects -
Rel.4.6C/D: Termination when attempting to read texts in the logon language -> Note 375494
Crash after transferring program and dictionary fields. Termination after transferring program and dictionary fields -> Note 189245
Release 3.1I: Termination after inputting field text -> Note 113318
3. Is the SAPGUI installation correct?
The Graphical Layout Editor is automatically installed during the standard installation of the SAPGUI.If you chose a non-standard installation, then you should have explicitely selected its installation (component "Development Tools - Graphical Screen Painter").
The program executable is called gneux.exe.During the SAPGUI installation it is placed in the same directory as the SAPGUI programms (for example, front.exe) (usually C:\Program Files\SAPpc\sapgui). The following belong to the program:
- An additonal executable gnetx.exe (RFC starter program)
- the DLL eumfcdll.dll
- various eusp* data files (that is, the names all begin with eusp.)
You can check the completeness of the program installation by starting the program gneux.exe locally in the SAPGUI directory (for example, by double-clicking on the program name in the Explorer window).The Layout Editor is displayed with German texts and an empty drawing area for the pseudo screen EUSPDYND 0000.
If the installation is not complete, an error dialog box provides information regarding the cause of the error, for example, sometimes the DLL eumfcdll.dll is missing after reinstalling the SAPGUI. For example, the eumfcdll.dll DLL was sometimes missing after the SAPGUI was reinstalled.
4. System link defined and okay?
The Graphical Layout Editor is a separate program which is started by the Screen Painter Transaction (SE51) on the Frontend machine.
Up to Release 3.0F, the programs communicated with each other via the graphics log of the SAPGUIs (gmux).The definition of the environment variable SAPGRAPH may be the cause for the program not being being found where it is.
As of Release 3.1 G, the programs use a separate RFC link which is set up in addition to the SAPGUI's RFC link.Missing or incorrect definitions of the RFC destination EU_SCRP_WN32 or problems with the creation of the RFC link are the most frequent causes for error message 37527 being displayed.Below you can find the correct settings for the RFC destination EU_SCRP_WN32 (under "Solution").Note 101971 lists all the possible causes for problems with the RFC link set-up. Attention:The Graphical Layout Editor may not be operated through a firewall (for example between the SAP and the customer system) because this does not allow an additional RFC connection in addition to the SAPGUI.
Solution
ad 1 UNIX/Motif
Note 45490 describes possible errors resulting from an incorrect program installation under UNIX/Motif (up to Release 4.6A).
ad 2 Termination when using
The above-mentioned notes may contain options for solving individual problems.However, you usually have to replace the program with an corrected version.You can do this either by downloading a patch from sapservX or by installing a more current SAPGUI.The patch is mentioned in the respective note.
ad 3 Installation
You either need to reinstall the SAPGUI or manually copy the missing file into the SAPGUI directory.In both cases you should make sure beforehand that a Graphical Layout Editor is no longer running.To do this you can either remove all processes gneux.exe from the process list by using a tool such as Task Manager (on WindowsNT) or exit the Graphical Layout Editor from the Screen Painter Transaction menu via Edit -> Cancel Graphical Screen Painter). Attention:For each session or system an individial Layout Editor process may exist so that, if need be, several processes should be cancelled.
ad 4 System link
Up to Release 3.0F:you can either delete the environment variable SAPGRAPH or copy all the files of the Graphical Layout Editor into the directory which is specified by SAPGRAPH.
As of Release 3.1G:you can use Transaction SM59 to check the RFC destination EU_SCRP_WN32 (expand the TCP/IP connections, select destination EU_SCRP_WN32).If the destination is missing, then you should create it with the following settings:
- Connection type "T" (start of an external program via ...)
- Activation type "Start"
- Start on "Front-end workstation"
- Front-end workstation program "gnetx.exe" (caution! NOT gneux.exe)
- Description (optional) "Graph. Screen Painter (Windows32)
Start Program gneux.exe using the gnetx.exe starter program."
If you want to start the program from a different directory than the SAPGUI standard directory, then replace the default value under Frontend work station by the complete path name for program gnetx.exe.Transaction SM59 also allows you to check the RFC connection via the pushbutton "Test connection").In this case the system attempts to localize and start the program gnetx.exe.If there are errors, a message is displayed regarding the possible causes (for example, gateway problem, timeout problem or the like).Note 101971 provides a detailed explanation of the problems involved with an RFC connection set-up.As the Graphical Screen Painter requires a functional RFC connection as of Release 3.1G, contact the System Administrator or create an message on the topic Middleware (BC-MID-RFC) if you encounter RFC problems.
If the program gnetx.exe can be found and started, the banner dialog box with logo, release data and version number is displayed briefly.As the Layout Editor itself is not started, the error cause must be in the installation of the Layout Editor program gneux.exe if the connection test was successful.
Release 4.5A to 4.6B: Use with Releases <3.1G>.
The Graphical Layout Editor is downward-compatible as regards the system connection, that is, an RFC-based Layout Editor for example from Release 4.6C can also be used on a non-RFC-based Screen Painter, for example of Release 3.0F.However, the releases mentioned above have a program error which causes a crash due to memory violation in the start phase of the program.Note 197328 describes the solution by installation of the corrected program version.
Important: Trace file dev_euspNNN!
If none of the diagnosis steps leads to the cause of the error and to the solution of the problem via the corresponding note, then you should add the contents of the trace files dev_euspNNN (NNN = process number) to the message for SAP, if possible.You can find this file in the current directory of the SAP System, for example under Windows NT in C:\Winnt\Profiles\<user>\SAPworkdir.If several such trace files can be found there, make sure that you use the file which matches the termination time with respect to date and time of creation.In most cases the ERROR message in the last lines of this trace file provides an important note on the cause of the error.
Source code corrections
Symptom
The graphic layout editor of the Screen Painter cannot be started (RFC version).
Other terms
() EUNOTE, EUSCREENPAINTER
Reason and Prerequisites
This is generally caused by the fact that the RFC connection between the frontend graphics layout editor and the calling screen painter program at the backend cannot be set up.
Possibility 1: Route permission denied
In the trace file dev_eusp<Process Id> of the graphics layout editor you find the entry "ERROR in RFCMgr_accept: not accepted", and in the RFC trace file dev_rfc.trc you have an entry of the form "ERROR route permission denied (<Front-Id> to <BackId>,<Service>)".
If there is a firewall between frontend computer and application
server, you need to decide whether the port for the RFC of the graphical layout editor can be released here (see Solution 1 below).
In case no firewall exists between the frontend computer and the application server, in its route permission table, the SAProuter contains either no entry for the frontend computer, on which the graphics layout editor is started, or the entry says that the link is saved by a password.Since the connection is denied, the graphics editor processes exits again, and the screen painter switches to the alphanumeric layout editor.
Possibility 2: Service 'sapgw<ServiceId>' unknown
In the trace file dev_eusp<ProzessId> of the graphics layout editor you have the entry "ERROR in RFCMgr_accept: not accepted", and in the RFC trace file dev_rfc.trc you have an entry of the form "ERROR service 'sapgw<ServiceId>' unknown".
The service sapgw<ServiceId> (for example, sapgw00) is not known on one of the computers participating in the RFC communication because the corresponding entry is missing in its service file. The affected computer can be the frontend computer or the gateway computer.
Possibility 3: The system parameter gw/cpic_timeout value is too low
This system parameter determines how many seconds the gateway is waiting for the RFC connection to be set up.In case of a high network load, the default value of 20 seconds is too small with the result that the connection cannot be created on time.Here the graphics layout editor process also exits with the trace file entry "ERROR in RFCMgr_accept: not accepted".
Possibility 4: System parameter abap/no_sapgui_rfc set
The profile parameter abap/no_sapgui_rfc of the system is set (that is, it has a value not equal to space or 0).This prevents the program of the graphics layout editor from being started with RFC at the frontend.
Possibility 5: Unnecessary authorization check
The error message "No RFC authorization for user xxxxxx" is generated although the check of the RFC authorization was deactivated by profile parameter auth/rfc_authority_check (value = space or 0). The problem is caused by a program error, that ignores the value of the profile parameter let during the call of the RFC authorization check (see Note 93254). This error can occur as of Release 4.5.
Solution
ad 1) If a Firewall is installed between frontend computer and the application server, you need to decide whether the port for the RFC link of the graphical layout editor shall be released in the firewall. This is port 33nn, where nn is the 2-digit system number of the SAP application server. As of Release 3.1G, the graphical layout editor needs an RFC link for communication with the application server in addition to the already existing linkof the SAP GUIs. Such a second link is not allowed by the firewall in general because it would contradict the security concept (password protection, logging of the connection).
If no firewall exists, you should check whether the frontend computer can be added to the route permission table or whether the password option can be removed from out of the available entry.
For details refer to chapter 4.4 of the attached Note 30289.
ad 2) Include service sapgw<ServiceId> in the service file.
Refer to Note 52959 for details.
ad 3) Increase value for system parameter gw/cpic_timeout. 60 seconds should be sufficent as a timeout limit.
ad 4) Set the system parameter abap/no_sapgui_rfc to space or 0
Start the application server so that the new parameter value comes into effect.
ad 5) Import the Support Package specified in the attachment for the release in question or implement the advance correction in the source code as described in the attached correction instructions.
As a workaround, assign RFC authorizations as described in Note 93254.

Logical System is Not Defined in EBP...

Hi SAP GURU's,
Please do Accept My Thanks for Kind Help
Rendered So far ..
My issue is whie working wih Accoutn Assignment is EBP ,I Tried to Maintain Logical System ..But system is throwing Error Massage Logical System is Not Defined in EBP..
Where as it was Defined and Assigned to the Client
in the Configuration ...
The Same thing has been defined in R/3 also ...
what Could be the Reason..? ? ?
Could Any Gentleman through Some light on this
Suitable Points Assigned for the Right Answer
Thansk in Advance
Adarsh

Hi,
Pl define the same logical system names in the Define Back end systems or in the Table
bbp_backend_dest.
Thanks & Regards,
Nagarajan

Logical System is not defined in table SMOF_ERPSH!

Hi,
When i am replicating a material group to SRM system, in SMQ2, the error message appears as 'Logical System is not defined in table SMOF_ERPSH!'.
can any one please let me know why this comes up, i have checked the SMOEAC settings, its fine and the logical system entries are already present in the tabe

Hi,
Can you verify all your settings as per note 720819?
Also under SMOEAC transaction, site attributes for your site type 'CRM' may not have any value. Please define attributes for your SRM RFC destination. Select the correct RFC destination, then click on button 'Get Values'.After doing this, table SMOF_ERPSH should be populated correctly.
Regards,
Nikhil

My app went from working fine to: Id field not defined for cfc Path.to.my.ORMCfCPag when I restarted

Hi everyone,
I have a CF9 ORM problem that I haven't been able to figure out and thought I'd see if you had any idea. I have seen a few postings talking about a "similar" problem but none of them correctly resolved this particular issue. I appreciate any help you can offer.
I recently created a CF9 app where I generated scripted ORM CFCs for my app using ColdFusion Builder. It worked great and my app was completely working. However, when I was adding some enhancements, I ran into an error when I restarted the CF app server. Here's the message I keep getting:
"Id field not defined for cfc Path.to.my.ORMCfCPage. Either the table should have a PK column mapped to a cfc field OR at least one field should be specified as id."
My App.cfc file only had orm enabled (no other mappings) when it was working. I've since tried specifying things like the cfc location etc. and it still hasn't helped.
// MORE DETAILS:
- When my app was working, I had moved it to 2 other servers. I had this error on both of those but not on my local copy. They all use the exact same database.
- The last change I made before the error was adding a generator="identity" field to my generated ORM beans. Once I got the message, I tried changing it back and restarting again but still got the error.
- I've also made sure all of the Adobe tags are in my web root (as suggested in a prior posting about this problem). I've search all over for a solution and nobody has a solution posted online that works so far.
Do you have any idea why this is happening?
Thanks!
Jeff

Quick thought and probably not relevant, but do you have this.ormsettings.savemapping set to true in your Application.cfc? I've fallen foul of this before - once CF has generated the hbmxml files and saved them to disk you can make all kinds of changes to your code which won't make a difference as it'll continue to read from the file versions, but only for certain properties and methods at times it seems.
Long shot I know, but I found CF ORM to be a nightmare for seemingly random caching.

Logical Path not defined..?

Similar Messages

Maybe you are looking for