Re: Windows 2003 server, Exchange 2007, Windows 2000 workstation, Outlook 2003, and Client Access V5R2

if you google "cwbsvstr.exe" many techie sites (non-as400) list this as an optional pgm that can be removed from startup. Have your MS techs been doing such things?
jim
----- Original Message ----- From: "Charles St-Laurent" <dringpiece@xxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Monday, May 28, 2007 3:46 PM
Subject: Re: Windows 2003 server, Exchange 2007, Windows 2000 workstation,Outlook 2003, and Client Access V5R2

Hi!

We tried that solution and it does not work...

Charles


"Jim Franz" <franz400@xxxxxxxxxxxx> a écrit dans
le message de news:00a801c7a15c$bce0a2d0$5b03000a@xxxxxxxxxxx

Not a pretty solution, but has it worked to reinstall CA on one of those
pc's?
jim
----- Original Message ----- From: "Charles St-Laurent"

<dringpiece@xxxxxxxxxxx>

To: <midrange-l@xxxxxxxxxxxx>
Sent: Monday, May 28, 2007 2:23 PM
Subject: Windows 2003 server, Exchange 2007, Windows 2000
workstation,Outlook 2003, and Client Access V5R2


> Hi!
>
> We migrated our windows server last weekend. We had a Windows 2000

server

> and now we have a Windows 2003 server. We also migrated to Exchange > 2003
> mail server. On each workstation, we installed Outlook 2003. We have
> Client
> Access V5R2 installed on these workstations. Each workstion has Windows
> 2000
> installed.
>
> Now we have a problem. Half of the workstations cannot connect to our
> iSeries. At computer startup, we got an error message box about a

program

> called "cwbsvstr.exe" and an error about __crtLCmapStringW and

msvcrt.dll.

>
> We I try to open a conection to our iSeries, I get an error message box
> about "cwbemlic.dll" that cannot be loaded. But the dll is still in my
> C:\program files\IBM\Client Access\Emulator...
>
> I tried to repair my registries with XP Repair Pro. It did not solve > the
> problem...
>
> Help! Half of our users cannot connect to our server!!!
>
> Charles
>
>
>
> -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email:

MIDRANGE-L@xxxxxxxxxxxx

> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email:

MIDRANGE-L@xxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--------------------------------------------------------------------------------

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.