Highlighted
Absent Member.
Absent Member.
3790 views

upgrade question

currently at version 1.0 build 115... should we be able to patch to the latest 1.1 patch using yast???
Labels (1)
0 Likes
21 Replies
Highlighted
Absent Member.
Absent Member.

kautium wrote:

> We don't have high hopes about opening a Support Request.


It's what you're going to have to do.

> I'm really starting to hate Novell for releasing crappy code all the
> time. 😞


If it was crappy code, then the problem you're describing would affect
many many customers. Yours is the only one I can think of where no
items sync from devices to GW and affects every single user of that
Mobility installation. Seems more like a problem in your environment.
Many other customers are successfully using Mobility, syncing data
between GroupWise and mobile devices.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

jmarton;2105139 wrote:
If it was crappy code, then the problem you're describing would affect
many many customers.

I think so too, but considering that this forum is full of stories about problems that occur randomly in same kind of environments, it is not very far fetched that this is a problem that could occur for others too.

And yes, i'm sorry to say, but i really think that Novell has produced tons of crap within last years.

jmarton;2105139 wrote:
Seems more like a problem in your environment.

Possibly, but isn't it even a bit weird that this situation occured right after a simple update?

I updated SLES --> reboot --> updated working datasync 1.0 build290 to 1.1.1 (with update.sh) --> reboot --> stuff wont sync from devices to GW anymore

jmarton;2105139 wrote:
Many other customers are successfully using Mobility, syncing data
between GroupWise and mobile devices.

I bet there is not a single customer using datasync without any problems. 1.0 build 290 was pretty stable for us, but still some users were experiencing weird problems with it from time to time.
0 Likes
Highlighted
Absent Member.
Absent Member.

kautium;2105149 wrote:
I think so too, but considering that this forum is full of stories about problems that occur randomly in same kind of environments, it is not very far fetched that this is a problem that could occur for others too.

And yes, i'm sorry to say, but i really think that Novell has produced tons of crap within last years.


Possibly, but isn't it even a bit weird that this situation occured right after a simple update?

I updated SLES --> reboot --> updated working datasync 1.0 build290 to 1.1.1 (with update.sh) --> reboot --> stuff wont sync from devices to GW anymore


I bet there is not a single customer using datasync without any problems. 1.0 build 290 was pretty stable for us, but still some users were experiencing weird problems with it from time to time.


I too am going to update to version 1.1.1 today from 290. I tried this before and it really screwed up my system ( not sure what happened) I too am running this on a VM and had to roll back to a snapshot. the problem was that the snapshot was taken 20 hours before the messup. Rolling back is fine however your customers will loose any appts on their calendar that were made from the time of the snapshot to the time of the roll back. Easy fix for this is to go to the web admin and choose to resync their device. Then everything will come down (with the exception of re-occuring appts)
0 Likes
Highlighted
Absent Member.
Absent Member.

kautium wrote:

> I think so too, but considering that this forum is full of stories
> about problems that occur randomly in same kind of environments,


Um, so are Microsoft's forums, VMware's forums, Citrix's forums, etc.
If software didn't have problems there'd be no need for forums. People
don't go there just to post "Everything is working fine. Just an FYI."

> And yes, i'm sorry to say, but i really think that Novell has produced
> tons of crap within last years.


That's your opinion, but fact of the matter is many people are
successfully using Mobility.

> Possibly, but isn't it even a bit weird that this situation occured
> right after a simple update?


Still doesn't mean there isn't an issue in your environment, especially
considering that you state every user is affected.

> I updated SLES --> reboot --> updated working datasync 1.0 build290 to
> 1.1.1 (with update.sh) --> reboot --> stuff wont sync from devices to
> GW anymore


Using both builds 315 & 343 here and they are both working fine.

> I bet there is not a single customer using datasync without any
> problems.


You might be right, but don't forget there are two sets of issues:

server issues (GW or Mobility)
device issues

The device issues often can't be helped and would be present with just
about every syncing solution. I've had a number of cases where devices
suddenly stop receiving mail... only to discover the user accidentally
put the device into airplane mode.

The fact that a total of four updates has been released in a relatively
short amount of time does show there are issues, but at the same time
also shows the committment on the part of Novell to address them as
quickly as possible given just how important mobility is for all
customers.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

tschwartzniu wrote:

> I too am going to update to version 1.1.1 today from 290. I tried
> this before and it really screwed up my system ( not sure what
> happened)


It shouldn't, and I'm fairly certain others here have done the same
without issue. Here we went from 290 to 315, while our 343 server was
a fresh 343 install. I personally haven't tried 290->343 or
290->315->343, though I'll be doing the latter soon.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

On 11.05.2011 14:36, kautium wrote:
>
> We don't have high hopes about opening a Support Request.


Just open the SR and get your datasync working again..
Many people are having _some_ issues, especially with the Nokia devices,
but you seem to have total system issue, not a single device issue.

I know you don't have support available with ALA (argh...), you can try
it through Pekka@Novell or buy through Enfo or arrowecs, it will be
around 1000$;
http://www.alttech.com/support/novell

and, if it is defect, you'll get refunded.

-sk


HAMK University - OES, NW, GW, NCS, eDir, Zen, IDM, NSL - www.hamk.fi
0 Likes
Highlighted
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

skapanen;2105469 wrote:
On 11.05.2011 14:36, kautium wrote:
>
> We don't have high hopes about opening a Support Request.


Just open the SR and get your datasync working again..
Many people are having _some_ issues, especially with the Nokia devices,
but you seem to have total system issue, not a single device issue.

I know you don't have support available with ALA (argh...), you can try
it through Pekka@Novell or buy through Enfo or arrowecs, it will be
around 1000$;
Arrow ECS Novell Support Request Page

and, if it is defect, you'll get refunded.

-sk

Looks like we managed to get sync working both ways again by removing LDAP user group from both connectors and then adding it back again. Datasync did not remove users while doing this. I think there was some sort of hickup in datasync database and actually i'm not 100% sure things started to work for all users, but at least for some folks sync is working again.

We already installed another v1.1.1 server yesterday from scratch and it is working fine. I think we will move all users to that new server soon, since we lost our faith to our old datasync-server .

We don't have the time to negotiate with Novell support at the moment, but if this continues, then we do not have much of a choice.
0 Likes
Highlighted
Absent Member.
Absent Member.

kautium wrote:

> Looks like we managed to get sync working both ways again by removing
> LDAP user group from both connectors and then adding it back again.
> Datasync did not remove users while doing this.


I wonder if your current success is going to be short-lived. The fact
that the users weren't removed from the connectors after deleting the
LDAP groups seems to indicate a problem.

> We already installed another v1.1.1 server yesterday from scratch and
> it is working fine. I think we will move all users to that new server
> soon, since we lost our faith to our old datasync-server .


I'd say that is your best bet at this point. I wouldn't trust the old
server either, at least not without bringing in Novell technical
support.

> We don't have the time to negotiate with Novell support at the moment,
> but if this continues, then we do not have much of a choice.


If the issue comes up on your new server, I'd say you're going to have
to open an SR. But from what you describe I would be extremely
surprised if the issue came up again.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Highlighted
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

jmarton;2105524 wrote:
I wonder if your current success is going to be short-lived. The fact that the users weren't removed from the connectors after deleting the
LDAP groups seems to indicate a problem.

I didn't check what the documentation says, but is it even supposed to delete users if the group is deleted from datasync? Users will be deleted if they are removed from the group within eDirectory, but what should happen when whole group is removed from datasync?

Looks like removing and then adding ldap group back to datasync triggered initial sync process to most users, so if they had done calendar items to their phones while sync was not working, and they also had set "remove from phone" in ActiveSync client settings, they lost those items from their devices. Some users have also reported that they lost much more than that, which does not surprise anyone, since GW/Datasync connection has never been very reliable.

I wonder how for example Google makes their email, calendar and contact sync work so flawlessly and so that users find it easy to setup and use? I mean, syncing those simple items should be a pretty straightworward process, but somehow Novell is struggling with it constantly.

Our users won't take explanations much longer...
0 Likes
Highlighted
Absent Member.
Absent Member.

kautium wrote:

> I didn't check what the documentation says, but is it even supposed to
> delete users if the group is deleted from datasync?


Yes.

> Looks like removing and then adding ldap group back to datasync
> triggered initial sync process to most users, so if they had done
> calendar items to their phones while sync was not working, and they
> also had set "remove from phone" in ActiveSync client settings, they
> lost those items from their devices.


That makes sense.

> I wonder how for example Google makes their email, calendar and
> contact sync work so flawlessly and so that users find it easy to
> setup and use?


I don't believe they use ActiveSync.

Note if you do some Googling, you'll find people having various sync
issues with Exchange as well.

> I mean, syncing those simple items should be a pretty
> straightworward process, but somehow Novell is struggling with it
> constantly.


So does Microsoft.

> Our users won't take explanations much longer...


If you use any vendor's product, have a problem, and then don't contact
tech support there's a good chance your users will be upset as the
problem will persist.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
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.