08-18-2010 07:13 AM
I just started getting this error message when I tried building my project:
ERROR - C:\Users\ejeffries\AppData\Roaming\Sage\Platform\O
at Mono.TextTemplating.TemplatingEngine.Run(Assembly assem, String type, ITextTemplatingEngineHost host, CultureInfo culture)
I get a ton of these and have absolutly no clue what they mean or how to go about fixing them. It happens right after it attempts to Generate a Server Entity for each of the components of the project such as attachements, contacts and accounts.
Any help would be greatly appreciated!
08-19-2010 02:14 PM
I do not have a specific instance where I have seen this error, but have you tried to delete the contents of the output folder and perform a rebuild?
Did you do anything just before this starting? Which version are you on?
08-20-2010 12:07 PM
I tried to delete the output folder to no avail. I am on version 188.8.131.521.
There was nothing changed that I was aware of.
I actually gave up and reverted back to an old copy. Though this is an odd issue it seems to be a bug of sorts.
09-02-2010 03:22 AM - edited 09-02-2010 03:23 AM
I too had this issue, I managed to get around it by a full rebuild, i've only had this issue once, and never again since that full build. I'm not sure why a full build fixed it.
09-15-2010 09:28 AM
Good point. A build->rebuild might do the trick.
In class this week I have seen something similar and simply opening the snippet (business rule, event, whatever) in question resolved the issue. Just open the item that is failing (using the menu on the left -- not a double click on the error) and then a rebuild may let you progress.
I know it is strange, but something seemed to get corrupted and this resolved it.
We might have to add this to the boot camp presentation on debugging SalesLogix -- http://www.sagesaleslogixbootcamp.com/
09-23-2010 03:01 PM
Try a “Nuke and Pave” with the re-generate ModelIndex file option:
1. From Application Architect, choose ‘Tools -> Build Settings’ from the menu and note the Build and Assemblies paths
2. Close Application Architect
3. Issue an IISRESET
4. Delete all files and subdirectories from the following folders:
a. The Build path from Step 1 above
b. The Assemblies path from step 1 above
c. C:\Documents and Settings\All Users\Application Data\Sage\Platform\WebPortal\Design\SlxClient
d. Your deployed website (Usually C:\Inetpub\wwwroot\SlxClient)
5. Determine if you project is stored in the database VFS or on the Local Disk (LFS):
a. Open the Project Explorer window in AA (left dockable window)
b. Open the Project Workspaces window in AA (bottom dockable window)
c. Look at the name of the current project in the Project Explorer window and find that name for the corresponding project in your Project Workspaces folder
6. Delete the ‘ModelIndex.xml’ file.
a. If you’re working in a VFS:
b. If you’re working in a LFS:
7. Do a build and deploy.
8. Note that these steps will force a full rebuild of your project and cause the ModelIndex.xml file to be re-generated.
03-11-2011 10:24 PM
I thought I would add to this post in hopes that it would save someone else some grief.
I had this same issue and spent many sleepless nights working it out. All of the above tricks didn't help.
What I finaly found, is that all of my C# Code Snippet Properties on my entity got corrupted. If I tried to open the property in the editor window, it threw an error.
I dropped and readded my code snippet properties, and everything was right in the world again.
04-04-2011 10:08 AM
I can think of two possible reasons why you might get a null reference exception on a code snippet property. A code snippet property is composed of a *.method.xml file, a *.codesnippet.cs file (or *codesnippet.vb file), and a reference to the method file in the *.entity.xml file. If the snippet file or the method file are missing, you could get a null ref. There's no good way to fix this except remove the remnants (copy out the snippet content if it still exists) and start over.
The other possibility is that the in-memory snippet object didn't get initialized correctly and the references between the entity and the snippet objects couldn't be resolved, resulting in a null ref exception. I don't really know why this would happen, except I fixed a few similar types of issues in some related areas. Maybe the snippet was left open in a previous AA session and in the following session it was opened automatically, but not correctly initialized. Resolution may just involve touching the snippet in a different way - a full build, opening the entity and then the snippet, etc.
It sounds like both resolutions have been used successfully, so this may actually be two different defects and not one. In either case we'd like to fix the underlying issue. If you can provide steps to reproduce the issue, PLEASE share so we can get this resolved.
04-04-2011 10:46 AM
The issue is very easy for me to replicate, but it only occures with certain Entities. they happen to be a large entities with just over 100 properties, 10 code snippet properties, and a dozen business ruels and events.
I've determined that if I attempt to modify the entity by adding a new field or modifying an existing one, the issue occures. It seems the best way to trigger the issue (every time), is to change the size of a property on the Entities "Propertyies" collection. On saving the changes, the Entity appears to rebuild. It appears that the size of the entity causes an issue with resources, and I get an "Out of Memory Exception" almost every time. My guess is that it is unable to complete the build, and the code snippet properties are the victim. Deleting the CS properties and readding them is the only means for resolving the issue that I've been able to find.
The Out of Memory Exeptions, seem to be the source of most of my issues. I can replicate these in our dev environment, as well as at at a clients site. One has Windows 2003, the other has Windows 2008 R2.
I have gone as far as completely logging out of AA, and then loging back in, just to do the Entity change. This will be successful about half of the time. I get the same memory exception error when working with a large smart part (100 or so controls), and attempt to move them arround. There seems to be certain opperations that cause a complete rebuild of the underlying XML that don't have much success with large operations. To put it another way, there seems to be limit on the size of an entity or smart part that effects stabiltiy.
I'm more than happy to demonstrate the issue if you would like.
Please let me know if there's any additional detail you would like.
04-05-2011 01:29 PM
Thanks for the info!
It sounds like you really have more of a memory usage issue rather than specifically a code snippet issue.
That's just as serious, if not more so, so let's try to figure out what is going on.
Saving an entity shouldn't trigger a build.
Are you sure a build was being performed or did you just notice a lot of disk I/O?
Did you see build messages in the output window?
Were you saving a single file or multiple items?
Your large entity sounds pretty close to the out of the box Account entity. Do you think a few more properties would push Account over the edge to manifest the problem?
Are you working with a limited amount of memory on the AA machine?
It might be very helpful if you could provide a video (maybe using something like Camtasia) starting from a just logged in AA though your usage to the out of memory exception.