web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Customizations fail on...
Microsoft Dynamics SL (Archived)

Customizations fail on 64-bit client

(0) ShareShare
ReportReport
Posted on by Richard West 525

This weekend I upgraded our environment from SL 6.0 to SL 7.0 (SP3).

Overall the upgrade smooth with one big exception.

On our client computer we are running Windows 7 64 bit (which is supported in FP1 and above, according to the documentation). There were several issues in getting the client up and running (we had to mannually register capicom.dll located in the SysWOW64 folder).

Now the client appears to be up an running OK execpt for any screen that we hve VBA customizations on. The first time the user launches the screen everything works fine. The customizations are in place and work as expected.

When the user closes the screen, then later opens the same screen errors begin to occur: http://img535.imageshack.us/img535/5625/error1c.png

When this screen is closed the "normal", non-customized version of the screen is loaded.

When the users closes Dynamics SL completely, then reopens SL, a different error is dispalyed when they try to open the same screen as before:  http://img90.imageshack.us/img90/8682/error2d.png

The screen will never load at this point and the only solution is to reimport the customizations. At this point everything repeats: First load is good, second load has compiler error, and third time error loading VBA project is displayed.

Has anyone seen this type of behaviour before? This has caused us to roll back our upgrade from version 6 to 7 that occured over the weekend and right now we are at a standstill trying to figure this out.

This problem does not occur on a client that is running Windows 7 32-bit. It only appears to occur on the 64-bit platform.

Obviously it is not my first choise, nor recomendation, that we downgrade to Win 7 32-bit, so I am hoping for a different solution.

Thanks,

Richard 

 

 

 

*This post is locked for comments

I have the same question (0)
  • hassanvoyeau Profile Picture
    hassanvoyeau 580 on at
    Is there a compatibility mode in 64bit for 32bit or something similar? If that is true you can find out from MS if that is supported as a workaround until you figure out what the problem is. Also, did you do a upgrade of the client or a fresh install. A fresh install with the client making sure to backup old client installation folder might be worth a try.
  • Richard West Profile Picture
    Richard West 525 on at

    This was a fresh install on a new PC running Windows 7 64-bit.

    As far as I know there is no mannual way to specificy a compatibility mode. The SL client application is a 32-bit application. As such a 64-bit OS automatically recognizes this and installs and runs it from the "Program Files(x86)" folder and the SysWOW64 folder.

    In further testing I have deleted all customizations from the database be executing the following SQL queries against the SYS database.

    delete from Custom
    delete from Custom2
    delete from CustomVBA

    I then was able to open the screens and work as normal - although without the customizations I can not fully function -- this only proves the test.

    I then created a new customization that simply added a textbox control. Save the customization (All Users level). When I would reopen this screen I had the same problems that I had when using my original customizations. This would seem to eliminate something specfic in my original customizations, and more of a problem with the 64-bit client being able to execute ANY customizations.

  • hassanvoyeau Profile Picture
    hassanvoyeau 580 on at
    Sounds like your problems are on the server side. Is this client/server or standalone installation?
  • Richard West Profile Picture
    Richard West 525 on at

    Client Server installation.

    Server is running Windows 2008 32-bit.

    Client Windows 7 64-bit - regardless of user account logged in - has the problem.

    Clients running Windows 7 32-bit - regardless of user account logged in - do not have this problem.

    That makes me think this is more of a client issue than a server issue. A server issue would seem to affect all users and all client systems. This is specfiic to the 64-bit OS client, regardless of the user account running on that workstation.

     

  • hassanvoyeau Profile Picture
    hassanvoyeau 580 on at
    Did you choose VBA for your installation? I can't remember what the other option is.
  • Richard West Profile Picture
    Richard West 525 on at

    Yes -- I choose VBA.

     I think the other option is BSL.

  • hassanvoyeau Profile Picture
    hassanvoyeau 580 on at
    This would be my last suggestion. You might want to check the installation/related folders and make sure that the permissions are in line with what exists on the other clients.
  • pbrattin Profile Picture
    pbrattin 1,850 on at

    I have 95% confidence that the problem has nothing to do with 64Bit. Rather it is a VBA problem that existed in 6.5 and 7.0 and occurred on Vista and Win7 32 bit and 64 bit. It and caused me some headaches until I figured out how to fix it. The fix is easy. See Article ID: 971965.

    We run Win7 and Vista 64 bit with no problems. 

     

  • pbrattin Profile Picture
    pbrattin 1,850 on at

    From the Solomon partner newsgroup: 

    Subject: Re: Can't find Project or Library (Trim function)   4/21/2010 11:35 AM PST
    By:   Jeff Williams  In:   microsoft.private.mbspartner.solomon
     
    I have ran across a few things that can cause that

1) reregister/install the vba components.
2) delete the temp kernel files (the swimapi.k* files)
3) some other 'reference' in the vba project is missing or invalid.

On 4/21/2010 12:23 PM, tom malia wrote:
> I know I’ve seen this somewhere before that this is a know problem.
>
> Client has a customization that uses the TRIM function in some VBA code…
> all was working fine until “Update Tuesday” yesterday.
>
> Now they get an error message “Can’t find Project or Library” and the
> Debugger stops on the “Trim” function.
>
> What causes this and what was the resolutions again?
>
> Tom Malia
>
> T&T Data Solutions L.L.C. <http://www.ttdsinc.com>
>
.

     

  • Richard West Profile Picture
    Richard West 525 on at

    Ohhh, that sounds like my exact problem -- even down to the TRIM function.

    I have tried deleting the swimapi.k* files from the "C:\Users\<profile name>\AppData\Roaming\Microsoft Dynamics SL\APC" folder.

    Can you advise on how I can reregister/install the VBA components?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans