Highlighted
Honored Contributor.
Honored Contributor.
2640 views

Attachment Control Interface Error ; Groupwise 2012

Trying to upgrade clients to Groupwise 2012.
Made a bundle with zenworks 7, deploying, all works, MSXML, WSE3, Groupwise Client.
Only on startup I am getting an Attachment Control Interface Error.

On the forum I could find an old post for groupwise 6 with a temp folder not being present,
checked but not the case.

Also something about a bindery server, for version 5

Any ideas ?

Stephan
Labels (2)
0 Likes
13 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

What OS and SP are the workstations?

Are the users Local Admin's?

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Hello Laura,
Workstation(s) ( I only tried 2, before distributing ) are all XP Sp3's
Stephan
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Hi Stephan,

Are the users local admin's on the workstations?

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Dear Laura,
I distributed under admin user, so yes.
Stephan
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

On an affected computer, logged in as the user affected try the following:

Right-click My Computer, go to Properties, Advanced, Environment Variables, under User Variables for x user check the Variable called TEMP - it should point to something like this: %USERPROFILE%\Local Settings\Temp

Double check that path and verify if the user in question has full permissions to that folder.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Yes it does :
%USERPROFILE%\Local Settings\Temp
equals C:\Documents and Settings\admin\Local Settings\Temp
And yes user has full permissions.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Hi Stephan,

I'm all out of ideas. Sorry! I have personally never encountered this error before.

Maybe one of the GroupWise guru's will pick up on this thread and have some brilliant ideas for you.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi Stephan,

I'm having the same error on a Windows 7 & GroupWise 2012 Client.
Deployment is by MDT, with MSXML and WSE installed first.

Did you already solve this one...

TIA,

Cheers,

Marc
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Dear Marc,
No I did not solve this. so the clients PC's are still at Client 8.
I had no time yet to search what the "Attachment Control Interface" is and where it is installed.
I had 1 PC where I first deleted the GW 8 client manually and then installed the 2012 client, that worked.
So something must be wrong with updating some parts of the GW client.
My plan is to do the uninstall and install thing, with Snapshot, so to see which things have changed.
But the next two weeks are full....
0 Likes
Highlighted
Absent Member.
Absent Member.

stelgenkamp;2245220 wrote:
Dear Marc,
No I did not solve this. so the clients PC's are still at Client 8.
I had no time yet to search what the "Attachment Control Interface" is and where it is installed.
I had 1 PC where I first deleted the GW 8 client manually and then installed the 2012 client, that worked.
So something must be wrong with updating some parts of the GW client.
My plan is to do the uninstall and install thing, with Snapshot, so to see which things have changed.
But the next two weeks are full....


Hi Stephen,

Well I worked arround the problem since I have to do only clean GroupWise Client installs on a Windows 7 deployment with MDT 2012.
I've adjusted the setup.cfg , copied it to the win32 folder and run the setup.exe.

No .mst files etc.

And this works without any problems.

So I agree that 'something' is not copied over or installed when you use the .mst option. But which component I don't know.

Cheers,

Marc
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Dear Marc,

Ok, nice that you got it working. What did you adjust in the setup.cfg ?

Stephan
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.