Forum Discussion
Memorable MemberAnother meaningless spark error: Session is unable to register ReplId
Hi dbeavon3,
I understand your frustration and concerns. Could you please provide an update on the status of your ticket? Has the issue been resolved or has the support team provided any solution ?
Regards,
Vinay Pabbu
Memorable MemberHi Anonymous
I haven't updated the community since this past Monday.
As I mentioned, I was blocked by SME at Microsoft for several days. I think I'm unblocked now. I am told there is an ICM now, but I can't independently verify whether that is true.
I doubt you have access to see the customer SR, but you are more than welcome to try. The SR number is TrackingID#2501160040000052.
I am pretty satisfied with the effort on the Mindtree side. However I don't have high hopes for the back-end PG. At the very minimum I would expect them to publish their bugs to their "known issues" list. It doesn't seem they do that as a matter of course. As-of now all the spark bugs we encounter are missing from the public list, and it requires a minimum investment of 10+ hours of time, along with an average wait time of two weeks before any ticket is sent to the PG (via a new ICM).
Hi dbeavon3,
Thankyou, I completely understand your issue; however, I am unable to access ICMs with just the tracking ID. Could you please provide the ICM ID?
Since there is already an ICM in place, I hope it will be resolved as soon as possible based on the severity. I kindly request your patience until the ICM is resolved.Regards,
Vinay Pabbu
- dbeavon3
Hi Anonymous You should be able to find the ICM attached to the SR.
Do you work for Mindtree? It seems like you are unaware of their policies and procedures. You are far more likely than me to get ahold of the ICM number. You can reach out to the ops manager or to any Microsoft FTE.Fabric Bugs are so challenging to work on, starting with the fact that Microsoft/Mindtree won't even share the bug identifiers. It is extremely frustrating. In place of a real identifier, you can use this post or else the SR number. Those can serve as the bug identifier, especially when opening a "unified" ticket about the bug. In my experience you can get any identifiers you may need (like the ICM) by talking to an FTE. A Microsoft employee has a lot fewer restrictions on what they can share about Microsoft bugs.
Hi dbeavon3,
I understand your frustration, and I sincerely apologize for any inconvenience. I do not have direct access to track ICMs.
ICMs are managed by the support team, who prioritize them based on severity and issue type. Unfortunately, I do not have the scope to reach out to other members regarding ICMs. I recommend waiting for the support team’s updates, as they have full control over the resolution process.
Regards,
Vinay Pabbu