WFM and Windows 2000 Installation Problem

[Victor]

Has anyone yet attempted to install Workforce Manager on Windows 2000? I am running into different problem, such as SchServer not starting up, and workforce manager refusing to create forecasts...

Anyone else is running into the same problems as I do?
The error when I am trying to do forecast is:

"Could not create forecast 'hello', because:
The Microsoft Jet database engine could not find the object 'TEST.era_PABX'. Make sure the object exists and that you spell its name and the path correctly."

This one is definitely a problem with settings. What I don't understand is WHY is it looking for era_PABX table in TEST and not in wfm? Both of my database and user in SQL server is wfm, so where is TEST coming from?

As for Schedule Server... I give up (for right now)

[Kevin]

Vic
Looks like you have a problem of the user TEST accessing the tables, are you using Oracle for the installtion....if so then you have to create Private synonyms.
Get your Orcale whizz to have a look at this, if not drop me a mail and I can put you in touch with someone

Came across this last week

[Victor]

Kevin,

you are right. This is because 'test' user has no priveleges in the database. However, the problem was with the fact that THERE WERE NO USER named TEST mentioned anywhere in CME or ODBC settings.
I thought this was really strange. Deleting WFM and SchServer settings from CME and redoing it did not do the trick either.

Just for the heck of it, I created a different CME database, and recreated all of the environment, and... it worked fine! Looking through the old CME database using Query Analyzer, I was not able to find any 'test' occurences.

I assume it was one of those mysterious glitches that somehow come and go, I just hope it will not happen in a future, because I am not too fond about recreated the whole CME environment!

Thanks for the advice!
Vic

[Victor]

Ok, it seems like SchServer really hates Windows 2000. It claims that it cannot find cs.dll file and that some entry point is not there...

I tried to copy a cs.dll file from NT 4.0, but then it asked me for Netbeu.dll, copying that and trying to run it, results in an error message claiming that an entry point was not found in cs.dll file... Aaargh...
Was anyone able to run WFM6.0 on W2000?
Vic

[K]

Vic
I am at this stage able to run Schedule Server (and everything) on my server box(Win2000 SP1 MDAC 2.6 and the latest Jet service)

You may have to tweak with the DCOM settings to get the schedule server to kick off. However I have DCOM error when trying to get my client machine to kick off a schedule.

BTW on the subject of database, Genesys like to assume that they are the database owner in WFM, not really a good idea. If you have enterprise setups, make sure your DBA is on hand

Another 2 cents

[Nick]

Hi Victor,

I reported a similar problem to Genesys when trying to run a forecast on WFM 5.1.610 (SQL Server 7 database) and got same error as yourself. Genesys advise that WFM needs to query the database as the d/b owner, so the workaround was to use the 'changedbowner' stored procedure in SQL Server to change the database owner to the username that you have set up in your ODBC connection. I suspect that the TEST came from the original owner/creator of the WFM database? Genesys also advise that 5.1.612 solves this problem. I am currently installing 5.1.621, but am not taking any chances and have made the d/b owner the same as the ODBC connection username.

As it happens, we are encountering some problems with the GUI crashing when trying to update the employee details. This would appear to be an issue with Windows 98, which is running on the workstations where I have installed WFM. Have you come across any Win 98 compatability problems?

Regards

Nick

[Vic]

What agent details cause WFM to crash?
I know that unclicking hiring date causes WFM to crash on NT!

Speaking of SchServer, can you see it in dcomcnfg? I can only see SchServerProxy.