Splunk 6.2 upgrade issue -- users can no longer create dashboards

[dhavamanis]

After Splunk upgrade from 6.1.4 to 6.2, users not able to create the dashboard and its giving this error message.

In handler 'views': Could not find object id=test1

Can you please help us to resolve this issue.

[splunkIT]

FYI: this issue has already been addressed in splunk maintenance release 6.2.1 or later:

http://docs.splunk.com/Documentation/Splunk/6.2.1/ReleaseNotes/6.2.1

[jdastmalchi_spl · Accepted solution]

Both are known issues and will be addressed SPL-93439 for "."  & SPL-93453 for "@"

[dhavamanis]

We are keeping username as email to identify users uniquely. If the username contains “@” symbol and its breaking some of the features. I tried without “@” in username for user level role and its working fine.

http://answers.splunk.com/answers/104459/dashboards-wont-load-after-upgrade-to-splunk-6.html

[klnmc]

Recently upgraded from 5.0.10 to 6.2.0 . This is happening with the "." character in usernames also. This is happening across all apps including search. Examples:

User "admin" can create dashboards
User "dashboardtest" can create dashboards (fresh user with only the default "user" role)
User "firstname.lastname" cannot create dashboards

[dhavamanis]

We are keeping username as email to identify users uniquely. If the username contains “@” symbol and its breaking some of the features. I tried without “@” in username for user level role and its working fine.

http://answers.splunk.com/answers/104459/dashboards-wont-load-after-upgrade-to-splunk-6.html

[Thomas_Aneiro]

I have the same issue. In addition if you try to click save a second time it displays the below error message;

"Encountered the following error while trying to save: In handler 'views': An object with name=tst01 already exists"

Yet when searching through all views on the server there are none with the name tst01.

[Lucas_K]

Double check your metadata/local.meta in the app and make sure there is no reference to that view. Or alternatively double check that it is actually correct (owner and permissions).

If you try to create another view inside that app and its already owned by someone else it will error. If someone manually deleted the dashboards xml file the permissions may still persist inside local.meta causing that "already exists" error.

[Thomas_Aneiro]

Unfortunately no, this is something I am still working on. I posted the above in hopes that adding more info would help anyone being able to help us. I was not able to post a comment, only an answer that is why it was posted in that fashion.

[dhavamanis]

can you tell me, how to fix this issue?.