| Author |
Message |
|
|
This should work with SysAid Version 9.5 and above
I have created a report for you.
1. log on as a manager then go to design Report then click on the root of the tree "sysaid" then click on the "new report" icon above the tree.
2. a new window will appear with this title "New Report Options" choose Empty Report then click save.
3. in the next window right this string next to the Caption: List Knowledgebase Aritcle Authors
4. in the same window click the Report design tab then click the Browse button next to the "Upload Report File" and choose the "list kb article authors.jrxml" file from the attachment after that click Apply button.
5. move to the Prompt tab (in the same window) then copy the whole text from the attach "list kb article authors prompt.txt" and put it there after that click the apply button.
6. finally go to the script tab and then copy the whole text from the attach "list kb article authors script
.txt" and put it there after that click the ok button and run the report.
Let me know how you get on.
|
|
|
Joseph Zargari wrote:Hi Todd,
As far as we know, after researching this issue, the number of affected accounts was minimal (less than 5), because of the rare sequence of events required to trigger this issue. Of course the moment we learned about it, the issue was fixed immediately.
The only way to recover from this issue is to re-install the affected software. We apologize for this issue, and contact us if you need any assistance.
Thanks,
Joseph
Was there a new agent release to fix this? if so what version was affected and which version contains the fix please?
I want to make sure that we are on an unaffected version.
|
|
|
|
MichaelZ has my concerns spot on. We cannot use the project or monitoring modules in their current state either.
|
|
|
Thanks for the reply Oded, but it still doesn't explain why the dynamic custom forms bit has to wait for everything else to be ready in the major release.
I guess the question that is running through some of our minds is,
do the custom forms have any reliance on what make of database we are running? - if not then surely it just boils down to testing on the current version of tomcat that most of us are on?
or am I over simplifying this one?
|
|
|
DenaWF wrote:Hi guys,
I appreciate your remarks and I do understand that many of you are In-House customers and are concerned about when you will receive all the features that we are rolling out gradually (and faster) with the Cloud releases. I’m sure you understand that this is the nature of Cloud – since we have more control over the environment, the QA process is so much quicker – and this is how we are able to release so often.
It’s not the same with our In-House releases. Especially the upcoming one, which will include 2 MAJOR features (new GUI and Patch Management), both of which require heavy resources for testing (multiple OSs and databases, etc).
most of us don't want these new modules you keep developing, what most of us want is the core helpdesk components, service desk, projects module and asset management that we have already bought regularly updated and improved, instead not more than 3 improvements have been made to the projects modules since we bought it 5 years ago.
Why not deliver just the dynamic forms improvement now to your in house customers? Agile development should be frequent small updates should it not?
|
|
|
|
same problem here.... Hope a fix is available soon.
|
|
|
have you checked the MachineID in that registry key on a couple of them to see if they have somehow ended up with the same ID?
|
|
|
Just a guess, Were the virtual servers cloned with the sysaid agent already on it?, if so they will all have the same ID.
stop the sysaid service
Go in to the registry HKEY_Local_Machine\Software\Ilient\Agent
delete MachineID
and set FirstTime to Y
restart the sysaid service
|
|
|
I cannot reproduce any of these issues.
Can I ask what browser you are using?
Have you tried emptying your browser cache - this often fixes a lot of UI issues with sysaid after version changes.
|
|
|
Thanks Oded that's great news. We will then be able to push use of the knowledgebase lots more here.
There has already been a marked increase in my admins using it - I am not having to answer as many repeat questions that I have already put in the kb now, because they can find them much easier.
Any news on the open the article in new tab facility, so we can print - will that be available in the minor fix too?
|
|
|
|
Still waiting for that reply ......
|
|
|
I am a bit confused....
When I re-installed sysaid when we moved to Windows server 2008 R2 64bit and MS SQL 2008
there was only one version of the installer, but it installed to the 64bit Program Files folder i.e not the Program Files x86
When the first beta 9 patch came out there was a 64bit and a 32 bit version and we asked the question which to install ..
The answer came back:-
Ido Shomer wrote:Hi both,
It depends where is your SysAid server installed, under the Program files or Program files(86).
If under the later use the 32 upgrade patch and if under the Program files use the 64 bit.
Best Regards
Customer Relations
Beta Team
Ido Shomer
So I installed the 64 bit patch because of where sysaid was installed .... Then came this post:-
Ido Shomer wrote:Hi all,
Let me correct myself,
If you have a 64 bit machine you should use the 64 bit upgrade patch, but make sure to point it to the correct location of your SysAid server.
It can be under Program Files or Program files (86).
This will install a 64 bit java and would enable you to allocate more memory to SysAid.
Best Regards
Customer Relations
Beta Team
Ido Shomer
By this point it was too late to do anything else....
Then along came 9.052 patch which only had one version but asked which folder you wanted to install it to, so I just installed that to the 64bit Program Files folder.
I didn't get any error messages ..
So am I just running a 32 bit version in the 64 bit program files folder, or have i made a mess of my installation? Does any of this really matter?
Perhaps you could clarify please Joseph.
|
|
|
We seem to be going round in loops on this discussion, I thought we had established already in at least 2 other topics during the beta process that setting or unsetting that option does nothing except to hide the link to change views, it does not force the new tree view to appear for everyone.
And in your last post to me Oded you said that you thought you had a workaround and were going to get someone to contact me with it.
Oded M wrote:
Regarding the old KB UI, I think there is a workaround you can try to make sure only the new Ui is available and the old UI won't pop up for your users - I will have the teams check and communicate the solution to you for testing.
|
|
|
We seem to be going round in loops on this discussion, I thought we had established already in at least 2 other topics during the beta process that setting or unsetting that option does nothing except hide the link to change views, it does not force the new tree view to appear for everyone.
And in your last post to me Oded you said that you thought you had a workaround and were going to get someone to contact me with it.
Oded M wrote:
Regarding the old KB UI, I think there is a workaround you can try to make sure only the new Ui is available and the old UI won't pop up for your users - I will have the teams check and communicate the solution to you for testing.
|
|
|
posted in the beta phase :-
Ido Shomer wrote:Hi all,
We can confirm that in IE9 compatibility view the check box in Customize>>Appearance Display ‘Switch to List view’ link in Knowledge Base page will not show neither will the link to siwtch between the old & new views in the knowledge base itself.
As an interim solution we would suggest to use IE not in compatibility view.
Best Regards
Ido Shomer
Customer Relations
Beta Team
Are you using IE9?
|
|
|
