Forum Discussion
Memorable MemberAnother meaningless spark error: Session is unable to register ReplId
Memorable MemberAnonymous
Thank you for the reply.
In this case, I seem to be the first one to ever post about this message to the public internet.
Regardless if it is transient or not, customers need to understand the meaning of any error message. We need to know if errors can be fixed in our own custom code or must be fixed in Microsoft's code. We need to know if the fix will be considered a "workaround" or a "permanent" fix. We need to know if retries should be done x3 times or x30 times. We need to know if the problem is affecting all customer tenants, or if they are isolated to just our own customer tenant.
It is extremely unlikely that this is a "temporary glitch" which I will never see again. I should mention that I've only been using Fabric Spark for a few days, and I've encountered many, many errors which are meaningless to me. I have experience with other Spark platforms and in most cases we are able to google for an explanation about any error message. In most Spark platforms the error messages can be fixed by correcting our own code. However the bugs I'm seeing in this Fabric flavor of Spark seem to originate from Microsoft's home-grown extensions to Spark. (like Livy, for example)
If you are able to interpret this error message or the callstack please let me know. You could save me a LOT of time. The Mindtree support cases take many weeks, while waiting on a response from the back-end PG. I have started that process, but nobody from Microsoft has engaged with me yet.
Hi dbeavon3,
I apologize for the challenges you're facing. I understand the importance of having clear explanations and resolutions for error messages. I suggest raising a support ticket. If you have already done so, I kindly request you to wait for the response.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Regards,
Vinay Pabbu
- dbeavon3
Anonymous
I have tried raising a support ticket, but the Microsoft PG has not started to engage with this bug yet.As-of now I am only talking to the intermediary named Mindtree. As a customer I really expect the SaaS software vendor to engage when there are bugs. Until that happens, I must also reach out to this community and to other social media. There is a fairly significant chance that others are encoungering thes bugs as well, but they have not been added to the "known issues" yet.
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
- dbeavon3
Hi 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).